Qt-contributors-summit-2013-Adaptive-UI: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==Asset Prefix:== | |||
asset prefix: asset://main.qml | |||
will automatically be targeted to the ‘right’ location, and the build system will deploy to the ‘right’ location, too. | |||
==Selectors:== | |||
select different one file for platform (and model): | |||
../Conf.qml<br /> ../+tablet/Conf.qml<br /> ../+desktop/Conf.qml | |||
Some selectors will be provided by Qt, but there is an <span class="caps">API</span> for also add selectors. | |||
The selector logic should not only work for <span class="caps">QML</span> , but be part of Qt Core. | |||
What about performance? | |||
One could resolve some selectors at deployment time (e.g. platform). In addition one might resolve things at installation time (separate map file), or cache resolved paths between runs if the selectors haven’t changed. | |||
How to find the right file in case of conflicts / selectors providing the same file? | |||
Qt Creator could provide means to select active’ selectors’. | |||
Q: Will you be able to switch selectors at runtime (landscape/portrait)? | |||
Not really. You could reset the UI by reloading all .qml files though. But maybe it’s not the right thing for orientation changes anyway. | |||
==Singleton elements:== | |||
Singleton elements (e..g named Conf)<br /> fontSize:Conf.size | |||
==screen size / <span class="caps">DPI</span> / orientation== | |||
There will be variables to bind too. | |||
==Layouts== | |||
To be continued … | |||
* Import Restrictions ? Security? | |||
* Timeframe? | |||
* How does that relate to Ubuntu Grid Units? | |||
Revision as of 14:05, 25 February 2015
Asset Prefix:
asset prefix: asset://main.qml
will automatically be targeted to the ‘right’ location, and the build system will deploy to the ‘right’ location, too.
Selectors:
select different one file for platform (and model):
../Conf.qml
../+tablet/Conf.qml
../+desktop/Conf.qml
Some selectors will be provided by Qt, but there is an API for also add selectors.
The selector logic should not only work for QML , but be part of Qt Core.
What about performance?
One could resolve some selectors at deployment time (e.g. platform). In addition one might resolve things at installation time (separate map file), or cache resolved paths between runs if the selectors haven’t changed.
How to find the right file in case of conflicts / selectors providing the same file?
Qt Creator could provide means to select active’ selectors’.
Q: Will you be able to switch selectors at runtime (landscape/portrait)?
Not really. You could reset the UI by reloading all .qml files though. But maybe it’s not the right thing for orientation changes anyway.
Singleton elements:
Singleton elements (e..g named Conf)
fontSize:Conf.size
screen size / DPI / orientation
There will be variables to bind too.
Layouts
To be continued …
- Import Restrictions ? Security?
- Timeframe?
- How does that relate to Ubuntu Grid Units?