On Friday 09 March 2012 17:58:35 Martin Gräßlin wrote: > the March Iteration of splitting kdelibs [1] involves KWindowSystem. As I > was appointed to be responsible for that I will concentrate my work on this > epic starting from next week. Any help is more than appreciated.
Glad to read that. In case you missed it though, Aaron started a bit on the split, so there's already something in staging/. Probably worth talking to him in case he had plans not yet available in the repo. > What I plan to achieve: > * getting kwindowsystem as a Tier 1 library (currently it's planned as a > Tier 2) I honestly don't remember the reason why it was tentatively earmarked Tier 2. But if you manage to make it Tier 1, all the better. > * moving Plasma::WindowEffects into this library > * reaching a test coverage of > 90 % Thumb up to that. :-) > * removing all deprecated atom hints/legacy functionality etc. > * clean up coding style ;-) > * where it makes sense introduce Q_PROPERTIES > > A few things I will have to discuss with the KDE Frameworks maintainers. > E.g. I think we should drop the Windows and MacOS X implementations of > KWindowSystem as it is too close to our X world. Disclaimer: I'm close to clueless about KWindowSystem and friends, mainly shuffling options here. I'm wondering if that's a wise choice or if it would be better to make the API of KWindowSystem less "X oriented". Especially if it lands in Tier 1 I would see a strong value in the possibility of using KWindowSystem API on non-X systems. I count at least Wayland based systems which will appear at some point, we'd better be ready for them if possible. Also the Windows and MacOS X support are an interesting asset for the library reusability. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud patron of KDE, http://www.kdab.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
