I've been having fun writing apps in strict QML, intentionally. About every weekend I just take a traditional app use case and try writing it from scratch.
And surprisingly, the shortcoming is always documentation shortfalls. It took me digging through code samples to find out activeFocusItem is a thing, for example.
Just note you can't deploy QML only apps to mobile, you need a system with qmlscene installed already, but it is trivial to have a small C++ layer, and removing the JS only restriction gives you a huge amount more power over QML itself (building your own components in C++ vs combining them in JS).
I've been having fun writing apps in strict QML, intentionally. About every weekend I just take a traditional app use case and try writing it from scratch.
And surprisingly, the shortcoming is always documentation shortfalls. It took me digging through code samples to find out activeFocusItem is a thing, for example.
Just note you can't deploy QML only apps to mobile, you need a system with qmlscene installed already, but it is trivial to have a small C++ layer, and removing the JS only restriction gives you a huge amount more power over QML itself (building your own components in C++ vs combining them in JS).