The intuitive simplicity of QML is blessing and curse at the same time, because Java Script and Property Bindings do not necessarily encourage to write nice and clean source code.
In my session, I will talk about the lessons I learned over the last 5 years of professional UI development with Qt. As well as best practices for QML code- and project structure, I will present tricks, workarounds and problem solving strategies for common and frequently asked QML problems, such as:
-How do I set up a well organised QML project with outsourced colours, fonts and icons?
-How to implement flyouts, overlays or dialogs with a well-thought-out z-layering concept?
-How to detect click-events outside a Component (very useful to close an overlay)?
-How to develop custom controls in QML that are not only easy to use for the end user but also for the developers?

QtQuick is very performant: it runs on pretty much any platform and has a very steep learning curve. This is why Qt currently belongs to the most modern and versatile UI technologies on the market. QML allows to solve many problems with astonishingly little effort. In some cases however, seemingly small problems can result in big questions. In these situations it’s important to really understand the relevant concepts.

In my session I want to share my experience by presenting reusable techniques that will save a lot of time.

For example:
A well organised QML UI project template with outsourced colours, fonts and icons (singleton components / singleton js files).
A generic way to handle multiple Z-layers combined with a way to catch click-events outsides the the components own rectangle.
Example for handling declarative view interactions using a self-populating menu tree.

Info

Day: 2016-09-02
Start time: 16:15
Duration: 00:10
Track: QtQuick

Files

Feedback

Click here to let us know how you liked this event.