From: frankster <jsy...@te...> - 2011-09-23 15:14:44
|
On 09/22/11 22:41, William Zwicky wrote: > On Thu, Sep 22, 2011 at 9:27 AM, frankster<jsy...@te...>wrote: > >> On the subject of bugs, as input to this discussion and I guess to help >> with the 0.21 release notes, I have been through the cvs list and made a >> list of user-visible fixes/changes since I subscribed to the jsl mailing >> lists at the end of august; no doubt there have been various other >> patches since the 0.20 release but the sf.net web interface is too much >> of a PITA to look back through 6 years of cvs list archives! >> > Awesome work, frankie. Have things settled down? I'd like to post 0.21 > soon. > There is definitely one bug I want to fix before 0.21 - its the issue where the patch editors ask you to save changes even if you haven't modified anything. I would also like an up-to-date synths list available to coincide with the time of the release. I'll see if this can be hosted on the project sf.net web page and if I have access to do this. On the subject of the auto-generated synths list, if i remember correctly there were two outstanding issues with that. 1) the "comment" field. In the long run this might be solved by a config file if we have modular drivers, but for now I think this should be solved by adding a comment field into every driver in the same way as the info text. the comment field can be called "support info" or something, and its entire purpose is to document the level of support of a driver for inclusion into the synths.html. The other issue is that I can't remember if your auto-generation code could work out if we had patch /bank library/editor support or not. If not, maybe a filename string match could be good enough? Also I noticed this guy Thorsten who has been updating jsynthlib a bit over here: http://midibox.org/forums/topic/14981-jsynthlib-update/ I'd like to look at getting his work into 0.21 so I'm going to try and contact him. frankie |