Showcase

I'm very aware of signals and slots. IMO JS-like promises solve a slightly different problem. Qt signals are shared among all subscribers. Promises are specific to a single function call. In my lib I implemented promises using signal and slots. The difference is that there is a new QObject for each function call. In my experience this prevents potential issues with clients connecting to the same signal in the same object and then receiving multiple signals or having to manually disconnect after the first signal... Also signals and slots are scattered in the class header and in many functions, while the promise approach is more self-contained.

@posktomten Thanks! That's exactly the audience it's aimed at. Let me know if there is any feedback.

The latest coverage report for ShoopDaLoop is here.

Grateful for the enriching insights provided in the recent blog regarding OHT+Behavior: heat-maps and path-maps for Qt GUIs, alongside user-interaction abstraction! If you're keen on delving further into this fascinating realm, I encourage you to explore our dedicated blog section on UX heatmap. Dive in and uncover more about enhancing user experiences!

@oldmanCPP Please use https://forum.qt.io/category/8/showcase for advertisements...

@posktomten Now it should work! Feel free to write a comment if it doesn't work as intended. Good to know! "Unfortunately my compilation of Qt5.15.12 64-bit Linux GLIBC 2.27 was corrupt. I'll be back with a better version as soon as I have time. Excuse!"

@Mesrine One can play with the types in the browser here. If you found it interesting, please consider giving it a star on Git Hub. Also if you think this is a dead end, and there is no future for QML, please let me know.

@Mesrine One can play with the types in the browser here. If you found it interesting, please consider giving it a star on Git Hub. Also if you think this is a dead end, and there is no future for QML, please let me know.