Linked by Eugenia Loli on Mon 20th Nov 2006 16:31 UTC, submitted by elsewhere
Qt "This article focuses primarily on some technical aspects of Qt, Trolltech's cross-platform C++ toolkit which, as you may know, is the architectural core behind the KDE desktop on Linux. At the end, I show how easy it is to create a simple application without writing a line of code." More here.
Thread beginning with comment 184127
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Clearing up some FUD
by bnolsen on Tue 21st Nov 2006 15:31 UTC in reply to "Clearing up some FUD"
bnolsen
Member since:
2006-01-06

My code internals don't need internationalization.

When I want to see the condition number of the matrix I'm inverting I only need to print it out my debug in ascii. I don't unicode for any of that. Unicode is ultimately useful for interfacing, works well on the gui side. But it doesn't belong in my image processing algorithms.

Part of the bloat of Qt is that there are about 3+ ways to do the same thing. You may use the signal slot mechanism. If you don't want to use that you can override the event methods from the underlying widgets and handle events that way. If you don't like that then you can install an event filter on a widget and handle events that way. If you get too fancy with signal/slots then you end up with a signalling nightmare and issues with event tracking.

Not to mention Qt4 really bloated things by so tightly coupling everything with their MVC paradigm, especially in the Table and ListView widgets.

I mean it's all fine, there's a potential do lots of things, but I seriously question if all this featurization is really necessary and if it's really worth all the baggage that comes along with it.

I will say that I haven't really seen a good replacement for Qt yet, although I would like to spend more time with fltk2 to see if it does have enough to make it useable. I do like their KISS paradigm.

Reply Parent Score: 2

RE[2]: Clearing up some FUD
by aseigo on Tue 21st Nov 2006 16:41 in reply to "RE: Clearing up some FUD"
aseigo Member since:
2005-07-06

> My code internals don't need internationalization.

famous last words ;) seriously though, the nice thing is that QString remains amazingly fast and light so you get this additional capability for a near zero cost.

and when you do end up needing features like i18n you don't have to run and find a solution, it's already there.

there are few things as annoying as running into limitations in a toolkit, particularly when fixing those limitations would not come at an appreciable cost.

of course, for your matrix code don't use QString if you don't want to. use std::string or even char*. there's no one holding a QString gun to your head =)

> Part of the bloat of Qt is that there are about 3+
> ways to do the same thing

the 3 ways of reacting to events you outline each have distinct use cases and distinct times they are relevant. they aren't the mess of overlap you suggest. i'm not sure if you're just being argumentative or aren't familiar with Qt, but either way you missed the mark.

> Qt4 really bloated things by so tightly coupling
> everything with their MVC paradigm

bloated in which way? API? resource footprint?

if you're concerned about API, use the simpler Widget versions of these classes and you're essentially back to the Qt2/3 way of doing things. if you're concerned about resource usage, i'd suggest measuring again. for anything but trivial cases (where such numbers hardly matter one way or the other) i find the new model/view stuff to be quite an improvement here.

> if all this featurization is really necessary

of course not. it's nice, though.

> and if it's really worth all the baggage that comes
> along with it

imho, yes. and it seems many other qt4 users agree =)

Reply Parent Score: 5