On Tuesday 19 August 2008, Hari krishna Anandhan wrote: > On Wed, Aug 20, 2008 at 12:39 AM, Aaron J. Seigo <[EMAIL PROTECTED]> wrote: > > there is a dynamic context, and i am using nepomuk to store the various > > known contexts as well as mark which one is the currently active context. > > > > nepomuk is shared storage and a way to connect data to those contexts; > > plasma is a way to manage the contexts (though not necessarily all the > > related data) and define which is the current one. > > Oh, I didn't know that nepomuk also has a shared storage *note to > self: get updated with nepomuk architecture*. I was thinking it was > just for sharing a common metadata system across the desktop
it's not only a common system, it's a common data share of this information. so things tagged in dolphin can be used with those tags in amarok, for instance. that's what i'm going for here with Contexts > >> who you are with - nearby people > > > > this is presence info, and something that should be handled via decibel > > this would require more than presence (online, offline) and maybe > things like who are in the same locality at that moment. On a side > note, it would be great if presence also has semantic type associated > with it (like free, busy, away, etc). Currently these are just plain right, that's where nepomuk comes in again; and the nepomuk team has done a lot of work on exactly this area of things (semantics for people/contacts) on the semantic side, we just need to hook it into our applications now ... > >> resources nearby - any devices attached, or network connections > >> available, etc > > > > this is the role of Solid > > I understand that Solid provides that role. But, I am talking a more > generic case, where an application is not interested in dealing with > Solid API at all, but just needs it at a very-high level , like if it > just needs to be notified when a "particular type of device" is > removed. How to handle that? Solid provides for this as well ... > > better, i think, would be to just start working on implementing the > > infrastructure bits that are missing (e.g. the geoclue integration) and > > then start working outwards from there, bit by bit. perhaps first focus > > on things like contacts<->context associations, since that's an obvious > > (and obviously useful) thing. > > cool.. exactly what i was thinking of ! > But, still i am getting a little confused here *maybe due to less coffee* > > Or Maybe, in that, I understand context to be anything that > related-applications might be interested in, like activity, location, > people nearby, any active search filter, user-modes, etc context, in the general term refers to all of those things, yes. Plasma::Context will (at least for the immediate future) restrict itself to activity and location. > And that it is more than a simple "string", it needs more : a semantic > type, unique id (in case the string text changes), etc etc this will be handled by the nepomuk integration i think. -- 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 Trolltech
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/plasma-devel
