@pingufunkybeat That is not really correct. kdelibs is LGPL, the rest is mostly GPL.
Though there is one thing you have to keep in mind, kdelibs can use parts that are GPL, so if one wanted to use kdelibs commercially they would have to make sure that any dependency is LGPL or a weaker license as well.
I also find it sad that Qt gets ignored, because I think that it is a lot better than what I have read (! not used it myself) about GTK. Take this [1] and this [2]. Yeah it is great that GTK _finally_ catches up, but come one I did not experience those issues with Qt since ... ages, I can't even remember such issues.
And in fact a lot is happening in Qt-land, just read Qt Labs. My personal favourite -- even tough it was not that much work for them and is not complicated at all -- is the way the wrapper for OpenCl works. That is OpenCl done easy and clean.
[1] http://live.gnome.org/MathiasHasselm...wLayoutManager
[2] http://blogs.gnome.org/tvb/2010/04/1...ayout-for-gtk/
Though there is one thing you have to keep in mind, kdelibs can use parts that are GPL, so if one wanted to use kdelibs commercially they would have to make sure that any dependency is LGPL or a weaker license as well.
I also find it sad that Qt gets ignored, because I think that it is a lot better than what I have read (! not used it myself) about GTK. Take this [1] and this [2]. Yeah it is great that GTK _finally_ catches up, but come one I did not experience those issues with Qt since ... ages, I can't even remember such issues.
And in fact a lot is happening in Qt-land, just read Qt Labs. My personal favourite -- even tough it was not that much work for them and is not complicated at all -- is the way the wrapper for OpenCl works. That is OpenCl done easy and clean.
[1] http://live.gnome.org/MathiasHasselm...wLayoutManager
[2] http://blogs.gnome.org/tvb/2010/04/1...ayout-for-gtk/
Comment