Re: [Jsynthlib-devel] Interfaces

[Hiroo H. <hir...@co...>]

Rib,

Rib> I guess we need to choose the packages where the support files for xml
Rib> drivers, the drivers written in xml, and the ruby support classes
Rib> should go.
Rib> 
Rib> For easy reference, my original recomendation for these were,
Rib> respectively, org.jsynthlib.jsynthlib.core.xml,
Rib> org.jsynthlib.jsynthlib.xmldrivers, and org.jsynthlib.ruby.
Rib> 
Rib> I believe that Hiroo suggested org.jsynthlib.jsynthlib.xml and
Rib> org.jsynthlib.jsynthlib.drivers.
Rib> 
Rib> I'd be fine with having xml under jsynthlib instead of core, but I
Rib> wondered if it might be confused with the actual drivers written in
Rib> xml.  I recommended a separate directory for different types of
Rib> drivers because the parser can't tell the difference between a java
Rib> file and a messed up xml file.  But I suppose I could easily solve
Rib> this by requiring xml drivers to have a common extension (.xml,
Rib> .device, or .driver come to mind as possibilities).

Yes. Actually DeviceListWriter finds device classes by using filename
'synthdrivers/*/*Device.class' now.  (This is the only rule of class
name for synth drivers.)  We can do same thing for XML drivers.  I think
putting all synth driver in one place would have some more benefits.

Rib> > I'll stop changing core files for a while not to create conflict with
Rib> > you.  Are there anything I can help you for the interface change?
Rib> 
Rib> It'll probably be easier if I do it all myself.  I'll try to do it today.

OK.  Happy hacking!
-- 
Hiroo Hayashi