Sorting
Some problems have arised when sorting the music list and I want to take some time now to think about how we want to do sorting.
Blueprint information
- Status:
- Complete
- Approver:
- Scott Ringwelski
- Priority:
- High
- Drafter:
- Scott Ringwelski
- Direction:
- Approved
- Assignee:
- Scott Ringwelski
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Scott Ringwelski
- Completed by
- Scott Ringwelski
Whiteboard
Currently, if you try to sort by a field that could potentially have values with similar values (track id, date added, rating, play count, etc.), when you play that song, it will hop to the bottom of the list merely because the playing icon changes from null to the sound graphic (far left column). I could fix this in multiple ways:
1) Write my own custom compare function for every possible field to ensure that rows don't hop around when played.
2) Limit the users sorting ability. Why does the user need to sort by track when it is done automatically when sorting by artist or album? We could limit the user to sorting by these methods: Title, Artist, Album, Date Added, Last Played, Rating, Plays, Skips, and a few more i'm sure. I guess there were some more that we could get rid of but I guess now that I think about it, it would really just be sorting by track.
3)Lastly, I could start making my own treeview and treemodel. The default Gtk treeview and treemodel are incredibly slow and don't have the best interface, so there would certainly be more advantages than just sorting. Although that is slow too. However, writing something like this would be quite an endeavor so maybe somebody would be willing to help me on this?
Let me know what you all think in IRC.
