I'm the OP, and I have to pitch in here. This comment is a bit unhinged, basically claiming that every WIP GUI library written in Rust sucks on principle. This is false, and there are some very good ongoing efforts that will probably be great and desirable GUI options in the future.
Also, the comment claims that QML is not Qt. QML was added to Qt in 2009 and has been where a large proportion of the developer's focus has been ever since. It is absolutely Qt and you can't claim otherwise.
A bit of a passionate response to a passionate parent comment.
Hey, I'm the author of the post. Thanks for reading! Appreciate it :)
I think QML is very easy to get started with and you should just give it a go. It's not without its weirdness as other comments have already mentioned, and unfortunately there's still many controls that are less-than-ideal for desktop applications than their original QWidget equivalents. Using QWidgets+UIC is nice, but in my experience creates problems when you want to get fancy and custom with your design, with animations and shifting layouts and whatnot, well, especially after using QML.
A lot of apps people use these days are cloud-first and automatically save all the time, so there's not even a save button to have a floppy icon for! The icon to say that it's synced looks like a cloud, and if you're using a web browser it'll probably have a Download button with a download icon. No floppy disks in sight.
I wouldn't be surprised if there's computer users out there that wouldn't recognise the "save icon".
I disagree. Not all it's "autosave on cloud", and some apps keeps having an explicit save something button or option.
I recently had a discussion about replacing the "save icon" (IE. the old floppy disk icon) for an icon with an arrow pointing down, for a button that saves (don't download!) a custom query of the user in the system. Perhaps it could be replaced with another icon, but not by someone that everyone would think is "Download".
I strongly suspect I know what that does because I worked with Svelte 4 for years (you no longer have to do this in Svelte 5. I can recommend Svelte 5, it's nice).
Basically, assigning a state to itself tells it to signal that that state has changed and update anything that is listening to it. The `state` object is actually a JS Proxy returned by createState [0], which allows intercepting the assignment to the `windows` property and emit signals. Usually you dont have to do that, but in this case, the proxy doesn't notice that `state.windows.push(X)` is a mutation. Only assignments directly to the state object count as mutations.
TLDR, `state.windows = state.windows` tells the framework that `windows` changed.
This is a pretty neat idea, and shows that maybe a desktop environment could be a lot more flexible than we're used to if it was based on something flexible. Not exactly counter intuitive.
I'd like to see how complex a CEF-based Wayland compositor would be in comparison.
How about using Godot instead of CEF? It has a pretty full-featured UI system.
While you're at it, go on a huge tangent writing a library that allows one implementation to work as both an X11 and Wayland compositor.
Actually why stop there? Make said library also compile to a full screen Windows and Macos application that somehow renders the contents of windows to textures and does event handing etc. that way you can write your desktop environment once and use it everywhere.
reply