TreeItemModel: Add TreeItem::getUrl/setUrl, TreeItemModel::kUrlRole and SidebarModel::UrlRole - #16835
TreeItemModel: Add TreeItem::getUrl/setUrl, TreeItemModel::kUrlRole and SidebarModel::UrlRole#16835cr7pt0gr4ph7 wants to merge 1 commit into
TreeItem::getUrl/setUrl, TreeItemModel::kUrlRole and SidebarModel::UrlRole#16835Conversation
…nd SidebarModel::UrlRole The URLs associated with the tree items are used during Drag & Drop operations to identify those tree items.
|
I think it would be good if you'd share some info about the subcrates concept, maybe in the Proposals repo https://github.com/mixxxdj/proposals/ ? Thing is, even though features like "nested crates" and "playlist folders" have been requested frequently, corresponding PRs got little traction or were closed for other reasons IIRC, so in order to spend dev & review resources wisely it would be good to come up with a design first, discuss and tweak it, then implement it accordingly. |
Good point. Not as justification, but as context (also for me, when I'll look at this in 2 more years...): I've already been part of that discussion (together with you and @daschuer) over at: Though that was 2 years ago. To summarize the results, as I understand them:
As a sidenote, I've already invested the development time two years ago, as it's a feature I desperately want & need, and am actively using myself. It is one of the reasons why I'm running my own custom build of Mixxx in production for a few years now. |
|
My suggested approach:
|
|
Thanks for the explanation, looking forward to the Proposal!
Hahaa.. |
Proposal can be found at mixxxdj/proposals#21 :) Thank you for the feedback! |
The URLs associated with the tree items will be used during Drag & Drop operations to identify those tree items.
This is required for an upcoming PR for subcrates, but is also useful independently.