Re: [Jsynthlib-devel] Two proposals

[Joe E. <jo...@em...>]

Rib Rdb wrote:
>> 2 - Is there a reason JSL *needs* to store all of the synthdriver info
>> in synthdriver.properties? Why can't we just discover them at runtime
>> like DeviceListWriter (or whatever it's called) does?
>>     
> Doesn't DeviceListWriter take a long time and cause a bunch of modal
> dialog boxes to pop up?
>   
I don't get any dialog boxes at all when I run it. Also, I just ran it 
via my IDE and it took about 2 seconds. It might take longer if you ran 
it from scratch and you had to load the JVM.... but running JSL does 
that anyway, so you're only adding a couple of seconds to the load time 
of JSL.

There are two motivations for this.

1 - First, I used to have enormous headaches when trying to generate a 
new synthdriver.properties file because, for some reason, with the IDE I 
use, the new synthdriver.properties file would get placed in the 
directory *above* where JSL would look for it when I ran the main GUI. 
Don't ask me why. I never figured out why. All I did was figure out that 
it was happening and now I manually copy the new synthdrivers.properties 
file every time I run DeviceListWriter.

2 - If we're ever going to support downloading new synthdrivers over the 
net (like Firefox or WinAmp support downloading new skins), then there 
has to be some way of dynamically adding synthdrivers *anyway*.

Plus, I'm planning on adding a start-up splashscreen and I could add a 
progress bar and a little text bar which said stuff like "loading 
synthdrivers", "loading settings", "starting GUI", etc... to make the 
wait less annoying.

- Joe