Intended organization of KDE Frameworks

[Aaron J. Seigo]

On Tuesday, June 7, 2011 08:39:58 Inge Wallin wrote:
> So a well defined API that applications could use, and a well isolated way
> to include a set of implementations would be nice.  We are dealing with

the best way to make this happen is to create a concrete plan and propose it. 

for inspiration: at Platform 11, a couple of teams spent entire days going 
through every single class in kdelibs and entry in kde-runtime to catalog what 
is what. the results are on spreadsheets:

https://spreadsheets.google.com/spreadsheet/ccc?key=0AhQ1BhQL6D9wdGpvOHN0N0xRZVBGU1c3ZmdiaXZORUE&hl=en_US&authkey=CKTcjdgP
https://spreadsheets.google.com/spreadsheet/ccc?key=0Am2uzNh0KAtpdFVaRkMtMXZEcC00MEE0dzhrbWV2Nnc&hl=en_US&authkey=CI_3zNMC

these were then used to build up answers that are workable and make some 
sense.

it's work, but necessary work to turn a good ambition such as yours into a 
reality. we'll have a fair amount of time to do the actual work after 4.7 
branches, but we need to have concrete plans so we know what we are trying to 
do.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20110607/ad081f5c/attachment.sig>