Native QML Controls Attila Csipa, Qt Contributor Summit 2015 

The Way of the Desktop  Largely styling differences  Similar input methods  Limited number of platforms … not easy, but doable 

The evolutionary explosion  Vastly different interaction paradigms  Mouse + keyboard desktop  Touch enabled desktop/laptop  Tablet  Mobile phone  Embedded  Automotive  Smartwatches …don’t… even… try… to… cover them all 

The heartlant of Qt UIs CUSTOM 60FPS NIRVANA 

Common controls story… a bridge too far?  Vastly different interaction paradigms  Mouse + keyboard desktop  Touch enabled desktop/laptop  Tablet  Mobile phone  Gesture-driven (Kinect, Leap motion, Sprout)  Voice-driven (Cortana, GNow, Siri)  Embedded  Automotive  Console  Smartwatches  … my list will go oooon! 

Common controls story… a bridge too far?  Interaction development pace is increasing  New iOS every year  New Android each year  Win10 switching to iterative releases  Feature/style creep (bloat) 

It’s not about sharing code It’s about sharing technology  QML is a good fit – Syntax  Declarative  Terse  Generic  Familiar (JSON/Qt)  QML is a good fit – Object model  Introspective  Dynamic 

Native demos A.k.a. this is not just wishful thinking https://speakerdeck.com/achipa/fast-qml-ui-prototyping-for-platforms-without- qt-or-qtquick-support https://www.youtube.com/watch?v=Mo8J-g5XPGQ 

To awesome UIs… and beyond! (node.js + Meteor + qmlviewer) http://achipa.blogspot.no/2014/12/meteor-and-qt-match-made-in-heaven.html 

Pitfalls  imports are pain  QML lacking support conditionals  It’s a ”lesser evil” choice (multiple source files versus “almost works everywhere”) 

Thanks! (Discuss) Qondrite (the nodejs+Meteor+QML thing - https://github.com/achipa/Qondrite Android native controls - http://code.qt.io/cgit/playground/qtqmlandroid.git/