Menu
▾
▴
jsynthlib-devel — Mailing list for developers and users interested in improving the JSynthLib.
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(90) |
Sep
(38) |
Oct
(22) |
Nov
(3) |
Dec
(13) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(40) |
Feb
(119) |
Mar
(236) |
Apr
(41) |
May
(45) |
Jun
(10) |
Jul
(9) |
Aug
(12) |
Sep
(5) |
Oct
(17) |
Nov
(2) |
Dec
(3) |
| 2006 |
Jan
(23) |
Feb
(36) |
Mar
(49) |
Apr
|
May
|
Jun
(1) |
Jul
(11) |
Aug
(11) |
Sep
(15) |
Oct
(30) |
Nov
(36) |
Dec
(13) |
| 2007 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
(3) |
Jun
(7) |
Jul
(4) |
Aug
(1) |
Sep
(19) |
Oct
(1) |
Nov
(2) |
Dec
(5) |
| 2008 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(5) |
Dec
|
| 2009 |
Jan
(26) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(26) |
Sep
(6) |
Oct
(5) |
Nov
(6) |
Dec
(6) |
| 2010 |
Jan
(3) |
Feb
|
Mar
(5) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(6) |
Aug
(8) |
Sep
(220) |
Oct
(9) |
Nov
(27) |
Dec
(33) |
| 2012 |
Jan
|
Feb
(4) |
Mar
(9) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
| 2013 |
Jan
(6) |
Feb
(20) |
Mar
(6) |
Apr
(3) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(17) |
Nov
(2) |
Dec
|
| 2014 |
Jan
(9) |
Feb
(1) |
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(2) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael H. <kor...@ya...> - 2018-05-31 10:27:16
|
http://distant.promang.net Michael Hawkins |
|
From: Packe <pa...@ya...> - 2014-12-16 15:13:45
|
Hi, I’m writing to you to inform you that I have (finally) discovered the Ctrlr project. This project pretty much meets the needs I have for a sysex editor/librarian. The only thing that is currently missing are the drivers. I have therefore decided to abandon the JSL development and instead moving over to Ctrlr. As I have done quite some work in JSL concerning especially GUI testing and porting the drivers to JavaFX I realized that quite a lot of that code could be well suited to create a JSL->Ctrlr driver converter. It is now in a state where I can generate a basic Ctrlr editor panel from a JSL single driver with editor. I will be converting the Roland D50, Yamaha DX7, Emu Proteus/2 and Ensoniq ESQ1 drivers. If you are interested in porting any of the existing JSL drivers you can contact me. BR /Pascal |
|
From: Thomas J. <tho...@gm...> - 2014-12-14 17:34:42
|
Hi,
I've tried to get the current git HEAD running today (imho, the move to git
and the plan to make XML drivers is _awesome_) in order to a) finally get a
librarian solution for my hardware synths (and thus adding drivers, since
only one of my synths here is already supported) and b) try if I can
squeeze some contributions to JSynthLib into my schedule, but there's an
error while running "mvn package":
[INFO] --- maven-antrun-plugin:1.7:run (synthdrivers) @ jsynthlib ---
[INFO] Executing tasks
main:
[java] 18:24:24,025 [main] INFO org.jsynthlib.utils.DeviceParser -
Found 13094 URLs
[java] 18:24:24,051 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.NovationXioSynth.NovationXioSynthDevice
[java] 18:24:24,070 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.BehringerFCB1010.FCB1010Device
[java] 18:24:24,076 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.RolandJV80.RolandJV80Device
[java] 18:24:24,084 [main] DEBUG org.jsynthlib.utils.DeviceParser -
Found XMLDevice org.jsynthlib.synthdrivers.EnsoniqESQ1.EnsoniqESQ1Device
[java] 18:24:24,089 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.YamahaCS2x.YamahaCS2xDevice
[java] 18:24:24,107 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.QuasimidiQuasar.QuasimidiQuasarDevice
[java] 18:24:24,113 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.RolandGP16.RolandGP16Device
[java] 18:24:24,115 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.YamahaSY77.YamahaSY77Device
[java] 18:24:24,120 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.MIDIboxSID.MIDIboxSIDDevice
[java] 18:24:24,125 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.RolandJD800.RolandJD800Device
[java] 18:24:24,130 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.OberheimMatrix.OberheimMatrix1000Device
[java] 18:24:24,132 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.MIDIboxFM.MIDIboxFMDevice
[java] 18:24:24,133 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.BehringerVAmp2.VAmp2Device
[java] 18:24:24,138 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.AlesisDM5.AlesisDM5Device
[java] 18:24:24,139 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.RolandMKS7.RolandMKS7Device
[java] 18:24:24,140 [main] DEBUG org.jsynthlib.utils.DeviceParser -
Found XMLDevice org.jsynthlib.synthdrivers.YamahaDX7.YamahaDX7Device
[java] 18:24:24,154 [main] DEBUG org.jsynthlib.utils.DeviceParser -
PARSING org/jsynthlib/synthdrivers/EmuProteus2/EmuProteus2Device.xml
[java] 18:24:24,356 [main] INFO org.jsynthlib.utils.DeviceParser -
Found org.jsynthlib.synthdrivers.EmuProteus2.EmuProteus2Device name
Proteus 2
[java] 18:24:24,362 [main] DEBUG org.jsynthlib.utils.DeviceParser -
PARSING org/jsynthlib/synthdrivers/YamahaDX7/YamahaDX7VoiceBankDriver.xml
[java] 18:24:24,365 [main] INFO org.jsynthlib.utils.DeviceListWriter
- Failed to write device list
[java] 18:24:24,366 [main] WARN org.jsynthlib.utils.DeviceListWriter
- Element xmlBankDriverDefinition@http://www.jsynthlib.org/xmldevice is
not a valid xmlDeviceDefinition@http://www.jsynthlib.org/xmldevice document
or a valid substitution.
[java] org.apache.xmlbeans.XmlException: Element
xmlBankDriverDefinition@http://www.jsynthlib.org/xmldevice is not a valid
xmlDeviceDefinition@http://www.jsynthlib.org/xmldevice document or a valid
substitution.
[java] at
org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:322)
[java] at
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1273)
[java] at
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1257)
[java] at
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
[java] at
org.jsynthlib.xmldevice.XmlDeviceDefinitionDocument$Factory.parse(Unknown
Source)
[java] at
org.jsynthlib.utils.DeviceParser.getAllDevices(DeviceParser.java:94)
[java] at
org.jsynthlib.utils.DeviceListWriter.main(DeviceListWriter.java:38)
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
The debug line starting with PARSING was added by me to see which XML file
causes the failure.
According to xmllint, the file validates fine, so I don't know where the
problem is here... any hints?
As already said, it's the current git HEAD (just typed git pull; mvn
package before writing this) on a debian testing with openjdk 8
(8u40~b09-1) and openjfx (8u20-b26-3) on debian testing (openjdk/openjfx
packages from sid) built via maven 3.0.5 (reporting a Java version of
1.8.0_40).
I'd like to get the checkout running as-is before commiting anything to it.
Thanks,
Thomas
|
|
From: Packe <pa...@ya...> - 2014-10-23 18:10:37
|
Hi, I’ve finally had enough of Eclipse’s lousy SVN plugins so I moved the code from SVN to Git on Sourceforge. You can now access the code here instead: http://sourceforge.net/p/jsynthlib/jsynthlib I’ve kept the old repo as a read-only reference. I didn’t move any branches as my impression is that they are all outdated anyway. If you have any branch you want to keep alive just branch out in git and merge your SVN changes to it. BR /Pascal PS. If you all object furiously to this it is still possible to continue with the old SVN repo as it is still intact. DS. |
|
From: Packe <pa...@ya...> - 2014-10-10 21:56:42
|
Hi! Today I have delivered a lot of code to trunk. This is the initial step towards XML drivers. I have ported some drivers (those where I own the synthesizer..) as a proof of concept. There is still a lot of work to do even for these drivers though. The design is made to be backwards compatible thus the XML driver classes inherit from base driver classes that all other drivers also inherit. There are no new methods added instead I have used the old interfaces. There is a lot of documentation work yet to be done but I delivered this code any way to avoid ambiguity about which branch that is the ”main” branch. If anybody is interested you should feel more than welcome to review what I have done and I will quickly reply any questions posted here as that also could be good input for what to put in the docs. Anyway.. here are some things that have changed: - Dependency injection is used for some core components using guice - New editors use the JavaFX technology and are thus saved as FXML documents. These documents can be opened and manipulated in Oracle’s SceneBuilder (you need to have Java 8 from now on) - Patch parameters are defined in XML with unique UUIDs. - There is a class called FXMLGenerator. This class takes a driver XML document and outputs a corresponding FXML file. This file shall then be opened in SceneBuilder to improve the auto generated GUI stub manually - Old drivers with editors can be extracted into driver XML files by using the XMLExtractor class (under the test package) - And a lot more.. BR /Pascal |
|
From: Martin T. <m.t...@zo...> - 2014-03-04 10:08:28
|
On Mon, 3 Mar 2014, Packe wrote: > Hi, > > I have added a discussion forum on the project page on Sourceforge. Please create a new post there regarding this issue. done. MT |
|
From: Packe <pa...@ya...> - 2014-03-03 18:48:47
|
Hi, I have added a discussion forum on the project page on Sourceforge. Please create a new post there regarding this issue. Br /Pascal > 3 mar 2014 kl. 18:15 skrev Martin Tarenskeen <m.t...@zo...>: > > > I am not quite sure what the right place is to report the errormessages and failure I get after trying to build jsynthlib with the following commands: > > mvn clean > mvn package > > using the latest SVN sources on my Linux Fedora 20 system. > See attachment for the ERROR messages I get. > > -- > > MT > <mvn-jsynthlib-err.txt> > ------------------------------------------------------------------------------ > Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. > With Perforce, you get hassle-free workflows. Merge that actually works. > Faster operations. Version large binaries. Built-in WAN optimization and the > freedom to use Git, Perforce or both. Make the move to Perforce. > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > _______________________________________________ > Jsynthlib-devel mailing list > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Martin T. <m.t...@zo...> - 2014-03-03 17:15:29
|
I am not quite sure what the right place is to report the errormessages and failure I get after trying to build jsynthlib with the following commands: mvn clean mvn package using the latest SVN sources on my Linux Fedora 20 system. See attachment for the ERROR messages I get. -- MT |
|
From: Packe <pa...@ya...> - 2014-03-02 19:08:05
|
I haven't tested this on Linux. Please post the stacktraces in a bug/support request on sourceforge. If you are running maven you should run Mvn clean xmlbeans:xmlbeans package It will run some tests that probably will fail... /Pascal > 2 mar 2014 kl. 19:56 skrev Martin Tarenskeen <m.t...@zo...>: > > > I know practically nothing about java and maven. > But following the instructions I found, I was able to download the latest > sources from Sourceforge using svn. > > Then, after going inside jsynthlib-code/JSynthLib I did > > $ mvn package > > And things started to roll, until the process bumped into a long series of > ERROR messages. > > I am using Linux Fedora 20, I have java-1.7.0-openjdk and > java-1.7.0-openjdk-devel packages installed, I have maven-3.1.1 plus a > long list of additional maven plugin packages. > > Am I missing or misunderstanding something? > > I can remember that I was able to compile and build the old 0.20 version > using ant without problems, but that was quite some time ago. > > It would be nice if I knew how to compile before trying to touch any of > the synthdrivers. > > -- > > MT > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > Jsynthlib-devel mailing list > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: denis q. <dqu...@fr...> - 2014-03-02 19:08:04
|
Hi, what is the first error in your compilation log ? > I know practically nothing about java and maven. > But following the instructions I found, I was able to download the latest > sources from Sourceforge using svn. > > Then, after going inside jsynthlib-code/JSynthLib I did > > $ mvn package > > And things started to roll, until the process bumped into a long series of > ERROR messages. > > I am using Linux Fedora 20, I have java-1.7.0-openjdk and > java-1.7.0-openjdk-devel packages installed, I have maven-3.1.1 plus a > long list of additional maven plugin packages. > > Am I missing or misunderstanding something? > > I can remember that I was able to compile and build the old 0.20 version > using ant without problems, but that was quite some time ago. > > It would be nice if I knew how to compile before trying to touch any of > the synthdrivers. > |
|
From: Martin T. <m.t...@zo...> - 2014-03-02 18:56:17
|
I know practically nothing about java and maven. But following the instructions I found, I was able to download the latest sources from Sourceforge using svn. Then, after going inside jsynthlib-code/JSynthLib I did $ mvn package And things started to roll, until the process bumped into a long series of ERROR messages. I am using Linux Fedora 20, I have java-1.7.0-openjdk and java-1.7.0-openjdk-devel packages installed, I have maven-3.1.1 plus a long list of additional maven plugin packages. Am I missing or misunderstanding something? I can remember that I was able to compile and build the old 0.20 version using ant without problems, but that was quite some time ago. It would be nice if I knew how to compile before trying to touch any of the synthdrivers. -- MT |
|
From: Packe <pa...@ya...> - 2014-03-02 11:34:02
|
Hi, Please ask the user to submit a bug/support request on sourceforge. Br /Pascal > 2 mar 2014 kl. 10:41 skrev Martin Tarenskeen <m.t...@zo...>: > > > Don't know about the details, > I'm just forwarding a message: > > ---------- Forwarded message ---------- > Date: 02 Mar 2014 01:02:16 -0800 > From: pau...@ya... > Reply-To: yam...@ya... > To: yam...@ya... > Subject: [yamahablackboxes] JSynthLib 1.0 in Windows > > > > Tested with DX7 driver, nice Nimbus GUI. > No issues to run JSL setup in Windows. > TX81Z driver doesn't work properly! > > > > 1. add the java path system variable > 2. double-click JSynthLib-1.0-setup > 3. set midi user preferences ... > > __._,_.___ > Reply via web post > Reply to sender > Reply to group > Start a New Topic > Messages in this topic (1) Visit Your Group > Yahoo! Groups • Privacy • Unsubscribe • Terms of Use > . > [stime=1393750937] > __,_._,___ |
|
From: Martin T. <m.t...@zo...> - 2014-03-02 09:41:12
|
Don't know about the details, I'm just forwarding a message: ---------- Forwarded message ---------- Date: 02 Mar 2014 01:02:16 -0800 From: pau...@ya... Reply-To: yam...@ya... To: yam...@ya... Subject: [yamahablackboxes] JSynthLib 1.0 in Windows Tested with DX7 driver, nice Nimbus GUI. No issues to run JSL setup in Windows. TX81Z driver doesn't work properly! 1. add the java path system variable 2. double-click JSynthLib-1.0-setup 3. set midi user preferences ... __._,_.___ Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (1) Visit Your Group Yahoo! Groups • Privacy • Unsubscribe • Terms of Use . [stime=1393750937] __,_._,___ |
|
From: pascalc <pa...@ya...> - 2014-03-01 20:50:08
|
Hi again, I said earlier that I would send out some info on the users' mailing list but I just realized that there might not exist such a mailing list? Does anybody know if there ever has been a users' mailing list for JSynthLib? I posted a news on Sourceforge a couple of days ago I guess that will have to do if there is no users' mailing list. BR /Pascal 1 mar 2014 kl. 09:41 skrev Martin Tarenskeen <m.t...@zo...>: > > > On Sat, 1 Mar 2014, Packe wrote: > >> I can do that tonight. Besides that, as I haven't been involved with the project earlier, I have no idea where to publish news except on the sourceforge site. Any help/suggestions are highly appreciated. >> My next step now for the development is to restructure the code in an MVC architecture and then continue the work of XML drivers to make it easier for others to contribute their drivers. > >>> 28 feb 2014 kl. 22:53 skrev Frankie Fisher <jsy...@te...>: >>> Firstly, excellent work getting the project into a good shape and >>> getting a release out there. > > > Congratulations with the release of jsynthlib 1.0 !! > > I am really really glad the project is active again, and hope somewhere in the future to contribute some stuff myself. An easier way to create and contribute new synthdrivers would definitely be welcomed! > > I have posted announcements in yamahadx and yamahablackboxes Yahoo mailinglists, and on fedora-music and planetccrma mailinglists to help spread the word. > > -- > > MT |
|
From: Martin T. <m.t...@zo...> - 2014-03-01 08:41:14
|
On Sat, 1 Mar 2014, Packe wrote: > I can do that tonight. Besides that, as I haven't been involved with the project earlier, I have no idea where to publish news except on the sourceforge site. > Any help/suggestions are highly appreciated. > > My next step now for the development is to restructure the code in an MVC architecture and then continue the work of XML drivers to make it easier for others to contribute their drivers. >> 28 feb 2014 kl. 22:53 skrev Frankie Fisher <jsy...@te...>: >> >> Firstly, excellent work getting the project into a good shape and >> getting a release out there. Congratulations with the release of jsynthlib 1.0 !! I am really really glad the project is active again, and hope somewhere in the future to contribute some stuff myself. An easier way to create and contribute new synthdrivers would definitely be welcomed! I have posted announcements in yamahadx and yamahablackboxes Yahoo mailinglists, and on fedora-music and planetccrma mailinglists to help spread the word. -- MT |
|
From: Packe <pa...@ya...> - 2014-03-01 07:21:19
|
Hi Frankie, Great idea! I thought I should have sent out an email on the users' list but I forgot... I can do that tonight. Besides that, as I haven't been involved with the project earlier, I have no idea where to publish news except on the sourceforge site. Any help/suggestions are highly appreciated. My next step now for the development is to restructure the code in an MVC architecture and then continue the work of XML drivers to make it easier for others to contribute their drivers. Braån /Pascal > 28 feb 2014 kl. 22:53 skrev Frankie Fisher <jsy...@te...>: > > Firstly, excellent work getting the project into a good shape and > getting a release out there. > > Do we need to announce the release anywhere? I've updated freshmeat.net > with the release details (if anyone still uses that website these days). > Any other ways to let people know that jsynthlib is open for business? > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > Jsynthlib-devel mailing list > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Frankie F. <jsy...@te...> - 2014-02-28 22:15:28
|
Firstly, excellent work getting the project into a good shape and getting a release out there. Do we need to announce the release anywhere? I've updated freshmeat.net with the release details (if anyone still uses that website these days). Any other ways to let people know that jsynthlib is open for business? |
|
From: Packe <pa...@ya...> - 2014-01-03 22:12:57
|
Hi, Yes, I realized that to so I changed the name of my branch now so that it doesn't contain any digit anymore. /Pascal 3 jan 2014 kl. 23:11 skrev Joachim <li...@sd...>: > Hi Pascal, > > the numbers on the other branches are release numbers apart from > branch_k1_support and I have no idea what that branch is for. > > Regards, > Joachim > > Am 03.01.2014 22:50, schrieb Packe: > >> Probably yes but I saw that some other branches also had some numbers in their name so I thought it wasn't that bad.. >> >> Is it possible to rename a branch? >> >> BR >> /Pascal >> >> 3 jan 2014 kl. 22:12 skrev Joachim: >> >>> Hi, >>> >>> ah, didn't check this. OK, then I think it's best to rename the branch system-test5 to system-test: >>> http://sourceforge.net/p/jsynthlib/code/HEAD/tree/branches/ >>> >>> I use SVN at work but never created a branch on my own so I confused it here with real folders. >>> Might also be that I'm currently pretty exhausted. >>> >>> Joachim > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Jsynthlib-devel mailing list > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Joachim <li...@sd...> - 2014-01-03 22:11:30
|
Hi Pascal, the numbers on the other branches are release numbers apart from branch_k1_support and I have no idea what that branch is for. Regards, Joachim Am 03.01.2014 22:50, schrieb Packe: > Probably yes but I saw that some other branches also had some numbers in their name so I thought it wasn't that bad.. > > Is it possible to rename a branch? > > BR > /Pascal > > 3 jan 2014 kl. 22:12 skrev Joachim: > >> Hi, >> >> ah, didn't check this. OK, then I think it's best to rename the branch system-test5 to system-test: >> http://sourceforge.net/p/jsynthlib/code/HEAD/tree/branches/ >> >> I use SVN at work but never created a branch on my own so I confused it here with real folders. >> Might also be that I'm currently pretty exhausted. >> >> Joachim |
|
From: Packe <pa...@ya...> - 2014-01-03 21:50:23
|
sdiy.de> To: Joachim <li...@sd...> X-Mailer: Apple Mail (2.1510) Probably yes but I saw that some other branches also had some numbers in their name so I thought it wasn't that bad.. Is it possible to rename a branch? BR /Pascal 3 jan 2014 kl. 22:12 skrev Joachim <li...@sd...>: > Hi, > > ah, didn't check this. OK, then I think it's best to rename the branch system-test5 to system-test: > http://sourceforge.net/p/jsynthlib/code/HEAD/tree/branches/ > > I use SVN at work but never created a branch on my own so I confused it here with real folders. > Might also be that I'm currently pretty exhausted. > > Joachim > > Am 03.01.2014 21:55, schrieb Packe: >> Ah crap.. >> >> That's branches that I've created. This is where I was a bit confused with SVN. >> >> Are those really folders in the source repo? I think that if you check out trunk there should be no such folders. >> >> BR >> /Pascal >> >> 3 jan 2014 kl. 21:47 skrev Joachim <li...@sd...>: >> >>> Hi, >>> >>> there are five system-test folders. Like system-test5 here: >>> http://sourceforge.net/p/jsynthlib/code/1238 >>> >>> Joachim >>> >>> Am 03.01.2014 21:39, schrieb Packe: >>>> >>>> Hi, >>>> >>>> I think I only created one? >>>> >>>> I'm not used to SVN so there has been some problems along the way. >>>> >>>> Basically it should be a standard maven structure of the project now. >>>> >>>> In the src/test/resources I've put quite some xml files containing syses dumps auto generated and used by my test case. >>>> >>>> Where have I created more test folders? >>>> >>>> BR >>>> /Pascal >>>> >>>> 3 jan 2014 kl. 21:11 skrev Joachim <li...@sd...>: >>>> >>>>> Hi, >>>>> >>>>> why are you creating so many 'test' folders? >>>>> >>>>> Cheers, >>>>> Joachim >>>>> >>>>> Am 20.10.2013 22:09, schrieb Packe: >>>>>> Hi again, >>>>>> >>>>>> I have now been given admin rights to this project (thanks Joachim). What I understood from Joachim is that there is no active maintainer of the JSynthlib project today. So I'm now willing to assume that role. >>>>>> >>>>>> I've been sketching on sort of a roadmap and would like to get some feedback: >>>>>> >>>>>> Change project structure and fix ant script >>>>>> Create system test cases to secure basic driver functionality - assuming that the current drivers work as expected... >>>>>> Fix existing bugs (can those of you who know any bugs please report them on SF?) >>>>>> 1.0 release - As discussed in this thread: 10th anniversary >>>>>> I'm hoping to do that this year or early next >>>>>> Once the 1.0 release is done I think focus should be on merging the refactor branch to trunk and straighten up the API >>>>>> >>>>>> If anybody still believes in this project help is very much appreciated! >>>>>> >>>>>> One thing though, I think a problem previously has been that code has been delivered without prior review. Therefore I would like patches being submitted through the patch page on SF instead of direct merges to trunk. I (and possibly another volunteer) will monitor these patches and provide feedback/merge the patches as they are submitted. >>>>>> >>>>>> I'll wait one week from now to let you get back with your thoughts before starting any work at all. >>>>>> >>>>>> Chris, would you be able to explain what you did for changes to the ant script on the refactor branch? >>>>>> >>>>>> BR >>>>>> /Pascal >>>>>> >>>>>> 17 okt 2013 kl. 17:07 skrev Packe <pa...@ya...>: >>>>>> >>>>>>> Hi Chris! >>>>>>> >>>>>>> I understand your concerns regarding the status of this project. I found it about 6 months ago while I was creating something similar (from scratch..) and thought it would be worth a try to implement drivers for my synthesizers using JSynthlib instead, and it actually was… >>>>>>> >>>>>>> What worries me the most is that there doesn't seem to exist any test cases. Especially not for the drivers. Therefore it's extremely risky to do major changes to core. >>>>>>> >>>>>>> I would like to perform the improved folder structure change first, then create some test cases. It should be possible to automatically generate test cases by moving around controllers and listening to the MIDI output. >>>>>>> >>>>>>> Once that is done I think it would be appropriate to do the (very much needed) cleaning of core. >>>>>>> >>>>>>> I have seen too many "complete rewrite" projects just going nowhere. Therefore I think this project is a good start. Even if it is really messy it has one advantage: it works (at least for the synthesizers I own). >>>>>>> >>>>>>> BR >>>>>>> /Pascal >>>>>>> >>>>>>> 17 okt 2013 kl. 15:58 skrev "chr...@ch..." <chr...@ch...>: >>>>>>> >>>>>>>> Hi Pascal, >>>>>>>> >>>>>>>> Packe [pa...@ya...] wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> Yes, I have had a look at the refactor branch. My concern about that branch >>>>>>>>> was that it didn't seem active and that in some mailing list conversation >>>>>>>>> there was very high aims for what was going to be developed in that branch. >>>>>>>>> >>>>>>>> >>>>>>>> I got to a point with my refactoring where I would have liked some feedback and >>>>>>>> an indication whether the work was likely to be merged back into trunk. The lack >>>>>>>> of feedback and list activity in general lead me to the conclusion that >>>>>>>> JSynthLib is an orphaned project and that I should focus my efforts elsewhere. >>>>>>>> >>>>>>>> At the point I left it, the code in my branch compiles and loads the files >>>>>>>> created in the currently released version. I was somewhat dependent on people >>>>>>>> testing, since I didn't have any supported synths to test an existing driver. >>>>>>>> >>>>>>>>> >>>>>>>>> Therefore I felt that it would take quite a long time to merge those changes >>>>>>>>> (which seems very good btw) to trunk. >>>>>>>>> >>>>>>>> >>>>>>>> Had there been any activity in the trunk, then I would have merged or ported >>>>>>>> those changes. From what I can see, there still hasn't been any activity on the >>>>>>>> trunk since I started my branch. >>>>>>>> >>>>>>>>> >>>>>>>>> Regarding Ant vs Maven vs whatever I don't really have a firm opinion. >>>>>>>>> >>>>>>>> >>>>>>>> It's not something I have particularly strong feelings about - I'd be much more >>>>>>>> concerned in a project like JSynthLib if it mandated the use of a particular >>>>>>>> IDE. I vaguely recall someone almost doing this by trying to use the GUI builder >>>>>>>> in NetBeans many years ago. That was when the project seemed more active and I >>>>>>>> first considered trying to contribute to it - the attempt to enforce NetBean's >>>>>>>> GUI builder is what put me off. >>>>>>>> >>>>>>>>> >>>>>>>>> The benefit of Maven is that it has a resource folder right inside src which >>>>>>>>> is handy to save resources such as images in. As you mention it is also neat >>>>>>>>> to handle dependencies. >>>>>>>>> >>>>>>>> >>>>>>>> Maven seems to have adopted existing best practices in this regard. >>>>>>>> >>>>>>>>> >>>>>>>>> What would you say is left before we can merge the refactor branch to trunk? >>>>>>>>> >>>>>>>> >>>>>>>> I suspect that my branch is at least as stable as trunk, but with the beginnings >>>>>>>> of a major API cleanup. It looks like there was a clear design and decent >>>>>>>> encapsulation at some point, but that they have been broken over the years. >>>>>>>> Cleaning this up further will be a lot of work, and I wonder if it may not be >>>>>>>> better to start from scratch with the core, and just using the existing drivers >>>>>>>> as a form of documentation for new ones. >>>>>>>> >>>>>>>>> BR >>>>>>>>> /Pascal >>>>>>>>> >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Chris >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> October Webinars: Code for Performance >>>>>>> Free Intel webinars can help you accelerate application performance. >>>>>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>>>>>> the latest Intel processors and coprocessors. See abstracts and register > >>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >>>>>>> _______________________________________________ >>>>>>> Jsynthlib-devel mailing list >>>>>>> Jsy...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> October Webinars: Code for Performance >>>>>> Free Intel webinars can help you accelerate application performance. >>>>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>>>>> the latest Intel processors and coprocessors. See abstracts and register > >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >>>>>> _______________________________________________ >>>>>> Jsynthlib-devel mailing list >>>>>> Jsy...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >>>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Rapidly troubleshoot problems before they affect your business. Most IT >>>>> organizations don't have a clear picture of how application performance >>>>> affects their revenue. With AppDynamics, you get 100% visibility into your >>>>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >>>>> _______________________________________________ >>>>> Jsynthlib-devel mailing list >>>>> Jsy...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Rapidly troubleshoot problems before they affect your business. Most IT >>> organizations don't have a clear picture of how application performance >>> affects their revenue. With AppDynamics, you get 100% visibility into your >>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! >>> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Jsynthlib-devel mailing list >>> Jsy...@li... >>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >> > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Jsynthlib-devel mailing list > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Joachim <li...@sd...> - 2014-01-03 21:12:10
|
Hi, ah, didn't check this. OK, then I think it's best to rename the branch system-test5 to system-test: http://sourceforge.net/p/jsynthlib/code/HEAD/tree/branches/ I use SVN at work but never created a branch on my own so I confused it here with real folders. Might also be that I'm currently pretty exhausted. Joachim Am 03.01.2014 21:55, schrieb Packe: > Ah crap.. > > That's branches that I've created. This is where I was a bit confused with SVN. > > Are those really folders in the source repo? I think that if you check out trunk there should be no such folders. > > BR > /Pascal > > 3 jan 2014 kl. 21:47 skrev Joachim <li...@sd...>: > >> Hi, >> >> there are five system-test folders. Like system-test5 here: >> http://sourceforge.net/p/jsynthlib/code/1238 >> >> Joachim >> >> Am 03.01.2014 21:39, schrieb Packe: >>> >>> Hi, >>> >>> I think I only created one? >>> >>> I'm not used to SVN so there has been some problems along the way. >>> >>> Basically it should be a standard maven structure of the project now. >>> >>> In the src/test/resources I've put quite some xml files containing syses dumps auto generated and used by my test case. >>> >>> Where have I created more test folders? >>> >>> BR >>> /Pascal >>> >>> 3 jan 2014 kl. 21:11 skrev Joachim <li...@sd...>: >>> >>>> Hi, >>>> >>>> why are you creating so many 'test' folders? >>>> >>>> Cheers, >>>> Joachim >>>> >>>> Am 20.10.2013 22:09, schrieb Packe: >>>>> Hi again, >>>>> >>>>> I have now been given admin rights to this project (thanks Joachim). What I understood from Joachim is that there is no active maintainer of the JSynthlib project today. So I'm now willing to assume that role. >>>>> >>>>> I've been sketching on sort of a roadmap and would like to get some feedback: >>>>> >>>>> Change project structure and fix ant script >>>>> Create system test cases to secure basic driver functionality - assuming that the current drivers work as expected... >>>>> Fix existing bugs (can those of you who know any bugs please report them on SF?) >>>>> 1.0 release - As discussed in this thread: 10th anniversary >>>>> I'm hoping to do that this year or early next >>>>> Once the 1.0 release is done I think focus should be on merging the refactor branch to trunk and straighten up the API >>>>> >>>>> If anybody still believes in this project help is very much appreciated! >>>>> >>>>> One thing though, I think a problem previously has been that code has been delivered without prior review. Therefore I would like patches being submitted through the patch page on SF instead of direct merges to trunk. I (and possibly another volunteer) will monitor these patches and provide feedback/merge the patches as they are submitted. >>>>> >>>>> I'll wait one week from now to let you get back with your thoughts before starting any work at all. >>>>> >>>>> Chris, would you be able to explain what you did for changes to the ant script on the refactor branch? >>>>> >>>>> BR >>>>> /Pascal >>>>> >>>>> 17 okt 2013 kl. 17:07 skrev Packe <pa...@ya...>: >>>>> >>>>>> Hi Chris! >>>>>> >>>>>> I understand your concerns regarding the status of this project. I found it about 6 months ago while I was creating something similar (from scratch..) and thought it would be worth a try to implement drivers for my synthesizers using JSynthlib instead, and it actually was… >>>>>> >>>>>> What worries me the most is that there doesn't seem to exist any test cases. Especially not for the drivers. Therefore it's extremely risky to do major changes to core. >>>>>> >>>>>> I would like to perform the improved folder structure change first, then create some test cases. It should be possible to automatically generate test cases by moving around controllers and listening to the MIDI output. >>>>>> >>>>>> Once that is done I think it would be appropriate to do the (very much needed) cleaning of core. >>>>>> >>>>>> I have seen too many "complete rewrite" projects just going nowhere. Therefore I think this project is a good start. Even if it is really messy it has one advantage: it works (at least for the synthesizers I own). >>>>>> >>>>>> BR >>>>>> /Pascal >>>>>> >>>>>> 17 okt 2013 kl. 15:58 skrev "chr...@ch..." <chr...@ch...>: >>>>>> >>>>>>> Hi Pascal, >>>>>>> >>>>>>> Packe [pa...@ya...] wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Yes, I have had a look at the refactor branch. My concern about that branch >>>>>>>> was that it didn't seem active and that in some mailing list conversation >>>>>>>> there was very high aims for what was going to be developed in that branch. >>>>>>>> >>>>>>> >>>>>>> I got to a point with my refactoring where I would have liked some feedback and >>>>>>> an indication whether the work was likely to be merged back into trunk. The lack >>>>>>> of feedback and list activity in general lead me to the conclusion that >>>>>>> JSynthLib is an orphaned project and that I should focus my efforts elsewhere. >>>>>>> >>>>>>> At the point I left it, the code in my branch compiles and loads the files >>>>>>> created in the currently released version. I was somewhat dependent on people >>>>>>> testing, since I didn't have any supported synths to test an existing driver. >>>>>>> >>>>>>>> >>>>>>>> Therefore I felt that it would take quite a long time to merge those changes >>>>>>>> (which seems very good btw) to trunk. >>>>>>>> >>>>>>> >>>>>>> Had there been any activity in the trunk, then I would have merged or ported >>>>>>> those changes. From what I can see, there still hasn't been any activity on the >>>>>>> trunk since I started my branch. >>>>>>> >>>>>>>> >>>>>>>> Regarding Ant vs Maven vs whatever I don't really have a firm opinion. >>>>>>>> >>>>>>> >>>>>>> It's not something I have particularly strong feelings about - I'd be much more >>>>>>> concerned in a project like JSynthLib if it mandated the use of a particular >>>>>>> IDE. I vaguely recall someone almost doing this by trying to use the GUI builder >>>>>>> in NetBeans many years ago. That was when the project seemed more active and I >>>>>>> first considered trying to contribute to it - the attempt to enforce NetBean's >>>>>>> GUI builder is what put me off. >>>>>>> >>>>>>>> >>>>>>>> The benefit of Maven is that it has a resource folder right inside src which >>>>>>>> is handy to save resources such as images in. As you mention it is also neat >>>>>>>> to handle dependencies. >>>>>>>> >>>>>>> >>>>>>> Maven seems to have adopted existing best practices in this regard. >>>>>>> >>>>>>>> >>>>>>>> What would you say is left before we can merge the refactor branch to trunk? >>>>>>>> >>>>>>> >>>>>>> I suspect that my branch is at least as stable as trunk, but with the beginnings >>>>>>> of a major API cleanup. It looks like there was a clear design and decent >>>>>>> encapsulation at some point, but that they have been broken over the years. >>>>>>> Cleaning this up further will be a lot of work, and I wonder if it may not be >>>>>>> better to start from scratch with the core, and just using the existing drivers >>>>>>> as a form of documentation for new ones. >>>>>>> >>>>>>>> BR >>>>>>>> /Pascal >>>>>>>> >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Chris >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> October Webinars: Code for Performance >>>>>> Free Intel webinars can help you accelerate application performance. >>>>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>>>>> the latest Intel processors and coprocessors. See abstracts and register > >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >>>>>> _______________________________________________ >>>>>> Jsynthlib-devel mailing list >>>>>> Jsy...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> October Webinars: Code for Performance >>>>> Free Intel webinars can help you accelerate application performance. >>>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>>>> the latest Intel processors and coprocessors. See abstracts and register > >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >>>>> _______________________________________________ >>>>> Jsynthlib-devel mailing list >>>>> Jsy...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >>>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Rapidly troubleshoot problems before they affect your business. Most IT >>>> organizations don't have a clear picture of how application performance >>>> affects their revenue. With AppDynamics, you get 100% visibility into your >>>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! >>>> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >>>> _______________________________________________ >>>> Jsynthlib-devel mailing list >>>> Jsy...@li... >>>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >>> >> >> >> ------------------------------------------------------------------------------ >> Rapidly troubleshoot problems before they affect your business. Most IT >> organizations don't have a clear picture of how application performance >> affects their revenue. With AppDynamics, you get 100% visibility into your >> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >> _______________________________________________ >> Jsynthlib-devel mailing list >> Jsy...@li... >> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > |
|
From: Packe <pa...@ya...> - 2014-01-03 20:59:37
|
sdiy.de> To: Joachim <li...@sd...> X-Mailer: Apple Mail (2.1510) Hi, I think I only created one? I'm not used to SVN so there has been some problems along the way. Basically it should be a standard maven structure of the project now. In the src/test/resources I've put quite some xml files containing syses dumps auto generated and used by my test case. Where have I created more test folders? BR /Pascal 3 jan 2014 kl. 21:11 skrev Joachim <li...@sd...>: > Hi, > > why are you creating so many 'test' folders? > > Cheers, > Joachim > > Am 20.10.2013 22:09, schrieb Packe: >> Hi again, >> >> I have now been given admin rights to this project (thanks Joachim). What I understood from Joachim is that there is no active maintainer of the JSynthlib project today. So I'm now willing to assume that role. >> >> I've been sketching on sort of a roadmap and would like to get some feedback: >> >> Change project structure and fix ant script >> Create system test cases to secure basic driver functionality - assuming that the current drivers work as expected... >> Fix existing bugs (can those of you who know any bugs please report them on SF?) >> 1.0 release - As discussed in this thread: 10th anniversary >> I'm hoping to do that this year or early next >> Once the 1.0 release is done I think focus should be on merging the refactor branch to trunk and straighten up the API >> >> If anybody still believes in this project help is very much appreciated! >> >> One thing though, I think a problem previously has been that code has been delivered without prior review. Therefore I would like patches being submitted through the patch page on SF instead of direct merges to trunk. I (and possibly another volunteer) will monitor these patches and provide feedback/merge the patches as they are submitted. >> >> I'll wait one week from now to let you get back with your thoughts before starting any work at all. >> >> Chris, would you be able to explain what you did for changes to the ant script on the refactor branch? >> >> BR >> /Pascal >> >> 17 okt 2013 kl. 17:07 skrev Packe <pa...@ya...>: >> >>> Hi Chris! >>> >>> I understand your concerns regarding the status of this project. I found it about 6 months ago while I was creating something similar (from scratch..) and thought it would be worth a try to implement drivers for my synthesizers using JSynthlib instead, and it actually was… >>> >>> What worries me the most is that there doesn't seem to exist any test cases. Especially not for the drivers. Therefore it's extremely risky to do major changes to core. >>> >>> I would like to perform the improved folder structure change first, then create some test cases. It should be possible to automatically generate test cases by moving around controllers and listening to the MIDI output. >>> >>> Once that is done I think it would be appropriate to do the (very much needed) cleaning of core. >>> >>> I have seen too many "complete rewrite" projects just going nowhere. Therefore I think this project is a good start. Even if it is really messy it has one advantage: it works (at least for the synthesizers I own). >>> >>> BR >>> /Pascal >>> >>> 17 okt 2013 kl. 15:58 skrev "chr...@ch..." <chr...@ch...>: >>> >>>> Hi Pascal, >>>> >>>> Packe [pa...@ya...] wrote: >>>>> >>>>> Hi, >>>>> >>>>> Yes, I have had a look at the refactor branch. My concern about that branch >>>>> was that it didn't seem active and that in some mailing list conversation >>>>> there was very high aims for what was going to be developed in that branch. >>>>> >>>> >>>> I got to a point with my refactoring where I would have liked some feedback and >>>> an indication whether the work was likely to be merged back into trunk. The lack >>>> of feedback and list activity in general lead me to the conclusion that >>>> JSynthLib is an orphaned project and that I should focus my efforts elsewhere. >>>> >>>> At the point I left it, the code in my branch compiles and loads the files >>>> created in the currently released version. I was somewhat dependent on people >>>> testing, since I didn't have any supported synths to test an existing driver. >>>> >>>>> >>>>> Therefore I felt that it would take quite a long time to merge those changes >>>>> (which seems very good btw) to trunk. >>>>> >>>> >>>> Had there been any activity in the trunk, then I would have merged or ported >>>> those changes. From what I can see, there still hasn't been any activity on the >>>> trunk since I started my branch. >>>> >>>>> >>>>> Regarding Ant vs Maven vs whatever I don't really have a firm opinion. >>>>> >>>> >>>> It's not something I have particularly strong feelings about - I'd be much more >>>> concerned in a project like JSynthLib if it mandated the use of a particular >>>> IDE. I vaguely recall someone almost doing this by trying to use the GUI builder >>>> in NetBeans many years ago. That was when the project seemed more active and I >>>> first considered trying to contribute to it - the attempt to enforce NetBean's >>>> GUI builder is what put me off. >>>> >>>>> >>>>> The benefit of Maven is that it has a resource folder right inside src which >>>>> is handy to save resources such as images in. As you mention it is also neat >>>>> to handle dependencies. >>>>> >>>> >>>> Maven seems to have adopted existing best practices in this regard. >>>> >>>>> >>>>> What would you say is left before we can merge the refactor branch to trunk? >>>>> >>>> >>>> I suspect that my branch is at least as stable as trunk, but with the beginnings >>>> of a major API cleanup. It looks like there was a clear design and decent >>>> encapsulation at some point, but that they have been broken over the years. >>>> Cleaning this up further will be a lot of work, and I wonder if it may not be >>>> better to start from scratch with the core, and just using the existing drivers >>>> as a form of documentation for new ones. >>>> >>>>> BR >>>>> /Pascal >>>>> >>>> >>>> Regards, >>>> >>>> Chris >>> >>> >>> ------------------------------------------------------------------------------ >>> October Webinars: Code for Performance >>> Free Intel webinars can help you accelerate application performance. >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>> the latest Intel processors and coprocessors. See abstracts and register > >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Jsynthlib-devel mailing list >>> Jsy...@li... >>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >> >> ------------------------------------------------------------------------------ >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >> the latest Intel processors and coprocessors. See abstracts and register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >> _______________________________________________ >> Jsynthlib-devel mailing list >> Jsy...@li... >> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >> > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Jsynthlib-devel mailing list > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Packe <pa...@ya...> - 2014-01-03 20:55:57
|
Ah crap.. That's branches that I've created. This is where I was a bit confused with SVN. Are those really folders in the source repo? I think that if you check out trunk there should be no such folders. BR /Pascal 3 jan 2014 kl. 21:47 skrev Joachim <li...@sd...>: > Hi, > > there are five system-test folders. Like system-test5 here: > http://sourceforge.net/p/jsynthlib/code/1238 > > Joachim > > Am 03.01.2014 21:39, schrieb Packe: >> >> Hi, >> >> I think I only created one? >> >> I'm not used to SVN so there has been some problems along the way. >> >> Basically it should be a standard maven structure of the project now. >> >> In the src/test/resources I've put quite some xml files containing syses dumps auto generated and used by my test case. >> >> Where have I created more test folders? >> >> BR >> /Pascal >> >> 3 jan 2014 kl. 21:11 skrev Joachim <li...@sd...>: >> >>> Hi, >>> >>> why are you creating so many 'test' folders? >>> >>> Cheers, >>> Joachim >>> >>> Am 20.10.2013 22:09, schrieb Packe: >>>> Hi again, >>>> >>>> I have now been given admin rights to this project (thanks Joachim). What I understood from Joachim is that there is no active maintainer of the JSynthlib project today. So I'm now willing to assume that role. >>>> >>>> I've been sketching on sort of a roadmap and would like to get some feedback: >>>> >>>> Change project structure and fix ant script >>>> Create system test cases to secure basic driver functionality - assuming that the current drivers work as expected... >>>> Fix existing bugs (can those of you who know any bugs please report them on SF?) >>>> 1.0 release - As discussed in this thread: 10th anniversary >>>> I'm hoping to do that this year or early next >>>> Once the 1.0 release is done I think focus should be on merging the refactor branch to trunk and straighten up the API >>>> >>>> If anybody still believes in this project help is very much appreciated! >>>> >>>> One thing though, I think a problem previously has been that code has been delivered without prior review. Therefore I would like patches being submitted through the patch page on SF instead of direct merges to trunk. I (and possibly another volunteer) will monitor these patches and provide feedback/merge the patches as they are submitted. >>>> >>>> I'll wait one week from now to let you get back with your thoughts before starting any work at all. >>>> >>>> Chris, would you be able to explain what you did for changes to the ant script on the refactor branch? >>>> >>>> BR >>>> /Pascal >>>> >>>> 17 okt 2013 kl. 17:07 skrev Packe <pa...@ya...>: >>>> >>>>> Hi Chris! >>>>> >>>>> I understand your concerns regarding the status of this project. I found it about 6 months ago while I was creating something similar (from scratch..) and thought it would be worth a try to implement drivers for my synthesizers using JSynthlib instead, and it actually was… >>>>> >>>>> What worries me the most is that there doesn't seem to exist any test cases. Especially not for the drivers. Therefore it's extremely risky to do major changes to core. >>>>> >>>>> I would like to perform the improved folder structure change first, then create some test cases. It should be possible to automatically generate test cases by moving around controllers and listening to the MIDI output. >>>>> >>>>> Once that is done I think it would be appropriate to do the (very much needed) cleaning of core. >>>>> >>>>> I have seen too many "complete rewrite" projects just going nowhere. Therefore I think this project is a good start. Even if it is really messy it has one advantage: it works (at least for the synthesizers I own). >>>>> >>>>> BR >>>>> /Pascal >>>>> >>>>> 17 okt 2013 kl. 15:58 skrev "chr...@ch..." <chr...@ch...>: >>>>> >>>>>> Hi Pascal, >>>>>> >>>>>> Packe [pa...@ya...] wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Yes, I have had a look at the refactor branch. My concern about that branch >>>>>>> was that it didn't seem active and that in some mailing list conversation >>>>>>> there was very high aims for what was going to be developed in that branch. >>>>>>> >>>>>> >>>>>> I got to a point with my refactoring where I would have liked some feedback and >>>>>> an indication whether the work was likely to be merged back into trunk. The lack >>>>>> of feedback and list activity in general lead me to the conclusion that >>>>>> JSynthLib is an orphaned project and that I should focus my efforts elsewhere. >>>>>> >>>>>> At the point I left it, the code in my branch compiles and loads the files >>>>>> created in the currently released version. I was somewhat dependent on people >>>>>> testing, since I didn't have any supported synths to test an existing driver. >>>>>> >>>>>>> >>>>>>> Therefore I felt that it would take quite a long time to merge those changes >>>>>>> (which seems very good btw) to trunk. >>>>>>> >>>>>> >>>>>> Had there been any activity in the trunk, then I would have merged or ported >>>>>> those changes. From what I can see, there still hasn't been any activity on the >>>>>> trunk since I started my branch. >>>>>> >>>>>>> >>>>>>> Regarding Ant vs Maven vs whatever I don't really have a firm opinion. >>>>>>> >>>>>> >>>>>> It's not something I have particularly strong feelings about - I'd be much more >>>>>> concerned in a project like JSynthLib if it mandated the use of a particular >>>>>> IDE. I vaguely recall someone almost doing this by trying to use the GUI builder >>>>>> in NetBeans many years ago. That was when the project seemed more active and I >>>>>> first considered trying to contribute to it - the attempt to enforce NetBean's >>>>>> GUI builder is what put me off. >>>>>> >>>>>>> >>>>>>> The benefit of Maven is that it has a resource folder right inside src which >>>>>>> is handy to save resources such as images in. As you mention it is also neat >>>>>>> to handle dependencies. >>>>>>> >>>>>> >>>>>> Maven seems to have adopted existing best practices in this regard. >>>>>> >>>>>>> >>>>>>> What would you say is left before we can merge the refactor branch to trunk? >>>>>>> >>>>>> >>>>>> I suspect that my branch is at least as stable as trunk, but with the beginnings >>>>>> of a major API cleanup. It looks like there was a clear design and decent >>>>>> encapsulation at some point, but that they have been broken over the years. >>>>>> Cleaning this up further will be a lot of work, and I wonder if it may not be >>>>>> better to start from scratch with the core, and just using the existing drivers >>>>>> as a form of documentation for new ones. >>>>>> >>>>>>> BR >>>>>>> /Pascal >>>>>>> >>>>>> >>>>>> Regards, >>>>>> >>>>>> Chris >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> October Webinars: Code for Performance >>>>> Free Intel webinars can help you accelerate application performance. >>>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>>>> the latest Intel processors and coprocessors. See abstracts and register > >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >>>>> _______________________________________________ >>>>> Jsynthlib-devel mailing list >>>>> Jsy...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >>>> >>>> ------------------------------------------------------------------------------ >>>> October Webinars: Code for Performance >>>> Free Intel webinars can help you accelerate application performance. >>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>>> the latest Intel processors and coprocessors. See abstracts and register > >>>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >>>> _______________________________________________ >>>> Jsynthlib-devel mailing list >>>> Jsy...@li... >>>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Rapidly troubleshoot problems before they affect your business. Most IT >>> organizations don't have a clear picture of how application performance >>> affects their revenue. With AppDynamics, you get 100% visibility into your >>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! >>> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Jsynthlib-devel mailing list >>> Jsy...@li... >>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >> > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Jsynthlib-devel mailing list > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel |
|
From: Joachim <li...@sd...> - 2014-01-03 20:47:36
|
Hi, there are five system-test folders. Like system-test5 here: http://sourceforge.net/p/jsynthlib/code/1238 Joachim Am 03.01.2014 21:39, schrieb Packe: > > Hi, > > I think I only created one? > > I'm not used to SVN so there has been some problems along the way. > > Basically it should be a standard maven structure of the project now. > > In the src/test/resources I've put quite some xml files containing syses dumps auto generated and used by my test case. > > Where have I created more test folders? > > BR > /Pascal > > 3 jan 2014 kl. 21:11 skrev Joachim <li...@sd...>: > >> Hi, >> >> why are you creating so many 'test' folders? >> >> Cheers, >> Joachim >> >> Am 20.10.2013 22:09, schrieb Packe: >>> Hi again, >>> >>> I have now been given admin rights to this project (thanks Joachim). What I understood from Joachim is that there is no active maintainer of the JSynthlib project today. So I'm now willing to assume that role. >>> >>> I've been sketching on sort of a roadmap and would like to get some feedback: >>> >>> Change project structure and fix ant script >>> Create system test cases to secure basic driver functionality - assuming that the current drivers work as expected... >>> Fix existing bugs (can those of you who know any bugs please report them on SF?) >>> 1.0 release - As discussed in this thread: 10th anniversary >>> I'm hoping to do that this year or early next >>> Once the 1.0 release is done I think focus should be on merging the refactor branch to trunk and straighten up the API >>> >>> If anybody still believes in this project help is very much appreciated! >>> >>> One thing though, I think a problem previously has been that code has been delivered without prior review. Therefore I would like patches being submitted through the patch page on SF instead of direct merges to trunk. I (and possibly another volunteer) will monitor these patches and provide feedback/merge the patches as they are submitted. >>> >>> I'll wait one week from now to let you get back with your thoughts before starting any work at all. >>> >>> Chris, would you be able to explain what you did for changes to the ant script on the refactor branch? >>> >>> BR >>> /Pascal >>> >>> 17 okt 2013 kl. 17:07 skrev Packe <pa...@ya...>: >>> >>>> Hi Chris! >>>> >>>> I understand your concerns regarding the status of this project. I found it about 6 months ago while I was creating something similar (from scratch..) and thought it would be worth a try to implement drivers for my synthesizers using JSynthlib instead, and it actually was… >>>> >>>> What worries me the most is that there doesn't seem to exist any test cases. Especially not for the drivers. Therefore it's extremely risky to do major changes to core. >>>> >>>> I would like to perform the improved folder structure change first, then create some test cases. It should be possible to automatically generate test cases by moving around controllers and listening to the MIDI output. >>>> >>>> Once that is done I think it would be appropriate to do the (very much needed) cleaning of core. >>>> >>>> I have seen too many "complete rewrite" projects just going nowhere. Therefore I think this project is a good start. Even if it is really messy it has one advantage: it works (at least for the synthesizers I own). >>>> >>>> BR >>>> /Pascal >>>> >>>> 17 okt 2013 kl. 15:58 skrev "chr...@ch..." <chr...@ch...>: >>>> >>>>> Hi Pascal, >>>>> >>>>> Packe [pa...@ya...] wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Yes, I have had a look at the refactor branch. My concern about that branch >>>>>> was that it didn't seem active and that in some mailing list conversation >>>>>> there was very high aims for what was going to be developed in that branch. >>>>>> >>>>> >>>>> I got to a point with my refactoring where I would have liked some feedback and >>>>> an indication whether the work was likely to be merged back into trunk. The lack >>>>> of feedback and list activity in general lead me to the conclusion that >>>>> JSynthLib is an orphaned project and that I should focus my efforts elsewhere. >>>>> >>>>> At the point I left it, the code in my branch compiles and loads the files >>>>> created in the currently released version. I was somewhat dependent on people >>>>> testing, since I didn't have any supported synths to test an existing driver. >>>>> >>>>>> >>>>>> Therefore I felt that it would take quite a long time to merge those changes >>>>>> (which seems very good btw) to trunk. >>>>>> >>>>> >>>>> Had there been any activity in the trunk, then I would have merged or ported >>>>> those changes. From what I can see, there still hasn't been any activity on the >>>>> trunk since I started my branch. >>>>> >>>>>> >>>>>> Regarding Ant vs Maven vs whatever I don't really have a firm opinion. >>>>>> >>>>> >>>>> It's not something I have particularly strong feelings about - I'd be much more >>>>> concerned in a project like JSynthLib if it mandated the use of a particular >>>>> IDE. I vaguely recall someone almost doing this by trying to use the GUI builder >>>>> in NetBeans many years ago. That was when the project seemed more active and I >>>>> first considered trying to contribute to it - the attempt to enforce NetBean's >>>>> GUI builder is what put me off. >>>>> >>>>>> >>>>>> The benefit of Maven is that it has a resource folder right inside src which >>>>>> is handy to save resources such as images in. As you mention it is also neat >>>>>> to handle dependencies. >>>>>> >>>>> >>>>> Maven seems to have adopted existing best practices in this regard. >>>>> >>>>>> >>>>>> What would you say is left before we can merge the refactor branch to trunk? >>>>>> >>>>> >>>>> I suspect that my branch is at least as stable as trunk, but with the beginnings >>>>> of a major API cleanup. It looks like there was a clear design and decent >>>>> encapsulation at some point, but that they have been broken over the years. >>>>> Cleaning this up further will be a lot of work, and I wonder if it may not be >>>>> better to start from scratch with the core, and just using the existing drivers >>>>> as a form of documentation for new ones. >>>>> >>>>>> BR >>>>>> /Pascal >>>>>> >>>>> >>>>> Regards, >>>>> >>>>> Chris >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> October Webinars: Code for Performance >>>> Free Intel webinars can help you accelerate application performance. >>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>>> the latest Intel processors and coprocessors. See abstracts and register > >>>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >>>> _______________________________________________ >>>> Jsynthlib-devel mailing list >>>> Jsy...@li... >>>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >>> >>> ------------------------------------------------------------------------------ >>> October Webinars: Code for Performance >>> Free Intel webinars can help you accelerate application performance. >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>> the latest Intel processors and coprocessors. See abstracts and register > >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Jsynthlib-devel mailing list >>> Jsy...@li... >>> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel >>> >> >> >> ------------------------------------------------------------------------------ >> Rapidly troubleshoot problems before they affect your business. Most IT >> organizations don't have a clear picture of how application performance >> affects their revenue. With AppDynamics, you get 100% visibility into your >> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >> _______________________________________________ >> Jsynthlib-devel mailing list >> Jsy...@li... >> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > |
|
From: Joachim <li...@sd...> - 2014-01-03 20:31:49
|
Hi, why are you creating so many 'test' folders? Cheers, Joachim Am 20.10.2013 22:09, schrieb Packe: > Hi again, > > I have now been given admin rights to this project (thanks Joachim). What I understood from Joachim is that there is no active maintainer of the JSynthlib project today. So I'm now willing to assume that role. > > I've been sketching on sort of a roadmap and would like to get some feedback: > > Change project structure and fix ant script > Create system test cases to secure basic driver functionality - assuming that the current drivers work as expected... > Fix existing bugs (can those of you who know any bugs please report them on SF?) > 1.0 release - As discussed in this thread: 10th anniversary > I'm hoping to do that this year or early next > Once the 1.0 release is done I think focus should be on merging the refactor branch to trunk and straighten up the API > > If anybody still believes in this project help is very much appreciated! > > One thing though, I think a problem previously has been that code has been delivered without prior review. Therefore I would like patches being submitted through the patch page on SF instead of direct merges to trunk. I (and possibly another volunteer) will monitor these patches and provide feedback/merge the patches as they are submitted. > > I'll wait one week from now to let you get back with your thoughts before starting any work at all. > > Chris, would you be able to explain what you did for changes to the ant script on the refactor branch? > > BR > /Pascal > > 17 okt 2013 kl. 17:07 skrev Packe <pa...@ya...>: > >> Hi Chris! >> >> I understand your concerns regarding the status of this project. I found it about 6 months ago while I was creating something similar (from scratch..) and thought it would be worth a try to implement drivers for my synthesizers using JSynthlib instead, and it actually was… >> >> What worries me the most is that there doesn't seem to exist any test cases. Especially not for the drivers. Therefore it's extremely risky to do major changes to core. >> >> I would like to perform the improved folder structure change first, then create some test cases. It should be possible to automatically generate test cases by moving around controllers and listening to the MIDI output. >> >> Once that is done I think it would be appropriate to do the (very much needed) cleaning of core. >> >> I have seen too many "complete rewrite" projects just going nowhere. Therefore I think this project is a good start. Even if it is really messy it has one advantage: it works (at least for the synthesizers I own). >> >> BR >> /Pascal >> >> 17 okt 2013 kl. 15:58 skrev "chr...@ch..." <chr...@ch...>: >> >>> Hi Pascal, >>> >>> Packe [pa...@ya...] wrote: >>>> >>>> Hi, >>>> >>>> Yes, I have had a look at the refactor branch. My concern about that branch >>>> was that it didn't seem active and that in some mailing list conversation >>>> there was very high aims for what was going to be developed in that branch. >>>> >>> >>> I got to a point with my refactoring where I would have liked some feedback and >>> an indication whether the work was likely to be merged back into trunk. The lack >>> of feedback and list activity in general lead me to the conclusion that >>> JSynthLib is an orphaned project and that I should focus my efforts elsewhere. >>> >>> At the point I left it, the code in my branch compiles and loads the files >>> created in the currently released version. I was somewhat dependent on people >>> testing, since I didn't have any supported synths to test an existing driver. >>> >>>> >>>> Therefore I felt that it would take quite a long time to merge those changes >>>> (which seems very good btw) to trunk. >>>> >>> >>> Had there been any activity in the trunk, then I would have merged or ported >>> those changes. From what I can see, there still hasn't been any activity on the >>> trunk since I started my branch. >>> >>>> >>>> Regarding Ant vs Maven vs whatever I don't really have a firm opinion. >>>> >>> >>> It's not something I have particularly strong feelings about - I'd be much more >>> concerned in a project like JSynthLib if it mandated the use of a particular >>> IDE. I vaguely recall someone almost doing this by trying to use the GUI builder >>> in NetBeans many years ago. That was when the project seemed more active and I >>> first considered trying to contribute to it - the attempt to enforce NetBean's >>> GUI builder is what put me off. >>> >>>> >>>> The benefit of Maven is that it has a resource folder right inside src which >>>> is handy to save resources such as images in. As you mention it is also neat >>>> to handle dependencies. >>>> >>> >>> Maven seems to have adopted existing best practices in this regard. >>> >>>> >>>> What would you say is left before we can merge the refactor branch to trunk? >>>> >>> >>> I suspect that my branch is at least as stable as trunk, but with the beginnings >>> of a major API cleanup. It looks like there was a clear design and decent >>> encapsulation at some point, but that they have been broken over the years. >>> Cleaning this up further will be a lot of work, and I wonder if it may not be >>> better to start from scratch with the core, and just using the existing drivers >>> as a form of documentation for new ones. >>> >>>> BR >>>> /Pascal >>>> >>> >>> Regards, >>> >>> Chris >> >> >> ------------------------------------------------------------------------------ >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >> the latest Intel processors and coprocessors. See abstracts and register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk >> _______________________________________________ >> Jsynthlib-devel mailing list >> Jsy...@li... >> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk > _______________________________________________ > Jsynthlib-devel mailing list > Jsy...@li... > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > |
89 messages has been excluded from this view by a project administrator.
