[Panel-devel] Amarok & plasma themes

Leo Franchi lfranchi at gmail.com
Thu Aug 2 17:18:38 CEST 2007


On 8/2/07, Aaron J. Seigo <aseigo at kde.org> wrote:
>
> On Thursday 02 August 2007, Bart Cerneels wrote:
> > 1. Backup of settings and the kiosk-tool. These deal with the rc file.
> > An rc file should contain settings of only one application. The kiosk
> > system is complex enough as it is.
>
> kiosk isn't particularly relevant here (it's pretty straightforward
> still),
> but the backup of settings might be slightly annoying (though that's
> certianly a very small percentage of use cases; how many people will
> backup -just- their amarokrc but not the rest of their configs?) ...
>
> this means coming up with a nice solution for use cases such as krunner
> which
> must use plasmarc and preferable (e.g. as a requirement) it should not
> need
> to know about plasmarc.
>
> > 2. What if many other applications start embedding plasma? plasmarc
> > will contain settings of all of them. What's the use of separate
> > rc-files then? Imagine the clutter and user confusion.
>
> same can be said for any such file, including kdeglobals. plasmarc is used
> by
> libplasma, which should be self explanatory from a design perspective.


i think editing plasmarc should be fine, so i'm gonna side with maxx_k
on this one. if we provide easy configuration from the Amarok GUI the
user never needs to know
that the settings exist there, everything will work *by default* and
*transparently*

> And for drag'and'dropping applets to the plasma corona (desktop) I
> > suggest a system that uses plamoid packages that are included in
> > Amaroks binaries. So d'n'd would be logicly the same as installing a
> > plasmoid with GHNS.
>
> essentially, yes. plasma is already for this, amarok just needs to ship
> said
> plasmoids.


yes, i have been meaning to look into the packaging/plasmoid stuff,
but honestly just haven't gotten there yet. also, looking at what i
want to do next
i'm not going to get there for a while yet.... so anyone that wants to
pick this stuff up is more than welcome, i can't be everywhere :)

> I guess the dataengines would have to be available
> > outside of Amarok, maybe even by default.
>
> well, yes, they have to be in order to be found. they are plugins that are
> loaded via kservicetypetrader.
>
> > Is there a DBUS API for adding dataengines?
>
> engines are loaded on demand by applets that use them. there is no need
> for a
> dbus api.


regarding the dataengine-outside-amarok thing, i'm not sure how we
want to deal with this. dataengines are always available---if the
desktop plasma loads
an applet that requests an amarok dataengine, it *will* be loaded. question
is, do we want to elegantly not do anything
if amarok is not running? also, what about if amarok *is* running and
plasma loads an amarok applet? ideally, it would work just as it would
inside amarok.

leo

> --
> 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
>
>
>


-- 
______________________________________________________
Leo Franchi                    angel666 at myrealbox.com
4305 Charlemagne Ct         lfranchi at gmail.com
Austin                                 cell: (650) 704 3680
TX, USA                              home: (650) 329 0125
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/panel-devel/attachments/20070802/fa9b6590/attachment-0001.html 


More information about the Panel-devel mailing list