On Thu, Sep 9, 2010 at 10:31 AM, Sean M. Pappalardo - D.J. Pegasus <[email protected]> wrote: > Taking this on-list. > > On 09/09/2010 07:24 PM, Albert Santoni wrote: >> >> Two main points: >> >> 1. What controller currently has a problem? I was under the assumption >> that we fixed all the Hercules devices and the SCS.3D. I don't really >> care about anything else at this point because we can't QA anything >> else. C'est la vie. > > Ok that's a good point, and maybe another vote for a separate "known to > work" list?
We tried that, and it didn't work. "Known to work" is too vague unless you can comprehensively test every button and knob on a controller, and to date, we haven't communicated that definition of "working" to our testers in the community. On the website for 1.8, I've listed all our existing supported controllers as "Community Supported". For 1.9 or 1.10, we can work out what "Officially Supported" means. The main issue I'd like to resolve is this terrible problem where user X downloads Mixxx, plugs in their controller which is supposed to be "supported", and function X of the controller doesn't work. I have some ideas for how to improve the situation, but we've digressed a bit here. > >> 2. It's a bit late to be worrying about this stuff. I'm going to give >> the order that 1.8 is to be declared finished soon... > > True but I thought that with Guy's recent bug reports and the recent commits > that things were still up in the air. So what is 1.8 going for then in > regards to this? 1.7 compatibility? > Leave it the way it is and wait for users to fix their controllers. We've already fixed the controllers that we can... (and it's not like we owe Vestax anything here) Albert >> Sean wrote: >> >> > Hey guys. >> > >> > I'd like to propose a meeting (or maybe just a mixxx-devel discussion >> > thread?) so we can conclusively decide on how exactly the jog and wheel >> > behavior should work in v1.8. >> > >> > Right now, we have a design conflict between "make it work like 1.7 so >> > existing mappings don't break" and "make it straightforward/correct" >> > which implies that any then-broken device mappings need to be fixed in >> > script. >> > >> > On that note, we really should add a "known to work" device list >> > separate from the "supported" device list, so that "supported" means an >> > active Mixxx developer has the device and we maintain an official >> > mapping for it. "Known to work" means user-supported, so don't file >> bugs >> > about these devices. (We might even go so far as to not bundle >> > non-official mappings and instead provide a link in the prefs to the >> > wiki and/or mapping forum.) >> > >> > Thoughts? >> > >> > Sincerely, >> > Sean M. Pappalardo >> > "D.J. Pegasus" >> > Mixxx Developer - Controller Specialist > ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
