[jmarshall]

Hi xexe, thanks for the post.

What would be _fantastic_ is if you could get me a copy of your database so that I have a nice, large, real user database to play with.

This will ensure we can optimize the initial listing (most important being the title listings) speeds - my main idea here is to fetch minimal info (i.e. just enough to display and sort the list) and then background fetch the rest in chunks.

Smartplaylists/Filters is something that's going to take a lot of work to get right (at least from a user-interface perspective). Any ideas you have to make this process easier for the user would be most helpful! Obviously the simple stuff (like allowing you to place a smartplaylist wherever you like in the hierarchy, rather than under the "playlists" node) is easy to take care of - the tricky bit is the interface to construct those filters. If you have ideas on this, I'd most welcome them.

The cool thing with CouchDb (if we choose to go with it) is the queries are written in javascript, and are stored in the db itself, which is accessible via a webinterface. You can construct views directly in the couchdb webinterface, so hopefully we'll have some way to allow power users such as yourself to setup views (aka filters) directly and have these show up in the UI automatically. Not quite sure how this will be done though at this point!

Cheers,
Jonathan