Hi. Albert Santoni wrote: > My proposed new MIDI restructuring, class diagram: > http://i42.tinypic.com/20k9bi9.png
Looks good to me. Calling it MidiDevice & MidiDeviceManager makes everything much clearer. > - What IS a MidiObject??? My guess is "the object that handles everything MIDI." Something else not designed to scale. > - I feel like MidiObject shouldn't do the MIDI processing->ControlObject > interactions itself, but I can't think of a better OO way to do it > because of scripting. It seems multiple (unrelated) objects & functions can be exposed to scripts, so why would scripting prevent doing it the Right Way(tm), especially since nearly all scripts would be tied to separate MidiDevices anyway? > and Linux, and the API is well thought out. I've never used output with > it though, but it looks OK. As long as we can send arbitrary length messages to MIDI devices, I'm happy. (Arbitrary length SysEx messages anyway; note and CC message length are fixed by the MIDI spec.) Just let me know with what sub-tasks you'd like help (and you think I could handle) when you're ready. Sincerely, Sean M. Pappalardo "D.J. Pegasus" <<--------------------------------------------------------------------------------->> This E-Mail message has been scanned for viruses and cleared by >>SmartMail<< from Smarter Technology, Inc. <<--------------------------------------------------------------------------------->> ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
