-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey,
> I'm against the idea of having a playdar service just for > configuration. Unless it has actual usable content, like for instance > your own GPodderService, it should not pollute the internet service > list. Configuration of a collection can be done using the > CollectionDelegate actions (they appear when hovered over the root > items in Local Music. If requested we can make a page for it in the > settings. There is also a branch by Rick that allows complete > disabling on a plug-in basis [1] this can support configuration for > each individual plugin, like playdar. > > [1] > http://quickgit.kde.org/?p=amarok.git&a=shortlog&h=refs/heads/rickc-pluginselection as the Branch is merged already some time, I was wondering if it would be possible to reenable PlaydarCollection, but not "enable it" by default. Means, that a User could (if he/she wants) enable Playdarcollection from the new Plugins Page in Settings. It would be a pitty to leave the PlaydarColllection Code "force-disabled" even in 2.4.1 Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk2EqlEACgkQlZvAMV/NgGJFsACfV8AxW3ZbIMma5PFsBjFh0csA d90An3Qd76KoIjfeRjdt8iKRbRBzkPGO =lThN -----END PGP SIGNATURE----- _______________________________________________ Amarok-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/amarok-devel
