On Sun, 27 Jan 2008 23:28:00 +0100 Erik Massop <[EMAIL PROTECTED]> wrote:
> On Sun, 27 Jan 2008 07:48:03 +0000 > Steven Robertson <[EMAIL PROTECTED]> wrote: > > Atomic media (I'm open to suggestions for the name as well as > > everything else) is an ordered set of media which behaves like a > > single article of media in every way. > > "Atomic" seems a bit weird, as atomic means unsplittable, whilst you > are proposing a SPLIT-operator... Fuse the atom, split the atom... it was my idea of a pun. ;) > Is this a static list? That is, is it saved as a list of ids, or can > it change when new media are added to the medialib? In other words, > is it a mediaid pointing to an static idlist, or a mediaid pointing > to a collection? From a client's perspective, it points to a collection. From the server's perspective, I believe that for reasons of performance and simplicity the "collection" will in fact be a cached idlist. When the medialib gets updated, affected items are regenerated. This is in no way a definitive answer, and it's subject to change based on implementation details. > > > In addition, AM are subject to the following restrictions, which > > make implementing them worlds easier: > > > > * AM can not be saved. > > How does that make the implementation worlds easier? (Probably also > dependent on the static/dynamic question above.) Currently > collections are translated to queries on the Sqlite-database, so if > AMs are stored that code might remain unchanged. That line could have been clearer, sorry about that. I evolved some of the terminology as I wrote the mail but failed to update the top. metamediaids are volatile and cannot be saved. A playlist, for instance, containing metamediaids would after shutting down and restarting xmms2d simply contain invalid mediaids. This restriction makes sense when you consider metamedids as an implementation detail, rather than an end product; the ultimate goal is for the fuse and split filter operators to work with other operators in collections, because they are most useful and powerful when they are used as dynamic interfaces to the media library, like other operators. Of course, the fuse and split operators themselves can be saved, and a DAG built using them will return the same collection of music every time it is run - but the metamediaids in the list may change. That being said, a split before saving and a fuse afterward on a playlist containing mmids would work just fine. > I suppose AMs can contain other AMs in a DAG-fashion? Yep. Addressed in the other mail on the list. Steven
signature.asc
Description: PGP signature
-- _______________________________________________ Xmms2-devel mailing list Xmms2-devel@lists.xmms.se http://lists.xmms.se/cgi-bin/mailman/listinfo/xmms2-devel
