RFC: wallpaper and containment handling in 4.2

[Ismael Asensio]

IMHO, wallpaper plugins should share as much code as possible with plamoids
alike (i.e Typical Wallpaper/Slideshow should be handled like the Picture
plasmoid), so that all the configuration is consistant between the. Also,
additional plugins or modes (eg. flickr photo retrieval, picture of the day,
etc) could be shared by plasmoids and desktop wallpaper.

Sorry if this is so obvious, as I think is the essential of plasma:
everything, everywhere, and without distinctions. Of course, I think data
engines will help this a lot.

2008/7/14 Aaron J. Seigo <aseigo at kde.org>:

> On Monday 14 July 2008, Petri Damstén wrote:
> > On Sunday 13 July 2008 04:12:07 Aaron J. Seigo wrote:
> > > * the ability for one plugin to provide multiple options to list (e.g.
> > > the current one should add "Image" and "Slideshow" to the options list)
> >
> > Can one library just export multiple plugins?
>
> that would require writing our own factory function macros (instead of
> using
> the kde ones, which are pretty much one library -> one plugin). in this
> case,
> though, it's not really necessary; one plugin should be able to support
> multiple modes just fine.
>
> to avoid loading plugins to discover these capabilities, it will likely
> require having .desktop files for each mode. a plugin can install multiple
> files, though, so the current wallpaper system could be one plugin with 2
> .desktop files.
>
> --
> 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 Trolltech
>
>
> _______________________________________________
> Panel-devel mailing list
> Panel-devel at kde.org
> https://mail.kde.org/mailman/listinfo/panel-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/panel-devel/attachments/20080714/fb93fcc3/attachment.html