I was browsing my music today, wondering how to make it faster to quickly navigate, and I realized a good way that a media library could be integrated. Basically, it would involve modifying the Albumlist extension in a few ways:

1. Duplicate the Albumlist panel three or four times with individual settings for each.
2. Have an option to make the albumlist based on only the currently selected playlist, rather than the entire database (and have the albumlist panels automatically update as the playlist changes).

Basically, what this would do is let you make selections in each of the panels, which would then progressively filter eachother as the playlist updates.

Not sure if that was really clear, but it would be nice to know if this is possible. Of course if I could program, I would do it, but unfortunately I have very little (if any) programming knowledge.

You would have to set up some sort of heirarchy (sp?) for the different panels, though. For instance, say I select something in albumlist A, then that creates a filtered playlist. The display in albumlist B updates to reflect your choice in albumlist A. You select something in albumlist B, which in turn updates the playlist. Now what happens to albumlist A? Does it also update to reflect the new playlist? Would we want that to happen, or would we want albumlist A to always reflect the original playlist? Also, on a related note, what happens to A when it updates the playlist itself? Wouldn't A automatically update to reflect the changes to the playlist, which would in turn create a rather meaningless albumlist display?

The other issue I see is the speed of refreshing the albumlist tree. I have no insight to offer here other than I think it might be significant, especially with multiple trees being refreshed.

Sorry if it seems like I'm picking on the idea too much. I'm really just thinking through it and typing at the same time. It does sound interesting, if not difficult to implement. (also, now that I think about it...I'm not too sure how the behavior you described is different from the regular behavior of the album list)

I see what your saying, and this can be solved by giving each albumlist its own settings. So, you could set one of the albumlists to be "root" list which would be based on the database. The other ones, then, would be set to variable 1, variable 2, etc.

Edit: The difference in behavior is that instead of a multi-branch tree, there would be mutliple lists. That way, it keeps to size of the list to a minimum, without having to deal with expanding and closing branches.

This already possible

Yes, we know that. But can the content of the panels be linked (filtered) as described above?