There, SoC is over! Not much updates here along the way, but I managed to reach all my objectives, which means collections are now operational in XMMS2! More thorough testing will happen when clients start using the new API, and I will of course keep working on the project to fix things, finish the last details and help make it into the release after the next. But most of the work is over, which means it is now possible to create dynamic collections, use party shuffle playlists, query the medialib without writing SQL queries, etc. I posted a mini-HOWTO to show how to work with collections using the standard XMMS2 cli. More details can be found on the concept and the design pages of the wiki.

I posted a first version of the Collections Design wikipage, for now mainly focusing on the collection API and the development roadmap. Things are getting clearer and more concrete, thanks to brainstorming and Anders' ever lucid advice.

The implementation phase is now starting in parallel, with a merge of some refactoring of the current API as a warm-up (had been sleeping in my git tree for way too long).

School has kept me busy lately, but I finally managed to complete the Collections Concept specification page. Things are much clearer now, and I shall start working on the implementation design right away!

Feedback is still welcome about the page above of course.

There we go, starting work on the Collections project of the XMMS2 music player! I'm delighted to be able to work on a project which I have long been interested in!

In short, collections are an abstract representation of subsets of the media library, which can be used to search/query music based on filters, save groups of songs, generate playlists (either static or dynamic, à la iTunes' Party Shuffle), etc. Collections will therefore make the access to the media library both simpler and more powerful, by unifying concepts (queries, playlists, views) and allowing new features.