asset prefix: asset://main.qml
will automatically be targeted to the ‘right’ location, and the build system will deploy to the ‘right’ location, too.
select different one file for platform (and model):
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 (e..g named Conf)
screen size / DPI / orientation
There will be variables to bind too.
To be continued …
- Import Restrictions ? Security?
- How does that relate to Ubuntu Grid Units?