Hi, and thanks for your help working through this!
On 24/03/15 18:07, Alexandre Abreu wrote:
Hi,
That sounds about right, ...
As you said, since then the css/js has since then received a bit of
love with quite a bit a bug fixing ad polishing for the system wide
installed theme. Our goal was to get it in proper work order so that
most of the hurdles are not there anymore and to basically keep it
that way (hurdles free),
Also, it is not in our priority at the moment to expand the support to
more theme or to have a more extensive support for theme switching
(more on that later).
totally understand that
We could revisit some of those bits if we are met with enough interest
and we obviously welcome contributions with open arms, this project in
particular is very contribution friendly.
yay
We might *fix* the theme layout to make things more manageable in
terms of theme selection (sounds like a low hanging fruit) and make it
more future proof, this seems like a reasonable thing to do anyway and
I will take a note to try to tackle that,
Regarding the mechanism to have a system wide theme selection, this is
something that we can tackle once we have something that is in better
shape in terms of structure, and I can think of easy mechanisms to add
there,
--
Alex
I do totally appreciate that the priority is one working theme, I am
just trying to figure out something sensible to do now, so that things
stand a fighting chance of working in the future. I am a bit concerned
that getting local and remote apps to load
/usr/share/ubuntu-html5-ui-toolkit/*0.1/ambiance*/css/appTemplate.css is
doomed to fail at some point in the future.
If right now there was a /usr/share/ubuntu-unity-theme which was a
symlink to /usr/share/ubuntu-html5-ui-toolkit/0.1/ambiance then I could
happily load /usr/share/ubuntu-unity-theme/appTemplate.css in the
knowledge that one day there might be something more dynamic there,
which would likely continue to work reasonably well even it ends up not
being a symlink, but some dynamically generated thing based on values
picked out of the QML theme for the device. There are other ways to
solve this, like a file that does an @include of our one and only theme,
and there are probably issues around javascript and paths and
containment that I don't yet understand. I don't think theme selection
needs to be solved today, but I do think that if a little bit of
abstraction is done now, then it avoids a squillion html5 apps failing
to look consistent with the rest of the system or flat out breaking as
soon as we do have a means of managing themes.
Alan.
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp