yokljo
Joined 7 years ago
Joined 7 years ago
Pretty happy with this one: https://www.dwitter.net/d/7421
It's always fun just spending 10 minutes slamming together some trig functions and see what appears on the screen.
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.
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.
I wouldn't be surprised if there's computer users out there that wouldn't recognise the "save icon".
RIP in peace
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.
[0]: https://github.com/MercuryWorkshop/dreamlandjs/blob/1e7a34a1...
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.
I've gone crazy with power.
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.
So many possibilities.