-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start the compositor side of the book #9
base: master
Are you sure you want to change the base?
Conversation
Forgot to commit this...
Bringing this back to a draft, I should probably rework the pages off |
Also, now The content of the calloop book are in calloop's git repo btw. |
Is there any new progress here? I am a wayland noob looking too write my own compositor in rust, very hooked on doing it with Smithay. But i am struggeling too learn how all the pieces work together. |
Been busy with a pull request in smithay recently. So I haven't had time to prioritize this specific pull request. |
At the moment if you need guidance, looking at anvil and joining irc or matrix would be best :) |
yeah, i should probably keep trying too read the source code off anvil. Will get myself on the Matrix. Thanks! |
You should join Smithay's matrix/irc, I'm sure everyone will be happy to help you one the way. |
Just joined the matrix chat. Bookmarked your wm, so i will surely copy paste some code from it sometime, lol. |
I suggest catacomb to be used as reference, it's created by alacritty's author, and codebase is relatively small and less complex than every other compositor mentioned above. (thats what I'm using as refernce for empty yet kerastes). |
Yep we have talked to @chrisduerr on matrix while catacomb was being in early stages and still to today. However this issue has been put to the side until the rework of wayland-rs is complete. Regarding catacomb for documentation reference, it is different from other compositors, descendants of anvil, however it has other issues, namely GPL which is not going to be suitable for reference in the book unless chrisduerr signs off on allowing us to reference catacomb for the book. Plus I also have my own compositor in the works which is not a direct descendant of anvil and I do think we will need to redesign anvil as a result of the wayland-rs rework. |
I think most of the code taken in the early commits is almost a verbatim copy from Anvil anyway, just removing stuff that isn't absolutely necessary. So there shouldn't be any issue with just using that as a reference and publishing it under MIT/Apache. I'm fine with smithay using any of the code before the license was added to help out, the first commit is likely the most useful one for minimal examples though. Either way things will likely have to be rephrased a bit, at which point I'm not sure any specific compositor will be of much use for more than a rough reference. The best "type" of behavior for an example would likely just be a Kiosk, since that gets rid of all the compositor-specific window management subjects. |
I have experience with some wlroots and now pure libwayland++, I have created private 32k loc vulkan compositor with it but even that makes it hard (at least for me) to switch from C++ implementation of protocol and start writing new and open source one in pure Rust. My first ever compositor was was written in first versions of Smithay 2,5 year ago but we all know how is this library today. |
I guess we may as well get the book on the road, Ive got what is effectively an empty compositor setup for the first page.