KDE Core/Platform 11/PlatformVsFrameworks
Appearance
< KDE Core | Platform 11
Definition of Frameworks and Platformm
In our communication we want to use Frameworks, since this communicates the modularity of our libraries better than the term "platform", which gives a more monolithic, either-or impression.
Framework
- Useful as separate library
- platform independent
Platform
What needs work here?
The following list gives an idea of some problems we see with splitting up our frameworks: 1) needs sycoca 2) uses mimetype/xdg 3) uses kded 4) kglobal used, but only for ref/deref (which can maybe move into Qt) 5) uses kglobal (in a non-trivial way) 6) uses kaboutdata 7) should be optional 8) duplicates functionality in Qt 9) should move into its own library
Framework or Platform in kdelibs
The list below indicates our _intended_ situation.
- kdecore
- auth 1)
- compression 2)
- kconfig 1), 8)
- date 3), 8)
- io 2), 5)
- jobs 4)
- kernel - needs splitting up and further investigation