Sounds great to me, I'm looking forward to the clients that can make use of this. Actually, I've had some crazy ideas of my own on the backburner that could probably benefit greatly from something like this.
I was about to mention that it would be nice to have some sort of standard stickers, so clients can have some common functionalities, but still allow arbitrary stickers so as not to tie clients down. But then I re-read it and realized you had that covered with the xml file, glad to know we're all on the same page :) On 1/19/09, EAW <eric.wolle...@gmail.com> wrote: > This is a *GREAT* feature! I'm very excited to see this in MPD!!!!!! > > e. > > On Jan 19, 2009, at 1:01 PM, Max Kellermann wrote: > >> Hi, >> >> yesterday, I have implemented a feature that has been awaited for a >> very long time: the sticker database. It is a database where you can >> attach additional information (name/value pairs) to objects, e.g. to >> song files. The stickers are stored in a separate "sticker database" >> (SQLite internally, --enable-sqlite, option "sticker_file"). >> >> Clients may add arbitrary names and values, currently heavily limited >> by the MPD protocol (no newlines, no binary, UTF-8 only). The >> meaning of the stickers is up to the client, MPD does not care at >> all. One feature which was requested by many many users is the song >> ratings. >> >> Other suggestions were collected by Rasmus "Rasi" Steinke in the file >> doc/sticker.xml. The client devs should agree on some basic >> standards, that's why we created that file. Accepting patches for >> that file! >> >> There is the new command "sticker" which enables clients to access the >> stickers of a song file. Its operations are limited to "get" and >> "set" >> currently, no enumeration yet. It might be useful to have variations >> of the "playlistinfo"/"lsinfo" commands which include some sticker >> values, to keep the network latency down. >> >> Awaiting your comments now. This is work in progress, and the concept >> may change in the near future. >> >> Max >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> _______________________________________________ >> Musicpd-dev-team mailing list >> Musicpd-dev-team@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team > > -- > Eric Wollesen > eric.wolle...@gmail.com > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Musicpd-dev-team mailing list > Musicpd-dev-team@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
