From: Rib R. <ri...@gm...> - 2006-02-06 02:24:38
|
On 2/5/06, Joe Emenaker <jo...@em...> wrote: > Daniel Appelt wrote: > > > For some reasons your changes give me compilation errors. > > Um... yeah. I noticed that. Part of the reason for this is because, when > I made he changes to the GenericDevice, I was also planning on changing > the way patches are decoded from their sysex messages. As it is now, > every subclass of Driver or BankDriver has to manuall remove the 0xF0 > and the manufacturer and device ID's from the sysex messages. My plan > was that we could have a variety of "DataModels" that would know how > various manufacturers encode their sysex data... and those data models > would handle all of the stripping of the 0xF0, 0xF7, and any > manufacturer/device ID's as well as decoding the data back into 8-bit > data if need be. > > When I presented the idea to this list, it caused a fair amount of > debate, and some devels didn't think it was a good idea, so I didn't > pursue it further. However, it turns out that the changes I made to > GenericDevice rely on these DataModels that I was working on. So, now, > I'm debating whether to just push forward with some next-generation > Device class (which would CO-EXIST with the current one, not replace > it), or whether to alter my changes to GenericDevice to use the old way. I don't really remember this discussion, but your description of data models sounds exactly like the Decoders used by the current XML driver. Perhaps we should find a way to combine the two ideas instead of having two next-generation classes trying to accomplish the same thing. |