>
> > >There's talk of abandoning GNOME now that QT is going open source.
I really don't think it will happen.
> > >many developers- myself included- will never go back to writing GUI code in
> > >C. I know there are C++ wrappers for GTK but they're not the same as
> > >writing to a native C++ library.
> >
> > Personally, I'm still trying to decide between Qt and Gtk for an app I'm
> > starting. And, man, am I having trouble deciding. I'd prefer to work in
> > C++, so Qt holds an attraction, but the fact that RedHat/Mozilla are
> > heavy into Gtk counts for a lot, too. Oh well....
>
> Well I've stopped using Qt more then a year ago, mostly because of
> all that bickering about license, and I am afraid will not go back. It
> is a great toolkit, but in my eyes its reputation is tarnished somehow
> by all what had happend recently. It is almost like a spell.
I'm on Harmony till september or so, and before I was coding for gtk
(i'm a c developper, not c++ so harmony is new to me )). I htink I won't
program with gtk before at least 1.2. The internals are really ugly (in
the X PoV), and it's really badly documented (at least compared to Qt).
I don't count the times where looking at the code, I scratched my head
asking why -this- was coded that way. AFAI can tell, all the internals
of gtk+ where coded with the thoughts of Spencer & Peter computer network
configuration (big server, small *network* clients).
Although I think Gtk+ will have a bigger impact now, I'm not ready to
put my nose back on this mess (even if they are finding the problems
one after an other in 1.1 and eventually correcting them), execpt maybe
to work on gtk/Qt/Harmony(?) compatibility stuff... ;)
But I can understand that someone prefer programming with Gtk :)
Lokh.
