We all know that Qt is great, but we also know that it can't possibly cover all use cases. Fortunately there are plenty of third party libraries based on Qt, which fill a lot of gaps, so you don't have to develop everything yourself.
Finding these third party Qt libraries can be a challenge, though. To address this we started a project to create a curated archive of all relevant Qt-based libraries some time ago (you may want to think of that as CPAN for Qt).
We have reached a state now, where the necessary infrastructure is there, and it's starting to become useful for production use. You can find the web site at inqlude.org.
To make this information more complete, I would like to give this a focused push now. My goal is to get all relevant Qt-based libraries listed by end of the week.
So I'm looking for 3rd party Qt libraries.
Are you releasing a Qt-based library? Do you know of libraries, which aren't listed yet?
If you do, please get in contact with me and let me know what's still missing. You can also create patches for the meta data, which the web site is based on. You'll find instructions on the web site.
If you want to get involved with the project you can also subscribe to our mailing list inqlude@kde.org.
Inqlude is meant to be open to allow everybody to participate on the same level. The infrastructure is free software. It's run by the KDE community, but we intend to cover the full Qt spectrum.
Let's make this a place, where Qt developers can easily find and get access to the full power of the Qt ecosystem.
If you have any comments or suggestions, don't hesitate to contact me.
Great initiative. I hope I have the chance to contribute some day.
ReplyDeleteI'm sure you already know about this list:
ReplyDeletehttp://qt-project.org/wiki/Category:Add-ons
I didn't see libqxt on either list: http://dev.libqxt.org/libqxt/wiki/Home
ReplyDeleteDo you have any plans to distinguish the libraries on whether they rely on KDE libs or not?
It's one of the open question, how we show dependencies between libraries. I don't want to implement a full dependency engine. For installation we rely on the native package managers. But it still would be useful to show some dependency information on the web site.
DeleteMaybe a concept like KDE Frameworks 5 uses it with different tiers, which indicate if and to what level other libraries are required, would be useful.
I don't intend to treat KDE libraries in a special way, though. What we have to solve for them we also have to solve for all other libraries.