© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> sorry for the brain dump :-/
Thank you for this, we need more of this to bring Mixxx to the max. ;-)
> The benefit of allowing skin designers to choose from a variety of navigation 'widget' formats would be that users could then pick a skin which best fits their requirements - some skins could have one-click access via fixed tabs, or a tree on the side, or some could use combobox dropdowns, etc.
Good approach, but not that easy, because currently all Library widgets are tight connected and not able to live without each others. But we should work towards changing this.
A toolbox of independent Library widgets would be really great.
> is actually possible to swap between navigation widgets.
Yes, we use the Qt MVC pattern, for the tree view and the Library, so it "should be" possible. But I am afraid that we have broken the pure MVC approach in some places, so that it is not working just as it is.
> Can we use all of the standard QT widgets in the interface?
Yes! The new combo box widget is intended to be used in the Skin above the library. It can be connected to the Mixxx Control Objects, (the Mixxx remote interface)
The library is build without these Control Objects. So you have full power of QT on one hand but not full power of the Mixxx Skin engine.
But it seams to be a good Idea to move more parts of the library to the skin engine.
> Before all that though, a first step might be to just try and get two table views (with two separate trees) side by
> side and see how well that works.
This sounds not that hard and will work from the Qt point of view.
The only problem is, that there are some places in code that assumes that there is only one view of the data and only one Table is displayed. The hard part is to find and eliminate these places.