[Panel-devel] Plasma and Amarok
Leo Franchi
lfranchi at gmail.com
Tue Jul 17 00:59:33 CEST 2007
On 7/16/07, Aaron J. Seigo <aseigo at kde.org> wrote:
>
> On Monday 16 July 2007, Maximilian Kossick wrote:
> > > the downside to this approach is that, while simpler to use, it means
> > > that it's an all-or-nothing approach ... it wouldn't be possible to
> use
> > > DataEngines for plasma in amarok and vice versa as a side effect of
> > > setting up separate applets.
> >
> > How about using additional constraints instead of changing the service
> > type? Amarok could add a constraint [X-Plasma-Domain] == 'Amarok' to
> > KTrader queries and only get results that were designed for Amarok.
> Plasma
> > would not use the additional constraint and could load Amarok's Applets
> and
> > Dataengines.
>
> heh.. i was just talking with Ian on irc about this and sent a similar
> email.
> it certainly is an approach with merit and potential.
>
> > Some of Amarok's dataengines are probably going to link to libamarok, so
> > Plasma shouldn't load them...i'm not sure how to solve this...maybe
> another
> > constraint?
>
> this shouldn't be a problem, as dataengines are loaded on demand by
> applets.
> plasma doesn't load any engine until it is requested. moreover, if the
> dataengine exists, then its library dependencies also must exist ... the
> only
> issue would be one of overhead, unless libamarok operates under the
> assumption that only one copy of it is in use at a time (though i would
> imagine that is not the case)...
>
> so as long as no applets that load an engine that links against libamarok
> are
> loaded, it's really a non-issue. personally, i'd like to see dataengines
> proliferate in this manner as it would make it easier to write
> desktop/panel
> components for specific applications.
this seems like a cleaner solution than changing the ServiceType on demand.
it would definitely allow for more flexibility, after all, amarok *is* able
to display plasma applets perfectly well. and as you so clearly state, the
other way around is a non-issue as unless the user loads amarok-specific
applets, nothing would happen (and if he did, well, they would be pretty
useless).
i'll take a look at this too, doesn't seem too outrageously complicated.
leo
> --
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
>
> Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
>
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-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/amarok-devel/attachments/20070717/68ddc11e/attachment-0001.html
More information about the Amarok-devel
mailing list