OK, I gotta hand it to CoPilot.
-
I think I'm making a charset/tileset editor now, somehow? Why are all the existing tools for this stuff so complicated and confusing?
Qt Quick/QML has too many ways to make runtime errors. Why am I dealing with static types and a compiler and static analyzers if I can still have random brokenness I'll only find at runtime by clicking the right place?
This does not spark joy.
-
Qt Quick/QML has too many ways to make runtime errors. Why am I dealing with static types and a compiler and static analyzers if I can still have random brokenness I'll only find at runtime by clicking the right place?
This does not spark joy.
@swelljoe Have you looked at Slint (https://slint.dev/)? Its accessibility is a work in progress, but as I understand it, it supports static typing all the way through. Written in Rust, but supports a few languages, including C++ and Python.
-
@swelljoe Have you looked at Slint (https://slint.dev/)? Its accessibility is a work in progress, but as I understand it, it supports static typing all the way through. Written in Rust, but supports a few languages, including C++ and Python.
@matt I hadn't heard of it. I kind of settled on Qt because it's so mature, has accessibility features baked in, has good tooling (qmillint, Gammaray, etc.), and I could find a lot of examples (I simply need examples, my brain can't do anything with just an API reference). And, it's not terrible that I got an excuse to refresh and modernize my C++ skills a little bit.
But, when it comes to building something big, I kind of already know I don't want to use C++ or Qt. Probably Rust or Zig.
-
@matt I hadn't heard of it. I kind of settled on Qt because it's so mature, has accessibility features baked in, has good tooling (qmillint, Gammaray, etc.), and I could find a lot of examples (I simply need examples, my brain can't do anything with just an API reference). And, it's not terrible that I got an excuse to refresh and modernize my C++ skills a little bit.
But, when it comes to building something big, I kind of already know I don't want to use C++ or Qt. Probably Rust or Zig.
@matt oh, they're aiming straight for Qt's embedded/auto market, huh? They have a backend targeting Linux without X or Wayland. Very embeddy. https://docs.slint.dev/latest/docs/slint/guide/backends-and-renderers/backend_linuxkms/
-
@matt oh, they're aiming straight for Qt's embedded/auto market, huh? They have a backend targeting Linux without X or Wayland. Very embeddy. https://docs.slint.dev/latest/docs/slint/guide/backends-and-renderers/backend_linuxkms/
@matt but, it looks really nice! Reactive UIs seemingly without the island of garbage upon which they built React.js.
-
Qt Quick/QML has too many ways to make runtime errors. Why am I dealing with static types and a compiler and static analyzers if I can still have random brokenness I'll only find at runtime by clicking the right place?
This does not spark joy.
More progress on the sprite editor. Preview looks OK, now (it was stretched to fill the space before, because I'm still figuring out how to make things specific sizes and shapes and locations in QML). Save also works correctly.
I also made a little guy with a big butt and big ears, I guess.
-
More progress on the sprite editor. Preview looks OK, now (it was stretched to fill the space before, because I'm still figuring out how to make things specific sizes and shapes and locations in QML). Save also works correctly.
I also made a little guy with a big butt and big ears, I guess.
Tried to refactor Main.qml into separate components without any alteration of the appearance or functionality.
In the distance, sirens.
-
Tried to refactor Main.qml into separate components without any alteration of the appearance or functionality.
In the distance, sirens.
Maybe that joke is obscure tumblore and I should explain.
-
Maybe that joke is obscure tumblore and I should explain.
I just looked into what it costs to sell games and stuff on Itch.io, and creators can set their own amount to give to Itch.io, instead of the flat 30 that Steam and all the app stores take. That's nice. That's really nice. From now on, if I can buy a game there instead of Steam, I'm doing that, because I never feel great about so much of the money not going to the creator.
-
I just looked into what it costs to sell games and stuff on Itch.io, and creators can set their own amount to give to Itch.io, instead of the flat 30 that Steam and all the app stores take. That's nice. That's really nice. From now on, if I can buy a game there instead of Steam, I'm doing that, because I never feel great about so much of the money not going to the creator.
This post is deleted! -
I just looked into what it costs to sell games and stuff on Itch.io, and creators can set their own amount to give to Itch.io, instead of the flat 30 that Steam and all the app stores take. That's nice. That's really nice. From now on, if I can buy a game there instead of Steam, I'm doing that, because I never feel great about so much of the money not going to the creator.
Looks exactly the same, but now most of the QML types are in their own files, Main.qml is much smaller, and we have 0 qmllint complaints. Most of this evening has been spent trying to reason out what recommendation `qmllint` is making and why. C++ and Qt docs are always so unopinionated. I need these folks to take a stand. If it's worth spitting out a warning in qmllint, it's worth being clear about what the user should do.
My little man drawing skills keep getting worse, somehow.