On Mon, Dec 03, 2007 at 12:45:30AM -0500, Albert Santoni wrote: > The library track table uses QT4's model/view architecture, and > apparently the underlying data structure for the library is actually a > playlist. This is totally unnecessary - The underlying data structure > for the library should be the TrackCollection, as that's what it was in > 1.5.0, and that's the whole point of the class. This class confusion > happened during the summer when the library code got all shuffled > around.
I'm not overly familiar with this part of the code, but having looked at it briefly, I can't see why you say wrapping playlist is not the right thing to do. Can you explain? As far as I see, the difference between a TrackCollection and a TrackPlaylist is order, both of columns and of rows. Maintaining an order of rows may be strictly unnecessary for the Library view, but does it matter? Presumably the Playlist model is the right one for the playlist views, so why not use it for the Library view too? I'm probably missing something obvious, it's been a long day... Ben ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
