On 09/03/11 15:38, Joe Emenaker wrote: > Well, I was using the space as quantifiable evidence that the codebase > is so heavily skewed toward synthdrivers... by a factor of about 6:1. > So, svn checkouts take 7x as long, making an archive of the code takes > 7x as long... etc. Every time I zip, unzip, or checkout a copy of the > code, "core" goes by pretty fast, and then I get to watch this endless > string of synths where I'm thinking "Wow... look at all of these synths > that I've never owned, never *will* own, and don't even know what they > look like... good thing I've got drivers for 'em...". And this > lopsidedness is just going to get more-lopsided. Although in the jar that people download its about 1.5Mb for groovy and a few hundred k for JSL including all drivers IIRC. so wierdly its lopsided in the other direction as far as users are concerned. > > Also, it just irks me that we have to generate a synthdrivers.properties > file any time a driver is added. The ".properties" system is just so... > yucky. JSL should be able to quickly and dynamically find all of its > drivers by itself.
Yeah you could imagine a nice web service which accepts a device query string and then provides a list of one or more drivers that claim to support it. Although the downside on this is that it would require that a server was maintained, and I notice that the patch upload website's search box doesn't work. So relying on a web service possibly isn't something that this project has historically been good at? ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
