Menu
▾
▴
jsynthlib-devel
|
From: frankster <jsy...@te...> - 2011-08-31 01:38:08
|
Hi, I have downloaded the latest version of jsynthlib from svn and found that there are various problems with the code in trunk. * The RolandD10 driver seems to use features from Java 1.5 whereas the build.xml specifies version 1.4.2. * Some files are not encoded correctly causing warnings about unmappable characters. These occur in the YamahaDX7 and YamahaFS1R synth drivers. I have updated the build.xml to specify Java 1.5 - this seems better than rewriting some of the RolandD10 driver. I have saved the relevant files in the Yamaha drivers as UTF8. Is there anybody with SVN access that can put these fixes into the repository? Also if anybody wants a copy of these minor fixes off me before they find their way into SVN, then I can email the files that I have changed. Looking at the mailing list, this project seems dead lately but maybe its just dormant ;) I have a couple of sound modules (Emu Proteus 2000 and Roland U220) that are not supported by jsynthlib and I may be motivated to add support for them if there's anyone still interested in this project. Regards, Frankie |
|
From: Vladimir A. <vl...@gm...> - 2011-08-31 18:20:35
|
Hi, The project definitely feels dead. Maybe it is time for someone with enough interest and time to fork it into fresh active project. I was considering forking myself, but was not sure I could commit to maintaining the whole project. I could contribute in developing and supporting few synths i have though - yamaha sy77, proteus 2000, alesis micron. Regards, Vladimir On 08/30/2011 08:37 PM, frankster wrote: > Hi, > I have downloaded the latest version of jsynthlib from svn and found > that there are various problems with the code in trunk. > * The RolandD10 driver seems to use features from Java 1.5 whereas the > build.xml specifies version 1.4.2. > * Some files are not encoded correctly causing warnings about unmappable > characters. These occur in the YamahaDX7 and YamahaFS1R synth drivers. > > I have updated the build.xml to specify Java 1.5 - this seems better > than rewriting some of the RolandD10 driver. I have saved the relevant > files in the Yamaha drivers as UTF8. > > Is there anybody with SVN access that can put these fixes into the > repository? Also if anybody wants a copy of these minor fixes off me > before they find their way into SVN, then I can email the files that I > have changed. > > Looking at the mailing list, this project seems dead lately but maybe > its just dormant ;) I have a couple of sound modules (Emu Proteus 2000 > and Roland U220) that are not supported by jsynthlib and I may be > motivated to add support for them if there's anyone still interested in > this project. > > > Regards, > Frankie > > > > ------------------------------------------------------------------------------ > 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 > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Joachim <li...@sd...> - 2011-08-31 21:15:59
|
Hi, there were already some speaking about taking over/forking. All of them calmed down pretty soon. My advise is: Develop something new first and then eventually start thinking about a fork. But I'm pretty suer there is no need for a fork: If you want to do something, simply do it and don't just talk about doing it. Cheers Joachim Am 31.08.2011 20:20, schrieb Vladimir Avdonin: > Hi, > > The project definitely feels dead. Maybe it is time for someone with enough interest and time to fork it into fresh active project. > > I was considering forking myself, but was not sure I could commit to maintaining the whole project. I could contribute in developing and supporting few synths i have though - yamaha sy77, proteus 2000, alesis micron. > > Regards, > > Vladimir > > On 08/30/2011 08:37 PM, frankster wrote: >> Hi, >> I have downloaded the latest version of jsynthlib from svn and found >> that there are various problems with the code in trunk. >> * The RolandD10 driver seems to use features from Java 1.5 whereas the >> build.xml specifies version 1.4.2. >> * Some files are not encoded correctly causing warnings about unmappable >> characters. These occur in the YamahaDX7 and YamahaFS1R synth drivers. >> >> I have updated the build.xml to specify Java 1.5 - this seems better >> than rewriting some of the RolandD10 driver. I have saved the relevant >> files in the Yamaha drivers as UTF8. >> >> Is there anybody with SVN access that can put these fixes into the >> repository? Also if anybody wants a copy of these minor fixes off me >> before they find their way into SVN, then I can email the files that I >> have changed. >> >> Looking at the mailing list, this project seems dead lately but maybe >> its just dormant ;) I have a couple of sound modules (Emu Proteus 2000 >> and Roland U220) that are not supported by jsynthlib and I may be >> motivated to add support for them if there's anyone still interested in >> this project. >> >> >> Regards, >> Frankie >> >> >> >> ------------------------------------------------------------------------------ >> 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 >> Jsy...@li... >> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > > > ------------------------------------------------------------------------------ > 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 > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > |
|
From: Vladimir A. <vl...@gm...> - 2011-08-31 22:16:16
|
Checking back archives of the list brings several offers from different people to contribute already made changes, like the one that started this thread. They all were "calmed down" all right because of absence of any activity from developers with svn access. In general, I would think Source Forge should allow creating branches in any project's repository by anyone, not just to registered developers of the project. That way actual changes can be published and tested by much broader audience, sort of wikipedia approach. I have deep respect to the work that have been done by creators of the project, but currently the project is not being improved, and does not accept any help being offered. And improvements can still be made in different parts of the project, not just adding drivers for new synths. Such state of affairs pretty much means dead project to me. I hope the project will be revived either as continuation of current line of development, or as a fork. As for doing something first - I already offered few months ago a librarian for yamaha sy77. Shall i dump it in form of patch onto the list? Regards, Vladimir On 08/31/2011 04:00 PM, Joachim wrote: > Hi, > > there were already some speaking about taking over/forking. > All of them calmed down pretty soon. > > My advise is: Develop something new first and then eventually > start thinking about a fork. > > But I'm pretty suer there is no need for a fork: If you want to do something, > simply do it and don't just talk about doing it. > > Cheers > Joachim > > Am 31.08.2011 20:20, schrieb Vladimir Avdonin: >> Hi, >> >> The project definitely feels dead. Maybe it is time for someone with enough interest and time to fork it into fresh active project. >> >> I was considering forking myself, but was not sure I could commit to maintaining the whole project. I could contribute in developing and supporting few synths i have though - yamaha sy77, proteus 2000, alesis micron. >> >> Regards, >> >> Vladimir >> >> On 08/30/2011 08:37 PM, frankster wrote: >>> Hi, >>> I have downloaded the latest version of jsynthlib from svn and found >>> that there are various problems with the code in trunk. >>> * The RolandD10 driver seems to use features from Java 1.5 whereas the >>> build.xml specifies version 1.4.2. >>> * Some files are not encoded correctly causing warnings about unmappable >>> characters. These occur in the YamahaDX7 and YamahaFS1R synth drivers. >>> >>> I have updated the build.xml to specify Java 1.5 - this seems better >>> than rewriting some of the RolandD10 driver. I have saved the relevant >>> files in the Yamaha drivers as UTF8. >>> >>> Is there anybody with SVN access that can put these fixes into the >>> repository? Also if anybody wants a copy of these minor fixes off me >>> before they find their way into SVN, then I can email the files that I >>> have changed. >>> >>> Looking at the mailing list, this project seems dead lately but maybe >>> its just dormant ;) I have a couple of sound modules (Emu Proteus 2000 >>> and Roland U220) that are not supported by jsynthlib and I may be >>> motivated to add support for them if there's anyone still interested in >>> this project. >>> >>> >>> Regards, >>> Frankie >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> 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 >>> Jsy...@li... >>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >> >> ------------------------------------------------------------------------------ >> 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 >> Jsy...@li... >> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >> > > ------------------------------------------------------------------------------ > 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 > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: William Z. <wrz...@po...> - 2011-08-31 22:45:35
|
Any admins still around? I think we should unlock the project so anyone can check in at any time. We might run the risk of having a vandal visit, but I think it's more important to make life easier for the occasional developer. If nobody responds, I may just do this myself. I'll call it "JSynthLib Anarchy". =^) -Bill Zwicky |
|
From: Michael H. <pat...@ya...> - 2011-08-31 23:14:14
|
I ran into some rather tough jsynthlib admin's a couple of years back. I think it was you Bill! But in retrospect, I understand why the admins were tough on me because I now know that I then new nothing about what I was doing. But my, my was it hard trying to get up to speed with jsynthlib with that kind of newbie treatment. Well, that water has gone under the bridge so I do recommend opening jsynthlib up for wider contribution. Basically, I think that anyone that wants to join the development team should be permitted to submit changes. I doubt that vandals will be all that interested in jsynthlib. Let's face it, it's been almost impossible to get any developers interested! And I don't think it's because of lack of functionality nor do I think it's because of total lack of interest. A cross platform MIDI librarian is a wonderful thing to my mind. The only thing that drives me nuts about jsynthlib is the maddening process of laying out widgets. There simply has to be either better documentation on it or a better way of doing it. But maybe I just still don't know what I am doing! Nevertheless, if someone opens up sourceforge jsynthlib a bit more then I am quite sure we would get a bit more support from the wider community out there. Please add me as a developer! I promise not to intentionally vandalize! Mike ________________________________ From: William Zwicky <wrz...@po...> To: Cc: jsy...@li... Sent: Wednesday, August 31, 2011 6:45 PM Subject: Re: [Jsynthlib-devel] fixed build error in trunk Any admins still around? I think we should unlock the project so anyone can check in at any time. We might run the risk of having a vandal visit, but I think it's more important to make life easier for the occasional developer. If nobody responds, I may just do this myself. I'll call it "JSynthLib Anarchy". =^) -Bill Zwicky ------------------------------------------------------------------------------ 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 Jsy...@li... https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Joe E. <jo...@em...> - 2011-09-01 03:55:47
|
On 8/31/2011 4:14 PM, Michael Hawkins wrote: > I ran into some rather tough jsynthlib admin's a couple of years back. I think it was you Bill! I don't think Bill is an "admin" (in the sense that he can't authorize people to upload to the svn repository); I think only Joachim and Brian are. The rest of us (about 15 others) have write-access to the svn, but we can't add people. > The only thing that drives me nuts about jsynthlib is the maddening process of laying out widgets. There simply has to be either better documentation on it or a better way of doing it. But maybe I just still don't know what I am doing! About 4 years ago, I started on a massive (for me) re-factoring of the code. I moved everything into packages which compartmentalized what everything did (ie, a package for low-level MIDI message handling, a package for the main GUI, a package for the widgets, etc.). The two big hurdles were: 1 - Rewriting the low-level MIDI stuff. As I recall, sending and polling for MIDI signals was done with the GUI thread or something, so I made a new thread which would handle all queuing of MIDI messages and notify various sysex handlers that something had come in for them, etc. It made it so that I could write a little MIDI monitor window to watch incoming traffic, etc. 2 - Re-vamping the hierarchy of the JSynthlib widgets. It turns out that the basic JSynthlib window was named something strange, which made it hard to get up to speed on how to make a new synth-lib module. Anyway, as you can imagine, with a huge refactor like that, there were tons of compile errors as I changed around the way things were invoked, etc. When I ran out of steam on it, I think there were still a handful of errors that I couldn't really figure out how to best solve... so I never committed the changes. Since the project is so dormant, I'm tempted to dig the code up again and commit it just to see if it generates some renewed interest... - Joe |
|
From: frankster <jsy...@te...> - 2011-09-01 08:23:00
|
On 01/09/2011 04:40, Joe Emenaker wrote: > I don't think Bill is an "admin" (in the sense that he can't authorize > people to upload to the svn repository); I think only Joachim and > Brian are. The rest of us (about 15 others) have write-access to the > svn, but we can't add people. Maybe you can have a look at the patches on the tracker and submit them into cvs ;) > > Since the project is so dormant, I'm tempted to dig the code up again > and commit it just to see if it generates some renewed interest... Sounds like a good idea to me. Frankie |
|
From: Vladimir A. <vl...@gm...> - 2011-09-01 14:49:16
|
Joe, You are listed as project admin. Did you ever try adding anyone to svn access? Few months ago you said you could add me to the project, but that ended with nothing. Did any other admins objected? Or it just did not work technically? Regarding you experimental work: The mechanism for such activity provided by subversion is branch. Once you created you branch you can screw it around in any way you please, it would not affect main line of development and releases. Once your branch would arrive to some agreeable good state, it can be merged back into trunk for common use. If you would put you refactoring effort on the branch 4 years ago, there would be a good chance someone could pick it up and help you finish it. When i was working on driver code, I was wondering on some design choices for class hierarchy, and I was very itchy myself to refactor the code. I decided to hold my horses until I could at least discuss that with main developers. So, please, create a branch for refactoring and commit you work there. It would be a shame to waste that effort. Regard, Vladimir On 08/31/2011 10:40 PM, Joe Emenaker wrote: > On 8/31/2011 4:14 PM, Michael Hawkins wrote: >> I ran into some rather tough jsynthlib admin's a couple of years back. I think it was you Bill! > I don't think Bill is an "admin" (in the sense that he can't authorize > people to upload to the svn repository); I think only Joachim and Brian > are. The rest of us (about 15 others) have write-access to the svn, but > we can't add people. > >> The only thing that drives me nuts about jsynthlib is the maddening process of laying out widgets. There simply has to be either better documentation on it or a better way of doing it. But maybe I just still don't know what I am doing! > About 4 years ago, I started on a massive (for me) re-factoring of the > code. I moved everything into packages which compartmentalized what > everything did (ie, a package for low-level MIDI message handling, a > package for the main GUI, a package for the widgets, etc.). The two big > hurdles were: > 1 - Rewriting the low-level MIDI stuff. As I recall, sending and polling > for MIDI signals was done with the GUI thread or something, so I made a > new thread which would handle all queuing of MIDI messages and notify > various sysex handlers that something had come in for them, etc. It made > it so that I could write a little MIDI monitor window to watch incoming > traffic, etc. > 2 - Re-vamping the hierarchy of the JSynthlib widgets. It turns out that > the basic JSynthlib window was named something strange, which made it > hard to get up to speed on how to make a new synth-lib module. > > Anyway, as you can imagine, with a huge refactor like that, there were > tons of compile errors as I changed around the way things were invoked, > etc. When I ran out of steam on it, I think there were still a handful > of errors that I couldn't really figure out how to best solve... so I > never committed the changes. > > Since the project is so dormant, I'm tempted to dig the code up again > and commit it just to see if it generates some renewed interest... > > - Joe > > ------------------------------------------------------------------------------ > 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 > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Joachim <li...@sd...> - 2011-09-01 16:44:59
|
Vladimir, > Did any other admins objected? Or it just did not work technically? I tried but I didn't find your SourceForge user. If you mail it to me (off-list) or to the list I'm able to add you. Cheers Joachim Am 01.09.2011 16:49, schrieb Vladimir Avdonin: > Joe, > > You are listed as project admin. Did you ever try adding anyone to svn access? > > Few months ago you said you could add me to the project, but that ended with nothing. Did any other admins objected? Or it just did not work technically? > > Regarding you experimental work: > > The mechanism for such activity provided by subversion is branch. Once you created you branch you can screw it around in any way you please, it would not affect main line of development and releases. Once your branch would arrive to some agreeable good state, it can be merged back into trunk for common use. > > If you would put you refactoring effort on the branch 4 years ago, there would be a good chance someone could pick it up and help you finish it. When i was working on driver code, I was wondering on some design choices for class hierarchy, and I was very itchy myself to refactor the code. I decided to hold my horses until I could at least discuss that with main developers. > > So, please, create a branch for refactoring and commit you work there. It would be a shame to waste that effort. > > Regard, > Vladimir > > On 08/31/2011 10:40 PM, Joe Emenaker wrote: >> On 8/31/2011 4:14 PM, Michael Hawkins wrote: >>> I ran into some rather tough jsynthlib admin's a couple of years back. I think it was you Bill! >> I don't think Bill is an "admin" (in the sense that he can't authorize >> people to upload to the svn repository); I think only Joachim and Brian >> are. The rest of us (about 15 others) have write-access to the svn, but >> we can't add people. >> >>> The only thing that drives me nuts about jsynthlib is the maddening process of laying out widgets. There simply has to be either better documentation on it or a better way of doing it. But maybe I just still don't know what I am doing! >> About 4 years ago, I started on a massive (for me) re-factoring of the >> code. I moved everything into packages which compartmentalized what >> everything did (ie, a package for low-level MIDI message handling, a >> package for the main GUI, a package for the widgets, etc.). The two big >> hurdles were: >> 1 - Rewriting the low-level MIDI stuff. As I recall, sending and polling >> for MIDI signals was done with the GUI thread or something, so I made a >> new thread which would handle all queuing of MIDI messages and notify >> various sysex handlers that something had come in for them, etc. It made >> it so that I could write a little MIDI monitor window to watch incoming >> traffic, etc. >> 2 - Re-vamping the hierarchy of the JSynthlib widgets. It turns out that >> the basic JSynthlib window was named something strange, which made it >> hard to get up to speed on how to make a new synth-lib module. >> >> Anyway, as you can imagine, with a huge refactor like that, there were >> tons of compile errors as I changed around the way things were invoked, >> etc. When I ran out of steam on it, I think there were still a handful >> of errors that I couldn't really figure out how to best solve... so I >> never committed the changes. >> >> Since the project is so dormant, I'm tempted to dig the code up again >> and commit it just to see if it generates some renewed interest... >> >> - Joe >> >> ------------------------------------------------------------------------------ >> 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 >> Jsy...@li... >> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > > > ------------------------------------------------------------------------------ > 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 > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > |
|
From: frankster <jsy...@te...> - 2011-09-01 16:54:36
|
Thanks for adding me. FYI: You can see Vladimir's user name from the 2 patches he put in the patch tracker: https://sourceforge.net/tracker/?group_id=41208&atid=430006 Cheers, Frankie On 09/01/11 17:44, Joachim wrote: > Vladimir, > > > Did any other admins objected? Or it just did not work technically? > > I tried but I didn't find your SourceForge user. If you mail it to me (off-list) > or to the list I'm able to add you. > > Cheers > Joachim > > Am 01.09.2011 16:49, schrieb Vladimir Avdonin: >> Joe, >> >> You are listed as project admin. Did you ever try adding anyone to svn access? >> >> Few months ago you said you could add me to the project, but that ended with nothing. Did any other admins objected? Or it just did not work technically? >> >> Regarding you experimental work: >> >> The mechanism for such activity provided by subversion is branch. Once you created you branch you can screw it around in any way you please, it would not affect main line of development and releases. Once your branch would arrive to some agreeable good state, it can be merged back into trunk for common use. >> >> If you would put you refactoring effort on the branch 4 years ago, there would be a good chance someone could pick it up and help you finish it. When i was working on driver code, I was wondering on some design choices for class hierarchy, and I was very itchy myself to refactor the code. I decided to hold my horses until I could at least discuss that with main developers. >> >> So, please, create a branch for refactoring and commit you work there. It would be a shame to waste that effort. >> >> Regard, >> Vladimir >> >> On 08/31/2011 10:40 PM, Joe Emenaker wrote: >>> On 8/31/2011 4:14 PM, Michael Hawkins wrote: >>>> I ran into some rather tough jsynthlib admin's a couple of years back. I think it was you Bill! >>> I don't think Bill is an "admin" (in the sense that he can't authorize >>> people to upload to the svn repository); I think only Joachim and Brian >>> are. The rest of us (about 15 others) have write-access to the svn, but >>> we can't add people. >>> >>>> The only thing that drives me nuts about jsynthlib is the maddening process of laying out widgets. There simply has to be either better documentation on it or a better way of doing it. But maybe I just still don't know what I am doing! >>> About 4 years ago, I started on a massive (for me) re-factoring of the >>> code. I moved everything into packages which compartmentalized what >>> everything did (ie, a package for low-level MIDI message handling, a >>> package for the main GUI, a package for the widgets, etc.). The two big >>> hurdles were: >>> 1 - Rewriting the low-level MIDI stuff. As I recall, sending and polling >>> for MIDI signals was done with the GUI thread or something, so I made a >>> new thread which would handle all queuing of MIDI messages and notify >>> various sysex handlers that something had come in for them, etc. It made >>> it so that I could write a little MIDI monitor window to watch incoming >>> traffic, etc. >>> 2 - Re-vamping the hierarchy of the JSynthlib widgets. It turns out that >>> the basic JSynthlib window was named something strange, which made it >>> hard to get up to speed on how to make a new synth-lib module. >>> >>> Anyway, as you can imagine, with a huge refactor like that, there were >>> tons of compile errors as I changed around the way things were invoked, >>> etc. When I ran out of steam on it, I think there were still a handful >>> of errors that I couldn't really figure out how to best solve... so I >>> never committed the changes. >>> >>> Since the project is so dormant, I'm tempted to dig the code up again >>> and commit it just to see if it generates some renewed interest... >>> >>> - Joe >>> >>> ------------------------------------------------------------------------------ >>> 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 >>> Jsy...@li... >>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >> >> ------------------------------------------------------------------------------ >> 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 >> Jsy...@li... >> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >> > > ------------------------------------------------------------------------------ > 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 > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Vladimir A. <vl...@gm...> - 2011-09-01 17:02:29
|
On 09/01/2011 11:44 AM, Joachim wrote: > I tried but I didn't find your SourceForge user. If you mail it to me (off-list) > or to the list I'm able to add you. Thanks, but I am not sure the amount of effort I could currently afford to contribute to the project would justify adding me as a developer now. I would stick around and use patch submission when needed for now. If I really find myself later involved in lots of code changes, then I would ask to be added Regards, Vladimir |
|
From: Daniel R. <dr....@co...> - 2011-08-31 23:00:15
|
Vladimir, are there any restrictions on forking (license-wise)? Are the project owners alive and responding, at least? JSynthlib is great, no doubt. I borrowed some code from there when I knew even less of what I was doing in terms of MIDI in Java. Then I decided to ignore JSynth entirely and I ended up writing confusionists.com/handsonicwhich turned out to be a mildly popular product. I have no point here, really, but I think that the usability concerns for end-users are a causal factor in the lack of interest. Speaking of open-source projects with very little public development interest, I have created confusionists.com/mjdj, a MIDI translator or morpher engine and API framework. I mention this because if anybody out there (with an interest in Java and MIDI) would be interested in taking a run through the code, it would really help out. Good luck with JSynthlib. This list hasn't produced any mail in months, so you might be on to something by starting anew. Best, Daniel |
|
From: William Z. <wrz...@po...> - 2011-08-31 23:37:18
|
I'm not an admin, so I can't help. That's why I threatened to fork. It looks like the developer docs are hard to find. Do you know about the wiki? http://jsynthlib.wikispaces.com/ -Bill Zwicky On Wed, Aug 31, 2011 at 4:14 PM, Michael Hawkins <pat...@ya...>wrote: > I ran into some rather tough jsynthlib admin's a couple of years back. I > think it was you Bill! But in retrospect, I understand why the admins were > tough on me because I now know that I then new nothing about what I was > doing. But my, my was it hard trying to get up to speed with jsynthlib with > that kind of newbie treatment. > > Well, that water has gone under the bridge so I do recommend opening > jsynthlib up for wider contribution. Basically, I think that anyone that > wants to join the development team should be permitted to submit changes. I > doubt that vandals will be all that interested in jsynthlib. Let's face it, > it's been almost impossible to get any developers interested! And I don't > think it's because of lack of functionality nor do I think it's because of > total lack of interest. A cross platform MIDI librarian is a wonderful thing > to my mind. > > The only thing that drives me nuts about jsynthlib is the maddening process > of laying out widgets. There simply has to be either better documentation on > it or a better way of doing it. But maybe I just still don't know what I am > doing! > > Nevertheless, if someone opens up sourceforge jsynthlib a bit more then I > am quite sure we would get a bit more support from the wider community out > there. > > Please add me as a developer! I promise not to intentionally vandalize! > > |
|
From: Vladimir A. <vl...@gm...> - 2011-09-01 00:00:07
|
Well, after looking carefully at developer section of the project I discovered civilized way for occasional developer to submit changes. There is a patch section. The lonely patch that i found in there was molding there since 2009. The patch added support for SY85. So I added a couple of patches there. I suggest anyone with useful changes contribute through that interfaces as well. We will see how that would work. BTW, there is also bug tracker for the project. Lets try to bring the project to life in a civilized way using available tools. If all this activity would still be ignored by project owners, then it would be worth discussing other options. I really would like the current project live and improve. There is a good website, decent documentation, and even centralized patch archive. This all could be brought from good to great Regards, Vladimir On 08/31/2011 06:37 PM, William Zwicky wrote: > I'm not an admin, so I can't help. That's why I threatened to fork. > > It looks like the developer docs are hard to find. Do you know about the > wiki? > http://jsynthlib.wikispaces.com/ > > -Bill Zwicky > > > On Wed, Aug 31, 2011 at 4:14 PM, Michael Hawkins<pat...@ya...>wrote: > >> I ran into some rather tough jsynthlib admin's a couple of years back. I >> think it was you Bill! But in retrospect, I understand why the admins were >> tough on me because I now know that I then new nothing about what I was >> doing. But my, my was it hard trying to get up to speed with jsynthlib with >> that kind of newbie treatment. >> >> Well, that water has gone under the bridge so I do recommend opening >> jsynthlib up for wider contribution. Basically, I think that anyone that >> wants to join the development team should be permitted to submit changes. I >> doubt that vandals will be all that interested in jsynthlib. Let's face it, >> it's been almost impossible to get any developers interested! And I don't >> think it's because of lack of functionality nor do I think it's because of >> total lack of interest. A cross platform MIDI librarian is a wonderful thing >> to my mind. >> >> The only thing that drives me nuts about jsynthlib is the maddening process >> of laying out widgets. There simply has to be either better documentation on >> it or a better way of doing it. But maybe I just still don't know what I am >> doing! >> >> Nevertheless, if someone opens up sourceforge jsynthlib a bit more then I >> am quite sure we would get a bit more support from the wider community out >> there. >> >> Please add me as a developer! I promise not to intentionally vandalize! >> >> > ------------------------------------------------------------------------------ > 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 > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Joe E. <jo...@em...> - 2011-09-01 17:01:14
|
On 9/1/2011 7:49 AM, Vladimir Avdonin wrote: > Regarding you experimental work: > > The mechanism for such activity provided by subversion is branch. Once you created you branch you can screw it around in any way you please, it would not affect main line of development and releases. Once your branch would arrive to some agreeable good state, it can be merged back into trunk for common use. The only problem with that is that, back when I started it, Sourceforge wasn't using SVN, it was using CVS. SVN understands files getting *moved* to other folders, while CVS treats them as though you deleted the old file and created a new one in the new location. So, the revision history gets "broken", in a way. I'm now worried that, if I try to make a branch, SVN won't understand any continuity from the existing source tree, and it will consider the entire source code to be new.... which would make for an interesting merge into the trunk, later. But I know almost nothing about how SVN does it's thing... - Joe |
|
From: Vladimir A. <vl...@gm...> - 2011-09-01 17:11:37
|
On 09/01/2011 12:01 PM, Joe Emenaker wrote: > On 9/1/2011 7:49 AM, Vladimir Avdonin wrote: >> Regarding you experimental work: >> >> The mechanism for such activity provided by subversion is branch. Once you created you branch you can screw it around in any way you please, it would not affect main line of development and releases. Once your branch would arrive to some agreeable good state, it can be merged back into trunk for common use. > > The only problem with that is that, back when I started it, Sourceforge wasn't using SVN, it was using CVS. SVN understands files getting *moved* to other folders, while CVS treats them as though you deleted the old file and created a new one in the new location. So, the revision history gets "broken", in a way. > > I'm now worried that, if I try to make a branch, SVN won't understand any continuity from the existing source tree, and it will consider the entire source code to be new.... which would make for an interesting merge into the trunk, later. > > But I know almost nothing about how SVN does it's thing... > > - Joe Subversion is much better at that than cvs. You can keep updating your branch with changes from trunk - or any other branch for that matter. And eventually goal of any branch is to be merged back to trunk, which also works well. So continuity is not lost in either direction. Take a look at these chapter from svn book -- it is not very long reading. http://svnbook.red-bean.com/en/1.0/ch04.html Regards, Vladimir |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X