On Wednesday, December 22, 2010, Thomas Olsen wrote: > I'm guessing I could clean up some space and I suppose I would only need to > checkout a subset of libplasma?
yes, just kdelibs. all the work would be in kdelibs/plasma/, but libplasma assumes it is in kdelibs for build purposes. it is probably workable to take just kdelibs/plasma/ and muck with the CMakeLists.txt file to get it to build outiside of kdelibs, but if you can spare the disk space, it's really not worth it. the sources for kdelibs are 228MB, my build dir for kdelibs is 1.9 GB. > But I would still need someone to make a plan and mentor me through > something Junior Job'ish to start with ;-) np; a plan was in the original email ... for the first item, i suppose the non-obvious bits are how to make a syncronous wrapper around a KJob (which is done using job->exec()) and how to use QMetaObject::invokeMethod to call the new slot (which has the side of effect of making it behave like a virtual method but without breaking binary compat). the biggest work would probably be taking the contents of Package::installPackage and putting it into a subclass of KJob. that's mostly copy and paste work, and the resulting KJob subclass itself would be a private class and go into kdelibs/plasma/private/ i'd be happy to mentor you as you go and answer questions if you're interested in taking this on :) -- 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
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
