On August 5, 2010, Aleix Pol wrote: > I will need to filter the plasmoids that we can add to the dashboard > because our configured file will be versioned and we need to have some > common denominator, so having a list of such would be a nice start.
if i understand what you need correctly, this will indeed be a common issue among applications, and i think it requires (at least to do it non-hackishly :) to be able to tag plugins with information that can be used in a generic fashion .. e.g. tagging the notes plasmoid in some way such that KDevelop will be able to know that it is useful to it, without the notes plasmoid having to actually say explicitly "use me in KDevelop" (since other apps will also want it, apps the notes plasmoid author doesn't know yet) > Also I need to have a plasmoid that displays information like the "Notes" > coming from the arguments passed by the 2nd parameter in ::addApplet(), is > there any that does that or it should be created? notes applet already does that, but only if a file is passed in .. which makes it a bit dodgy. that bit of the framework really ought to be re-thought out somewhat. right now we just pass in a string as the second arg and it is assumed to be a file. i was never very happy with that. -- 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