Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-31 Thread Elvis Stansvik
Den 31 mar 2016 3:10 em skrev "Nikita Krupenko" : > > 2016-03-30 16:17 GMT+03:00 Elvis Stansvik : > > I saw that there's an > > ObjectModel that could have been handy, but it's Qt 5.6+ only (while > > our product will use Qt 5.5.1 since it's based on current Ubuntu). > > No, it's not 5.6 only, this

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-31 Thread Nikita Krupenko
2016-03-30 16:17 GMT+03:00 Elvis Stansvik : > I saw that there's an > ObjectModel that could have been handy, but it's Qt 5.6+ only (while > our product will use Qt 5.5.1 since it's based on current Ubuntu). No, it's not 5.6 only, this component exists from the early beginning of QML. Though in so

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-30 Thread Elvis Stansvik
2016-03-30 16:16 GMT+02:00 Martin Leutelt : > From: Elvis Stansvik > To: Martin Leutelt > Cc: "interest@qt-project.org Interest" > Sent: 3/30/2016 3:17 PM > Subject: Re: [Interest] Structuring of QML app as set of interlinked screens > for maximum code reuse &g

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-30 Thread Martin Leutelt
From: Elvis Stansvik To: Martin Leutelt Cc: "interest@qt-project.org Interest" Sent: 3/30/2016 3:17 PM Subject: Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse 2016-03-22 22:38 GMT+01:00 Martin Leutelt : > Von: E

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-30 Thread Elvis Stansvik
2016-03-22 22:38 GMT+01:00 Martin Leutelt : > Von: Elvis Stansvik > An: "interest@qt-project.org Interest" > Gesendet: 22.03.2016 20:19 > Betreff: Re: [Interest] Structuring of QML app as set of interlinked screens > for maximum code reuse > > 2016-03-22 20:13 G

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-29 Thread Elvis Stansvik
2016-03-29 11:36 GMT+02:00 Nikita Krupenko : > QQC2 available in 5.6 as TP, is actively in development and final > version should be in 5.7. Some issues fixed only in 5.7. I recommend > to target to use Qt 5.7, if you plan to use QQC2. > You can mix both controls, but this controls use different Hi

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-29 Thread Nikita Krupenko
QQC2 available in 5.6 as TP, is actively in development and final version should be in 5.7. Some issues fixed only in 5.7. I recommend to target to use Qt 5.7, if you plan to use QQC2. You can mix both controls, but this controls use different HiDPI scaling mechanism: https://bugreports.qt.io/brows

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-29 Thread Elvis Stansvik
2016-03-25 10:32 GMT+01:00 Nikita Krupenko : > 2016-03-22 21:13 GMT+02:00 Elvis Stansvik : >> But this will only allow me to redefine properties, and add new child >> items. How would I then be able to define both which content goes in >> the main area (the content Rectangle in the "base" item) and

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-29 Thread Elvis Stansvik
Hi Nikita, (just back from Easter holiday) 2016-03-25 10:32 GMT+01:00 Nikita Krupenko : > 2016-03-22 21:13 GMT+02:00 Elvis Stansvik : >> But this will only allow me to redefine properties, and add new child >> items. How would I then be able to define both which content goes in >> the main area (

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-25 Thread Nikita Krupenko
2016-03-22 21:13 GMT+02:00 Elvis Stansvik : > But this will only allow me to redefine properties, and add new child > items. How would I then be able to define both which content goes in > the main area (the content Rectangle in the "base" item) and in the > two navigation bars (topBar and bottomBa

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-23 Thread Elvis Stansvik
ot;interest@qt-project.org Interest" >> Gesendet: 22.03.2016 20:19 >> Betreff: Re: [Interest] Structuring of QML app as set of interlinked screens >> for maximum code reuse >> >> 2016-03-22 20:13 GMT+01:00 Elvis Stansvik : >>> Hi all, >>> >>

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-23 Thread Elvis Stansvik
Betreff: Re: [Interest] Structuring of QML app as set of interlinked screens > for maximum code reuse > > 2016-03-22 20:13 GMT+01:00 Elvis Stansvik : >> Hi all, >> >> I'm working on a fullscreen Qt Quick/QML app (for machine control) >> which will consist of a

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-23 Thread Jason H
> Sent: Tuesday, March 22, 2016 at 3:13 PM > From: "Elvis Stansvik" > To: "interest@qt-project.org Interest" > Subject: [Interest] Structuring of QML app as set of interlinked screens for > maximum code reuse > > Hi all, > > I'm working on a fulls

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-22 Thread Ben Lau
If I understand your question correctly, you may use alias property to point to children of main / navigation bar. In Angular JS, they call this feature as "transclude". For example, Screen.qml: Item { property alias main : mainContainer.children } CustomScreen.qml: Screen { main: Item {

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-22 Thread Martin Leutelt
Von: Elvis Stansvik An: "interest@qt-project.org Interest" Gesendet: 22.03.2016 20:19 Betreff: Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse 2016-03-22 20:13 GMT+01:00 Elvis Stansvik : > Hi all, > > I'm wo

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-22 Thread Elvis Stansvik
2016-03-22 20:13 GMT+01:00 Elvis Stansvik : > Hi all, > > I'm working on a fullscreen Qt Quick/QML app (for machine control) > which will consist of a set of interlinked screens, with key presses > as the only interaction method. > > Each screen will have roughly the following QML structure: > > Re

[Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

2016-03-22 Thread Elvis Stansvik
Hi all, I'm working on a fullscreen Qt Quick/QML app (for machine control) which will consist of a set of interlinked screens, with key presses as the only interaction method. Each screen will have roughly the following QML structure: Rectangle { NavBar { id: topBar ...