> I suppose the interface widget could be loaded in based on a config key - e.g. <attribute config_key="[Library],nav_widget">ComboBox</attribute> (or 'Sidebar' or 'TabBar')? Though this does assume that all the library widgets would all be the same - e.g. you couldnt have one tab bar and one dropdown.
But never mind, your analysis looks good.
It seams to be sensible to just double Library and fix all issues that are coming along.
Currently the skin supports
<LibrarySidebar></LibrarySidebar>
and
<Library></Libraryr>
What will happen if we have them twice? What we need to allow this?
If you are ready to make your hand dirty and dig though the Mixxx library code, you are very welcome.
You will receive all support you need on the Mailing List and IRC.
Maybe this explains. But it was done before I started to developing on Mixxx. mixxxblog. blogspot. de/2008/ 12/rewriting- library. html
http://
I do not understand this:
> I suppose the interface widget could be loaded in based on a config key - e.g. <attribute config_ key="[Library] ,nav_widget" >ComboBox< /attribute> (or 'Sidebar' or 'TabBar')? Though this does assume that all the library widgets would all be the same - e.g. you couldnt have one tab bar and one dropdown.
But never mind, your analysis looks good.
It seams to be sensible to just double Library and fix all issues that are coming along.
Currently the skin supports
<LibrarySidebar ></LibrarySideb ar> </Libraryr>
and
<Library>
What will happen if we have them twice? What we need to allow this?
If you are ready to make your hand dirty and dig though the Mixxx library code, you are very welcome.
You will receive all support you need on the Mailing List and IRC.
But first, you should setup a powerful development environment and check it by fixing an "easy" tagged bug. www.mixxx. org/wiki/ doku.php/ bugfix_ workflow
This is a good start: http://
Thank you very much in advance!