-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey,
>> Yeah, Leo and I talked about putting together a 'dummy service' for >> it, which would allow enable/disable and configuration, and I still >> think that's a good idea, but it was decided way back when that it is >> a Collection rather than a Service, (though it does have >> characteristics of both). Also, I think it fits more as a 'local >> source of music' since one of the goals of Playdar was to make >> disparate sources all appear local. Also, for recommendations and >> such, (e.g. top tracks from similar artists), to be useful, it needs >> to be queried when the other collections are. > >> However, I feel rather strongly that being able to configure >> collection plugins in the same way that services can be configured is >> a great idea, especially with the number of collection plugins >> available now. Some Services have Collections ... I think it could stay as a Collection where it is and be enabled/disabled & configured via a Service ... could that be possible? Only thing is that I think every Service creates an "Entry" in the Internet and maybe the Collection of a Service doesn't find it's Place inside Local Music. >> Unfortunately, this is a limitation of playdar's current state. That >> said, it may be possible to create new resolvers/edit old ones so that >> this sort of query works, without having to mess with playdar-core, >> (since the resolvers determine what results are available). Using >> playdar-core and the included resolvers as is, however, means that no >> query which doesn't specify both an artist and a title will ever >> return any results, (i.e. single field matches are scored to low to be >> returned as results). If you can think of anything we could do about >> this from the Amarok side, I'd love to hear it, but we'll otherwise >> need to see how other implementations of the Playdar API work when >> they're ready. Thanks for explaining this ... would have to look into it. Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk1lTJAACgkQlZvAMV/NgGJcFACgyS849Xw79H6sm6nuHekZfcfL P5wAn0yWcuxovkK+XTGWXTdW3vxynNBW =JccD -----END PGP SIGNATURE----- _______________________________________________ Amarok-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/amarok-devel
