[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: My SoK project - Plasma D-Bus API
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2009-05-27 11:24:25
Message-ID: 200905270524.30726.aseigo () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday 27 May 2009, Ivan Čukić wrote:
> 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

i think there should only be one active context at a time, and since you can 
only really interact with one virtual desktop at a time (cube/sphere/grid 
effects not-withstanding) i think we should just publish the currently active 
one.

or, we could publish it per-virtual desktop as well and let apps decide what 
desktop(s) they care about? hm.

> > > > 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)

that's a good point; we could use RemoteDataEngine in the background always..

-- 
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 Software


["signature.asc" (application/pgp-signature)]

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread]