On Wed, 21 Sep 2011 16:11:03 +0200, Thiago Macieira wrote: > First, that's extremely vague. I can simply answer that with QML it's > easier to "do things against the toolkit", so it should take less time > than it has taken previously.
I don't want get lost in a discussion of specific problems - just to give you an idea: I had to implement an application where the customer wanted to have a user interface with rounded borders ( a requirement from the marketing ). So the development decided to use a style sheet with backgrounds with rounded borders. Now we had a custom widget, where a spectrogram was displayed ( done with QwtPlot, but this doesn't matter ). Because of aesthetic aspects and we couldn't waste pixels ( Qt/Embedded on a small display ) it was not acceptable to avoid the rounded corners by having contents margins - the spectrogram had to fill all pixels inside the borders. So I had to solve the following problems: - How to know radius and width of the border to clip the spectrogram - How to rearrange the drawing order, so the the background color is below and the border is painted above the spectrogram( antialiasing ) There were a couple of other problems I had to solve ( f.e. performance issues because Qt::WA_StyledBackground has an effect on update regions ) and in in the end it took me a week. On the other side I needed less than a day to implement all the usual UI stuff ( menus, widgets in layout + signals/slots ). Again: this is no positive or negative statement about QML. All I want to say is that every type of application I was working on has its own very special weird requirements, that take the majority of my development time. That's why I would always decide to use the API that helps me best to do these things. Uwe _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
