On Sat, Aug 30, 2008 at 8:49 PM, Aaron J. Seigo <[EMAIL PROTECTED]> wrote: >> Now, suppose I get an IM from one of my official contacts (via the >> Kopete in OfficeActivity); how will that chat session be tagged? The >> Kopete in HomeActivity would be wise enough to not tag it with >> HomeActivityContext as that contact is not associated with it. But, >> how can Kopete in OfficeActivity handle it, without knowing what >> context it is associated with? > > an app would be free to associate itself with any context it wished; this > would move it out of sync with the rest of the desktop, of course.
I don't get it. How can an app think of arbitrarily associating itself with a context without worrying about the rest of the desktop? It must be the user who does that by indirectly assigning acitivityContext to an app, by running the app in that activity. Now, I am confused. Something is getting lost somewhere ;( > if you look at the Plasma::Context class draft in libplasma this is also > evident. I had taken a look at it the moment you added it to SVN ;) I understand that it has methods to createActivity, list available activities and to get/set current activity. What I didn't understand is how you plan to tackle the scenarios i explained? like below... >> Scenario 2: >> Assume that the user is currently in OfficeActivity. At that moment, >> KGet (the download manager) is scheduled to be launched in >> HomeActivity and download a file. So, how can it get hold of the >> HomeActivity to tag the downloaded file with it, if only the current >> Activity is exposed? Lets talk technically ;) Of course, KGet can get a list of activities and also the current activity (which is OfficeActivity). But, it was scheduled to be launched in *some other*Activity which is not the current activity. so, how will the KGet know what context it should associate itself to? Should it get hold of the activity when it was scheduled itself? Would that not add more complexity to the whole thing? Or am I thinking too much ;) >> If Plasma just publishes the current activity, how can it get hold of >> its associated activity to tag it? > > i think i see the misunderstanding here; my proposal is: > > * nepomuk holds all the known activities in the store, organized according to > whatever the ontology ends up being > > * plasma designates one of these activities as the current one > > the second point does not interfere with the first one; all activities will > always be accessible via nepomuk. they'd have to be, in fact. > no, plasma *defines* which is the current activity and publishes that > information. the rest of the activity nodes remain in Nepomuk. (how would it > work at all if they weren't?!) No, I completely understand what you were saying...What I am saying is that there may be background or batch processes, where this *might* break if it is just plasma which manages this whole thing, without KWin knowledge or system-wide usage especially when apps come into picture (not sure, just looking for possible scenarios. i am not able to put my finger exactly on the problem ;( Can you explain your understanding with some examples? Please .... _______________________________________________ nepomuk-kde mailing list [email protected] http://lists.semanticdesktop.org/mailman/listinfo/nepomuk-kde
