Re: [Jsynthlib-devel] Okay... so why can't I edit a patch with this?

[Brian <br...@ov...>]

>
> Do you know of any technical barrier to putting all of the various 
> checksum algorithms into one class, so that something like the 
> hypothetical EvenMoreConformingDriver could use something like:
>   setChecksumType(YAMAHA_PRE_1996);
> in the constructor? I didn't say *psychological* barriers.... I said 
> *technical*. :)

No. I think that would be a good idea if someone is willing to put in 
the time. The only barrier is how to get people to know which checksum 
to use. But if you know the different checksum types in use
and how to name them such that people will know which one to pick, 
please do. The major problem I've had so far is that most manuals don't 
say "We use the foo algorithm" for checksumming, they
usually just give the step by step algorithm. From a driver writers pov, 
I've found it easier just to take this algorithm from the manual and 
type it in for each driver, than to check all the other drivers already 
written
and try to figure which one is doing the same thing. If the checksum 
algorithms can really be boiled down to things like YAMAHA_PRE_1996, 
than that would be great.

Please note also that there is ongoing work to allow future drivers to 
be written as XML files which describe the device rather than having to 
write everything in java. If we are going to add some niceties to the 
driver writing
process it might be worthwhile to see how the niceties could be carried 
over such that they are available to XML drivers as well.

Brian