[Development] Qt5 missing features
charleyb123 at gmail.com
Thu Apr 12 18:30:08 CEST 2012
> <snip, "theme" GUI interfaces for QML>
> A theme manager will make the things much more simpler and clear for the
> user and
> when it comes to add support for other platforms. <snip>,
> Let me try explain more:
> >From user perspective: <snip, want to re-use controls with different
> >From developer perspective who wants to add support for another platform
> <snip, re-using controls on new platforms>
> I want to specify simple attributes to the theme manager and it should do
> the magic for me,
something similar with Qt Style Sheets, of course now you'll say that it
> was too complex
> and almost nobody use it, I agree that it was complex but something
> simple must take
> its place, because I believe that something is better than nothing :) !
We have the same code on "touch-interfaces" and desktop. We need this.
We're using Qt Style Sheets, and they work ok. (Could be more elegant,
but is good enough, and it *works*.)
IMHO, it seems like this "theming" and "styling" thing should be so much
*easier* with QML. But, I'm not seeing approaches (yet) on these lists
that will work for us.
This is not a complaint: The QML declarative paradigm is new, and we must
think about these theme-issues in a new paradigm. (This is a very positive
But, my point: We need *ANY* "theme/style-convention" that *WORKS*. I
explored many designs in the "way-way-way" past, and they all worked to
varying degrees of success (so we have lots of options):
Summary: We (internally) are pursuing theming-and-styling through
centralized convention with our QML components. Because we must enforce
these types of conventions ourselves, things like the "QML desktop widgets"
don't exactly work for us, because they don't follow our theme-conventions.
(Recall that *by-definition*, "themes/styles" work *only* because
components follow a convention.) And, we've not fully established what
*should* be these conventions (they are in "flux"), but we *know* we *need*
So, for us, if it can't be "themed", we won't/can't use it. Period.
YMMV, I'm not-at-all disagreeing with other approaches, and understand why
graphic designers are writing custom QML components for their own purposes,
without centralized options for "themes/styles". That's not us, though:
Even for our "highly-custom" applications, we *demand* a single location
to maintain the "default-font-color" for the application.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development