I started korelib an experimental project (call it "research", or whatever *g*), and I wasn't very accustomed to all those licensing models back when we released the first version. Hell, I wasn't ever sure whether we'll ever get to use it in our applications or not (speaking of which, I have a personal "vision" that a shared library is worth nothing as long as no one is using it:) ), not to mention the fact that this is the first time that I know of when someone questions it's licensing.
And to answer the second part of your question: yes, theKompany will provide means for using korelib in non-GPL applications.
A new version of korelib is just around the corner, featuring Python bindings and an embedded Python interpreter. That means any application using korelib will get instant access to Python scripting, as well as the posibility of having plugins written in both C++ and Python. And no, this won't bloat your application at all, because all the Python stuff (embedded interpreter / bindings / plugins) will be itself a korelib plugin:).
The new version will have a dual licensing model similar to TrollTech's Qt (GPL/QPL/commercial), thus allowing non-GPL applications (either commercial or under an OSI approved license) to use korelib.
Slashdot Mirror
I started korelib an experimental project (call it "research", or whatever *g*), and I wasn't very accustomed to all those licensing models back when we released the first version. Hell, I wasn't ever sure whether we'll ever get to use it in our applications or not (speaking of which, I have a personal "vision" that a shared library is worth nothing as long as no one is using it :) ), not to mention the fact that this is the first time that I know of when someone questions it's licensing.
:).
And to answer the second part of your question: yes, theKompany will provide means for using korelib in non-GPL applications.
A new version of korelib is just around the corner, featuring Python bindings and an embedded Python interpreter. That means any application using korelib will get instant access to Python scripting, as well as the posibility of having plugins written in both C++ and Python. And no, this won't bloat your application at all, because all the Python stuff (embedded interpreter / bindings / plugins) will be itself a korelib plugin
The new version will have a dual licensing model similar to TrollTech's Qt (GPL/QPL/commercial), thus allowing non-GPL applications (either commercial or under an OSI approved license) to use korelib.