On Tuesday 24 September 2013, Aaron J. Seigo wrote: > as i write this, the idea of a hybrid package becomes more and more > desirable sounding. with a different main script, it should be possible to > launch the same UI but without it being an actual plasmoid. > > this would also change how plasmoids advertise they can be in the system > tray: they would add Plasma/Systemtray (or whatever) to their > ServiceTypes. there would be a PackageStructure for these that would load > an alternate mainscript (which could be defined in the metadata.desktop > just as we have now).
It's an interesting concept. and yeah, i don't see much other clean solutions besides having what is in the systray not a palsmoid strictly speaking. So, the only real difference for what the qml side is concerned, is having or not the "plasmoid" global object. that would mean: * forbid plasmoids that are intended to go in the systray to refer to "plasmoid" anywhere in the code. * if what changes in the mainscript, allow there, forbid in all other qml files * giving a plasmoid object never the less: and it would be the one of the systray itself. In the first two options i can see many very subtle bugs popping up, for plasmoid not being found in the context. the last one is interesting, even tough poses some interesting problem on what plasmoid properties mean: like "expanded" is usually when the applet is either in full view in the desktop or as a popupapplet with the popup menu open... but for what plasmoid in the systray is concerned, it is "expanded" only when both the systray popup is open *and* is displaying that plasmoid in particular hmm, interesting problem :p Cheers, Marco Martin _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
