Hi, On 18.11.04, Nicolas Évrard wrote:
Not intrusive at all. You just define you're login name and password in pytonerc and there is nothing else to do.
Actually, I don't like username and password as configuration options in the general section too much. Maybe one should create a different section for audioscrobbler. But see below.
Isn't there a command-line application for submitting audioscrobbler information. If yes, one could just call that when the playback of a new song starts (there is already support for this).
In fact, I'm using the playbackinfochanged event since the information is be sent after 240 seconds or when the track reached its middle. Correct me if I'm wrong but the playbackinfochanged event is the only one that send information about where we are in the song.
Yes, that's true.
Still, if you have already have implemented this feature, just send the patch to me or to the list and I'll have a look on it.
Ok, I'm using it for 2 days now and it works.
Here is the patch, the scrobber service module and the audioscrobber module (I plan on using it elsewhere that's why I separated them).
The separation is fine. But we should only start the scrobbler service if it is used. But... ... this all brings me to the point that it would actually be very nice, if we could make the audioscrobbler service the first PyTone plugin. The user should then be able to specify a list of plugins to be loaded in the configuration file. These plugins then probably could handle their configuration files separately. What do you think? It should not be too difficult to implement. Maybe, we have to make some iterations with the interface but in the end I think it would be useful for others as well. We could also provide a generic plugin class, which already does the setup of the threading stuff, etc. Jörg