Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Native QML UI Controls

Sponsored · Your Podcast. Everywhere. Effortlessly. Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.

Native QML UI Controls

Explore the (dis)advantages of using QML wrapped native UIs and toolkits, as opposed to the traditional QtQuick / QtQuick Controls based UIs. Moving from the single-codebase lowest-common-denominator UI approach to the single-language native-look-and-feel(-and-performance) UI one. #QtCS

Avatar for Attila Csipa

Attila Csipa

June 07, 2015
Tweet

More Decks by Attila Csipa

Other Decks in Programming

Transcript

  1. The Way of the Desktop  Largely styling differences 

    Similar input methods  Limited number of platforms … not easy, but doable
  2. 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
  3. 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!
  4. 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)
  5. 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
  6. To awesome UIs… and beyond! (node.js + Meteor + qmlviewer)

    http://achipa.blogspot.no/2014/12/meteor-and-qt-match-made-in-heaven.html
  7. Pitfalls  imports are pain  QML lacking support conditionals

     It’s a ”lesser evil” choice (multiple source files versus “almost works everywhere”)