Ok, I'll start making the API document, and will post it when it is ready.
> that's something nepomuk needs to do, not plasma. it goes like this: > > * plasma changes activities > * plasma changes it's current context > * Plasma::Context changes it in Nepomuk (missing) > * Nepomuk signals the change out (possible now, but ontology isn't set up?) I'll probably need some help with this one. I'll check the techbase for nepomuk stuff. I have one question, though. Since we now have the activity-per-virtual- desktop, and activity-per-screen-saver possibility, should we react on changes and always expose one current activity, or list all available (currently active) activities > > > overly useful), but running dataengines OOP as a general thing would be > > > an interesting project indeed. one would hope it would make the UI a > > > > That's true, though it would be a completely different project. > > yep :) BTW, since pinda is making the DA to be network transparent, this is not something (IMO) that will be difficult to do later. (depends on pinda's implementation, obviously) Cheerio _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
