[Qt-interest] C++ or QML

[Carsten Breuer]

Hi Thiago,
hi all,

> But please don't go overboard and say I claimed that we're not fixing bugs. 
> We're fixing bugs, as much as possible. When people complain that bugs aren't 
> getting fixed, it's usually because our priorities and those people's 
> priorities don't match.

I understand that, since we all have to set our priorities
in some way. I also know that the developers fixes a lot of bugs.

> Forget styling and use QML.
> 
> Qt classic widgets were made to have native look and feel. They were not made 
> to be tweakable -- that is the opposite of native look and feel. That's why 
> the use of stylesheets causes such a slowdown.

Agreed...but: I had to develop a application that matches the
consumer interface guidelines of my company. There was no room
for discussions about "native look and feel".

Stylesheets was the killer tool for me to meet the CI in a very
short time. I had no glue about css when i have started and
never have worked with QT before. So i got a KDAB training
and then i start hacking. I would never ever got that with QStyle and
i wouldn't even try. So for me, stylesheets are great and they should be
better documented and of course...should work.
Back to the original posting: I would never ever use them on embedded
devices.

> If you want to change the look, you should use styles, not stylesheets, or 
> paint the widget yourself.

Nope. Styles sucks and i'm to lazy to paint the widgets by my self
if i can solve it with stylesheets. ;-).

> But, anyway, precise "how I want it to look" is exactly what Qt Quick is 
> about.

OK, sound good.

>> If you want a component that acts like excel, this is going worse.
>> In C++ you can do that. what's about QML?
> I don't understand the question.

What i was trying to say is:

If the customer want a grid that behaves like microsoft excel,
it is pretty hard to solve this in QT. I had expected that this is
a common request to the QT developers, but emulation of different
navigation types are not implemented yet and are hard to do so.
Even displaying floats with more then 2 decimal points or the
use of different hotkeys for different models are pretty hard to implement.

> You'll see I did not intervene to promote Qt Quick. I just replied to answer 
> to an unfair question.

Well, i think it was important to discuss this here and
thanks for your reply. BTW: The question was not unfait ;-))).


Best Regards,



Carsten