On Monday 24 November 2008 20:24:59 Aaron J. Seigo wrote: > On Monday 24 November 2008, Fabrizio Montesi wrote: > > We would need to support the loading of Jolie scripts anyway (for more > > complex cases or coding distributed behaviour as backend to a plasmoid), > > so while this option (the XML one) could be nice I'm wondering if we > > would end up with too many ways to do the same thing, and I don't like > > this feeling. ;) > > yes, Jolie scripts don't look all that difficult to do and we should be > able to provide a number of stock scripts that cover the common cases, > preventing developers from having to dip into Jolie scripting unless they > are interfacing with something that has quirks. > > so let's just KISS
Let's recap a bit about ::access. For quirk-free things, one liner: Service::access(Service::Location& location, Service::Protocol protocol = Service::Protocol::Native) Where Service::Protocol::Native is what you need for accessing a Plasma::Service published on another machine. For adapters: Service::access(QString& jolieScript) // perhaps to find a better way than a QString? An adapter could require some initialization data (like the URI of the service to bridge to), meaning an initial call to its "initialize" operation just after access-ing it. Easy, but it's not a one liner. _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel