I’m on the Qt (owned by Nokia now) mailing list since I have a commercial license for a client project, and I got a very interesting email today, telling me that on its release in March 2009, Qt 4.5 will be available under the LGPL.
This is really big news. Up until the current Qt 4.4, your only licensing options are a per-seat and per-platform commercial license (which adds up if you have multiple developers and multiple target platforms, which you will do if you’re using Qt anyway), or alternatively the free option which means you use it under the GPL – meaning all your own code has to also be GPL, with an exception that allows you to publish / use software under other open source licenses too, but nevertheless it all has to be public. There’s a pretty big chasm in between these two options that in my experience a lot of projects fell into.
So, offering an LGPL option from Qt 4.5 is a major development. Qt is a really excellent library, the best cross-platform, native code widget set I’ve seen, but the licensing cost often put people off; this changes everything. I’m actually quite surprised they’re going this far – I think just changing the commercial licensing structure to be a little less multiplicative would have made a lot of people happy, but the LGPL option really turns things upside down. Essentially it means that you get all the cost benefits of the GPL version, except there’s a ‘fire break’ of open source responsibility between Qt and your application, meaning a lot more people can consider it. Nokia’s stated aims are:
- facilitate wider adoption of Qt across industries, desktop, web and embedded platforms
- establish Qt as a de facto standard for application development
- receive more valuable feedback and increased user contributions to ensure that Qt remains the best-in-class, cross-platform framework
- extend Nokia’s existing platform commitment to the open source community
I’m pretty sure this move will achieve all of those goals. It may well take a little wind out of the sails of wxWidgets, which in my experience never seemed quite as polished as Qt, but the licensing was much more favourable – although of course the wxWidgets project is still a lot less ‘corporate’, so will continue to have an appeal from feeling a bit more open.
Interesting times anyway!
January 14th, 2009 at 2:04 pm
Great news indeed!
Now Qt will play along nicely with Ogre3D’s license!
I hope to see Qt embedded in Ogre sometime soon
http://labs.trolltech.com/blogs/2008/12/02/widgets-enter-the-third-dimension-wolfenqt/
January 14th, 2009 at 2:25 pm
I think you mean Ogre embedded in a Qt window, and that’s been done lots of times (not least in the client project I refer to).
January 14th, 2009 at 3:49 pm
Wow, I think will take a lot of the wind out of wxWidgets’ sails. I guess they will not compete on features, performance, platform integration and stability now. Hopefully it will create beneficial competition between both projects.
The one I think wxWidgets might still have is its use of native widgets should give it a better level of integration with platform its running on.
January 14th, 2009 at 3:51 pm
Wow. I’ve always heard good things about Qt, but yeah I was one of the people who used wxWidgets instead because of licensing costs and the desire to avoid GPL.
Very interesting.
January 14th, 2009 at 4:25 pm
I’m one of those guys that leave Qt and started using WxWidgets because of license cost.
It’s really good news, Qt is full of features and as WxWidgets is really easy to work with.
January 14th, 2009 at 4:47 pm
@Rul: We’re already seeing integration like with the QtOgre Framework (http://ogre3d.org/forums/viewtopic.php?f=11&t=45709). Deeper integration could still be made though (but this was available before, just only to open source or commercial-license users since Qt has been GPL for years).
January 15th, 2009 at 8:00 am
@Matt: Following the link postet by Rul I think he just meant what he wrote. To embedd Qt in Ogre. To show a Qt Gui on an Ogre-surface. I don’t know about skinning features of Qt, otherwise that would be a funny feature but not really useful…