playlists in ML are a hack job
It seems like the playlist view in the ML hardly had any thought put into it, no offence. All it does is list the contents of a regular old playlist. It doesn't take advantage of any of the ML's features. None whatsoever.
First of all, it already looks almost the same as the smartlists, why not just make it exactly the same? This way we could browse playlists with the three pane view, click the column heading to sort, search within a playlist, and so on.
Also, why doesn't it link up with the ML database? Changes to ML entries should be passed over to relevant playlists. If the ML registers a change of metadata, the playlists should be updated. Try changing some metadata for a file that's already in a playlist. See how the playlist doesn't pick up on the new info? That's a bad thing, especially since the ML does find the changes.
|