On Monday, March 21, 2011, Marco Martin wrote: > On Monday 21 March 2011, Rohan Garg wrote: > > org.calligra-suite.stage-2619, thus you will need to keep this in mind > > when accessing the interface.I'm also going to send a seprate mail to > > the Calligra guys as to why they are appending the process id, since > > it just makes dbus calls more cumbersome. > > since dbus names has to be unique, if stage isn't a kuniqueapplicaton you > have to make it unique, so that's just normal
yes, and a out-of-process plasmoid could just list all available presentations to choose from if there is more than one instance of stage running with different presentations. a little more cumbersome, but it could work nicely from the user's POV, esp as usually there's only going to be one copy of stage running and when there are multiple instances, the user can easily switch between which control to use. btw, i don't know if it's come up yet but with a DataEngine driven approach that the control plasmoid uses for all interactivity, this would make it trivial to transfer the control plasmoid onto, say, your tablet, phone, etc. with plasma installed on it and control the presentation remotely. such a DataEngine would want to advertise one source per available (e.g. opened in stage) presentation and a control service accessible via serviceForSource. -- 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