Hi guys, I'm sitting in bed hacking and I just had this giant epiphany - The MIDI output mapping table in the prefs is going to be so complicated that it's going to be impossible to use without looking at our documentation. And experience has shown, the 1% of the people that read documentation can probably write XML. And we're talking about the 0.001% of our users that will actually want to set up MIDI outputs by hand.
I wish I had realized this about a month ago, before I went ahead and wrote it. I've added a piece of complex code with many function points, and it's going to do absolutely nothing for the vast, vast majority of our users. Is there a single good reason to keep this? Albert P.S. We've put a huge dent in our 1.6.2 TODO list, and I'm going through it in my head figuring out exactly which things we need to focus on in order to finish the release. I'll send an update to the list when we enter our final push... ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
