[Qt-qml] Fw: Why can't I stylesheet a font?

[Justin McPherson]

Hi,

I hear you. I think you are using language that isn't going to gel well.

The ability to parametrize your activity is always important when 
working iteratively.

Designers often get "less blue" type instructions from clients (or 
managers, much to their chagrin :)) Having to redo a lot of work for 
such trivial things is a major PITA. "Clients from Hell" has a number of 
over the top, but illustrative, examples.

It maybe that using tools such as QtCreator will be the way to 
accomplish this kind of task - however it looks as if you need some 
language support in this case.

That being said, it doesn't mean you should be trying to write a single 
Quick interface to cover all platforms, you should be writing to one 
platform (or pseudo platform - container with well defined size across 
all desktop for e.g) - and it should be trivial to create new interfaces.


- Justin





On 14/07/10 2:54 AM, ext Jason H wrote:
> I am missing like 1/2 the messages in my webmail interface. So I
> apologize for being a bit lost. I don't know why we are using the terms
> flame and flamebait.
>
> First the system palette stuff is ok. However it is completely
> read-only. It should be r/e and initialized to system defaults. Then you
> *should* be able to change it, to effect global changes in your
> application. Having it be read-only is to quit yourself with a gun and
> then shoot yourself in the foot. Oh, and it should also contain font
> information. Then any attribute that is not specified is inherited from
> this object.
>
> Hard coding is why most MS apps suck. Just try to resize some of those
> Windows dialogs. It is a major bummer most of the time.
>
> I do not agree with the statement "Then you're using the wrong tool. QML
> is intended to allow designers to do exactly that. If you want to
> replicate the 1980s world of UIs generated from data definitions and
> infinitely themable but sterile UIs, then you've missed the QML point
> entirely."
>
> QML allows for themes (or almost does) and they should be easily
> supported. This dynamic nature is only an asset to the tool. There is no
> reason why you can't hard-code everything. But the layouts in Qt are 99%
> of the reason why I still want local GUIs in Qt.
>
> I also think your use of the word "sterile" is myopic. With the proper
> structure and planning there is no reason why it would be "sterile", by
> anyway that you define it. In fact, could you explain what lead you to
> use the term "sterile" I can't follow at all.
>
> Then Ivan says:
> "I believe that this kind of "style-sheeting" is a bad idea for QML.
> As I say around the office: \"QML requires to have a mind-set change.
> Much more WebPage and Javascript oriented, then C++ oriented\"."
>
> Well CSS is a part of web pages. This kind of site-management is
> essential to responding to UI feedback in a timely fashon. Heck I
> imagine "previews" that allow you to provide a template and a live user
> interface that allows the customer (be it a paying one, the art
> department, or end user) to use color pickers and combo boxes to style
> their screens. it would not really be possible unless you search-replace
> on the QML files, rather than just change a single prefs file and
> reload. (I'd hope eventually the reload would not be necessary, and that
> you can send an event to re-import the prefs and evaluate) But that is
> future work.
>
> I still don't see why style sheets are anything less than a fantastic
> idea...
>
>
> ------------------------------------------------------------------------
> *From:* Ivan De Marino <ivan.de.marino at gmail.com>
> *To:* warwick.allison at nokia.com
> *Cc:* scorp1us at yahoo.com; qt-qml at trolltech.com
> *Sent:* Tue, July 13, 2010 12:19:41 PM
> *Subject:* Re: [Qt-qml] Fw: Why can't I stylesheet a font?
>
> [flame]
> +1 and http://doc.qt.nokia.com/4.7-snapshot/qml-systempalette.html
> [/flame]
>
> <http://doc.qt.nokia.com/4.7-snapshot/qml-systempalette.html>I believe
> that this kind of "style-sheeting" is a bad idea for QML.
> As I say around the office: "QML requires to have a mind-set change.
> Much more WebPage and Javascript oriented, then C++ oriented".
>
> Something that may also be done is to inject a Style QML object that
> carries the property that u really need to have "dynamically set".
>
> Anyway, there are QML-ways to do what you want, without breaking the
> Declarative-paradigm.
>
> On 13 July 2010 08:10, <warwick.allison at nokia.com
> <mailto:warwick.allison at nokia.com>> wrote:
>
>      > [flamebait]
>      > I have a complete disdain for hardcoding anything in a UI.
>
>     Then you're using the wrong tool. QML is intended to allow designers
>     to do exactly that. If you want to replicate the 1980s world of UIs
>     generated from data definitions and infinitely themable but sterile
>     UIs, then you've missed the QML point entirely.
>
>     --
>     Warwick
>
>     _______________________________________________
>     Qt-qml mailing list
>     Qt-qml at trolltech.com <mailto:Qt-qml at trolltech.com>
>     http://lists.trolltech.com/mailman/listinfo/qt-qml
>
>
>
>
> --
> Ivan De Marino | Software Engineer | France Telecom R&D UK - Orange Labs
> w. +44 20 8849 5806 | m. +44 7515 955 861 | m. +44 7974 156 216
> ivan[dot]demarino[at]orange-ftgroup.com <http://orange-ftgroup.com> |
> ivan[dot]de[dot]marino[at]gmail[dot]com
> www.detronizator.org <http://www.detronizator.org> |
> www.linkedin.com/in/ivandemarino <http://www.linkedin.com/in/ivandemarino>
>