Re: GTK library lifetime
 

That's your problem. You're a user.

There's tons of libraries that are glib driven that are more mature that provide the same functionality you see in Qt.

Qt is driven by Nokia. Glib/GTK is driven by the Red Hat, Novell, and the community. The fact you believe Qt is "better" is the effect of marketing.

Re: GTK library lifetime
 

one compelling reason to use gtk over qt (for me at least) is vala. much nicer language to develop in than c++.

Re: GTK library lifetime
 

Actually, being written in plain old "c", gtk allows you much greater freedom in choosing a language to create your own programs.

Re: GTK library lifetime
 

fwiw

http://meego.com/developers/meego-architecture
http://meego.com/sites/all/files/use...h-FullSize.png

Re: GTK library lifetime
 

Isn't the problem rather "Will my Hildon apps still work"? If so, the question should rather be: Will Maemo GTK+ exist in MeeGo and Hildon - even if they're community supported.

Most Hildon apps won't work on pure GTK+ and Hildon on top (out of experience)

Re: GTK library lifetime
 

That to me looks like an after-thought though sadly. Someone spoted that people would like GTK and decided to tack it on. Or in case of Moblin speculating on how to get maemo apps to it.

Re: GTK library lifetime
 

What I'm wondering is, if gtk and glib will ever be updated from stoneage versions? Even the ones coming with the N900 are already old.

Re: GTK library lifetime
 

I'm also a developer (been programming for just over 20 years).

I just think the integration of varous components seem more coherent than GTK. I'm not saying anything is wrong with GTK and the gnome desktop proves that it is still very capable (and a gnome user myself).

Admittingly I do not have a much programming experience with QT but judging by my exposure to both libraries I think QT is easier to work with.

This is just my opinion based on actual source code usage and not the effect of marketing - you insult my intelligence by your statement.

You may not know this but QT is also used by a desktop environment called KDE. It is an open-source project that uses QT at it core and many members of the community have influenced the development of QT and KDE.

One of GTK's original goals was to offer a GPL equivalent to QT.

QT was a proprietory product by Trolltech and due to some licensing restrictions many members of the community were suspicious of it. QT was under a license which meant if your product was GPL then QT was free. If you developed a proprietory product then you had to buy a license.

Eventually Nokia bought Trolltech and QT (from ver 4.5?) is now under the LGPL.


I am also a developer - I try to understand both roles.

That statement is meaninless. Windows is more mature than Linux.


You forgot to finish that sentence with "and the community"

That is plain wrong! I have studied source code and actually written some too.


As I work further with QT I might say "sh** I wish I stuck with GTK" then again I might not.

At the end of the day having both GTK and QT libraries for the Maemo/maemo/MeeGo platform can only be a good thing. It should hopefully attract more developers too.

I'm pretty sure GTK will still be a permanent library in Maemo/maemo/MeeGo and hoepfully the platform will keep evolving.

Like Hannah Montana would say "It's the best of both worlds!"

Re: GTK library lifetime
 

Good quewstion for the GTK+ and Hildon maintainers, most of them with a link to Maemo and/or Moblin anyway.

btw GTK+ and Clutter are in the MeeGo picture mainly because Moblin's maintainers will keep taking care of them.

Re: GTK library lifetime
 

One thing can be done now to help compatibility - provide Hildon alternatives/wrappers to the patched GTK+ versions (like tap_and_hold company) in one of the next updates. Keep them later in MeeGo. Inform the developers that the previous ones will be deprecated.

There. Easy.