[Qt-interest] Are there any disadvantages with OT

[BRM]

----- Original Message ----

> From: Dave Smith <dave at thesmithfam.org>
> David Ching wrote:
>   > Not to start an argument, but if I show my clients a UI I can create using
> > .NET and one of the many libraries from Telerik/Dev Express/Infragistics, 
> > etc. vs. what I can build in Qt off the shelf or with the aforementioned 
> > widget libs from KDAB, etc, I mean... there is no comparison.  Qt is butt 
> > ugly compared to to the .NET ones.  It runs faster and is cooler to develop 
> > in, but it is butt ugly.
> I disagree. I've seen several craptacular GUIs developed with other 
> toolkits, and I think it has a lot more to do with the skill of the 
> developer than the widget toolkit used.

Very much agreed. +10

Doesn't matter what toolkit you use (aside from Java, for the most part), it's very much dependent on the skill of the developer as to the quality of the GUI.
Especially how much attention they pay to the minor details - keyboard short-cuts, widget placements, etc.

Fact is, Qt does make a lot of it far more simple to develop and manage than most anything else.
Qt's functionality is on-par (and probably very superior to) that of prototyping a GUI with Visual Basic.

In fact, if you use QtCreator, you can mimic the whole Visual Basic experience - but have a far more powerful language (C++) at your hands.
I haven't seen _any_ other toolkit do that, not to mention giving you _more_ bang-for-the-buck (so to speak) since you can arrange a lot of the GUI driving via Qt Designer without having to write much code due to signals/slots.

Ben