smithay VS yofi

Regarding smithay being production ready, it's bug tracker mentioned it does not implement "idle-inhibit" , iirc that means you can't watch a movie without the lock screen being activated, i would argue most people would not consider that a production ready library.

https://github.com/Smithay/smithay may or may not be useful, depending on what exactly you want to do.

Understand Wayland concepts: Familiarize yourself with the basic concepts and principles of Wayland. This will help you gain a solid understanding of how the system works. You can refer to the official Wayland documentation (https://wayland.freedesktop.org/docs/html/) and the Wayland book (https://wayland-book.com/). Learn Rust: If you're not already proficient in Rust, take some time to learn the language. The Rust Book (https://doc.rust-lang.org/book/) is a great place to start. Study existing Wayland compositors: Since you mentioned Anvil and smallvil, you can study their source code to gain insights into how they're designed and implemented. Try to understand the structure and how different components interact with each other. Dive into Smithay: Smithay (https://github.com/Smithay/smithay) is a Rust library for building Wayland compositors. Familiarize yourself with the library and its components. You can start by studying the provided examples and reading the API documentation. Learn graphics programming: Since you're interested in graphics effects, you'll need to learn about graphics programming concepts, such as shaders, framebuffers, and texturing. Vulkan (https://www.vulkan.org/) is a popular graphics API that you can use with Rust. Check out the following resources to learn more about Vulkan and graphics programming in Rust: Vulkan Tutorial (https://vulkan-tutorial.com/) gfx-rs (https://github.com/gfx-rs/gfx), a Rust graphics library Vulkano (https://github.com/vulkano-rs/vulkano), a safe, pure-Rust wrapper around the Vulkan API Start small: Break down the compositor project into smaller, manageable tasks. Begin by implementing basic functionality, like setting up a window and drawing simple shapes. Gradually add more features, such as input handling and window management. Ask for help: Join the Wayland and Rust communities to ask questions and seek advice. You can find them on forums, mailing lists, and chat platforms like Discord or IRC. The Wayland mailing list (https://lists.freedesktop.org/mailman/listinfo/wayland-devel) and the Rust programming subreddit (https://www.reddit.com/r/rust/) are good places to start. Iterate and experiment: As you progress, keep experimenting with different graphics effects and shaders. Try to implement the features you're interested in, such as blur, window previews, and window switching.

Wayland compositor: https://github.com/Smithay/smithay

There is also smithay which is used by system76 for their new wayland compositor.

fwiw, wlroots-rs is no longer maintained. Consider using smithay instead.

Hello! I would like to hear some suggestion and opinions from Rust community about building Wayland ecosystem in Rust based around Smithay and their Client Toolkit. I'm working with Wayland Compositors for over 2 years now (private projects) and wanted to move ahead from C++ to build modern Desktop Ecosystem and it's components (truly unique, not copies of macOS or Windows styles) like notification daemon, customizable desktop shell or powerful wallpaper daemon for any compositor which implements layershell protocol. Current idea is to create wallpaper daemon which uses WGPU to render shaders, images or gifs with comfort of high perofrmance renderer (still learning wgpu and it's slow process). For UI components I would like to use truly amazing KayakUI create which uses JSX-style syntax for designing widgets. Desktop Shell should provide plugins (most likely applied through WASM) for integrating various creates to get e.g. weather info or compositor integration etc.

So you want to pass argument(s) to the program, right? That's a little bit messy, because sometimes you want to launch an app that contains multiple words and another time an app with some arguments. Personally don't really like the implicit way of handling that (e.g. as it done in rofi), so I'd like to consider an explicit argument separation via special characters, take a look at this issue.