The sane way to have the Theme element exported is via
qmlRegisterSingletonType() so I think that's what sailors are doing :)
About the import, they probably just registered the singleton type using
the Sailfish.Silica import URI, so you don't have to import another module
to be able to access the
Hi Thomas
I was hoping you would answer 8-)
The .js route did occur to me, but I initially decided to make that "Plan B".
As the list of UX constants will be used by most of the QML files in
my project, a shared js script (i.e. defined as .pragma library) would
seem to be the way to go. But
On 2014-01-28 10:59, christopher.l...@thurweb.ch wrote:
I would like to create a C++ plugin for my app to export common UX
settings as constants to the QML side (Things like font sizes, margin
sizes that reoccur throughout the app.)
In essence I want something very similar to the functionality
Hi All
I would like to create a C++ plugin for my app to export common UX
settings as constants to the QML side (Things like font sizes, margin
sizes that reoccur throughout the app.)
In essence I want something very similar to the functionality offered
by by the Silica Theme.
After som
