> On 2009-09-03 19:01:20, Rob Scheepmaker wrote: > > Cool, nice work. Indeed support for drag&dropping those urls and 'opening' > > them should still be added. I've added that to my TODO. I'm currently at > > tokamak, but will be going away tomorrow morning and have some other stuff > > to do as well, so I don't think I'll be able to do this here, but I'll make > > some time next week. > > I'll create some function to the plasma-desktop dbus interface probably, > > create some small helper program that invokes this, and of course add the > > drag&drop support which is all quite trivial. This will all greatly help in > > making the remote widgets feature more discoverable and accessable.
Great :) Waiting for next week or whatever your (and mine) time permits. Perhaps you even do not need to write a special helper program then, and "exec=qdbus org.kde.plasma /Desktop openService %U" or similar (no Plasma Desktop running currently to check for real D-Bus addressing) should be sufficient. Hm, but what to do with Plasma services which are rather designed for e.g. Amarok? No idea now. - Friedrich W. H. ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/1515/#review2242 ----------------------------------------------------------- On 2009-09-03 18:23:03, Friedrich W. H. Kossebau wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/1515/ > ----------------------------------------------------------- > > (Updated 2009-09-03 18:23:03) > > > Review request for Plasma. > > > Summary > ------- > > Hi! > > With commit #1019443 to kdebase/runtime/kioslave/network (done today) I added > a new entry for "Plasma service" to the DNSSD (zeroconf) backend for the > network:/ kioslave, which means that network:/ should now show a nice Plasma > icon for such services and have a link "plasma:/hostname:port/name" connected > to the entry. > (Beware, you need to restart kded after updating your install, as the > kioslave is feeded by a kded module, which has the data in the binary (yes, > TODO :) )! Perhaps you even have to load the module manually, the automatic > load is reported to sometimes fail: > "qdbus org.kde.kded /kded loadModule networkwatcher"). > > Now, the listing in network:/ is one thing, one also wants to deal with the > service item in Konqueror, e.g. click on it or drag'n'drop it to the Plasma > workspace. The same happens if the plasma:/ url is used in web pages or > emails ("Son, here you can connect to my Dinner-is-ready plasmoid, Yours, > Mum"), or isn't this supposed to be done? > With KIO there is the need of a .protocol file which describes what the > plasma:/ protocol is about (see patch for prototype). AFAIK for such > protocols not starting a kioslave, but a helper program ("helper=true"), that > one needs to be defined here in the "exec=" line. So what would the helper > program be for plasma:/ urls? For Drag'nDrops this entry is ignored, BTW, and > just the url passed. > > > Diffs > ----- > > trunk/KDE/kdelibs/plasma/CMakeLists.txt 1019436 > trunk/KDE/kdelibs/plasma/plasma.protocol PRE-CREATION > > Diff: http://reviewboard.kde.org/r/1515/diff > > > Testing > ------- > > > Thanks, > > Friedrich W. H. > > _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
