The (unknown) KDE-Platform-independent libraries

David Faure faure+bluesystems at kde.org
Fri Apr 19 07:20:22 UTC 2013


On Thursday 18 April 2013 21:06:49 Alexander Neundorf wrote:
> On Thursday 18 April 2013, Kevin Ottens wrote:
> > On Friday 05 April 2013 12:13:37 Mirko Boehm wrote:
> > > I hope the other framework developers agree when I say that the best
> > > time to begin advertising this is around the KDE conference this year,
> > > which will be held together with the Qt Contributor Summit.
> > 
> > I'm torn on that... We probably should start to make more noise toward of
> > community for sure. For third party developers it's still a bit early has
> > there's still no release in sight.
> 
> I'm not sure this is the case for all frameworks.
> E.g. karchive seems to be in pretty good shape

Not really. It needs large overhaul, to stop using Unixisms (mode_t, time_t, 
etc.) on Windows. It currently doesn't even compile on Windows.
Someone was working on that, I'll have to dig into old emails and ping him 
about that...

> I guess also itemmodels and some more in tier1/.
> What would be needed would be to have everything needed in a released Qt5
> version.
> I'd also like to get extra-cmake-modules into a releasable state, since it
> could very well be released before, which could also help to make its status
> clearer.

Alex Fiestas had another idea: how about we make a tag [once all unittests 
pass again], and suggest that other KDE modules who want to port to Qt5 
already (e.g. I hear calligra is starting to think about it), should use that 
as a basis?
This is very very similar to what we do with Qt5: we base our developments on 
a "somewhat stable but unreleased" git version, qt5.git
Of course the difference is that the API in qt5.git cannot change anymore, 
while the one in KF5 will change, and this "offer" to other KDE modules will 
come with a very big warning about that.

I think this is already more doable than an early release which blocks us from 
fixing the API ever again.

PS: parse error at the subject, KDE isn't a platform...

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Sponsored by BlueSystems and KDAB to work on KDE Frameworks



More information about the Kde-frameworks-devel mailing list