jsynthlib-devel

[Jsynthlib-devel] Yamaha FB01, Waldorf Micro Q and Roland D-5 drivers

[Maciej Ł. <loz...@o2...>]

Hello.

I'm about to write drivers for Yamaha FB01, Waldorf Micro Q and Roland 
D-5. I'll probably start with Yamaha, but later I plan to play with 
Waldorf. And here is my question - I found an entry in "Feature 
Requests" on SourceForge about Waldorf Q. Does it mean that someone is 
working on it? For Yamaha and Roland I found nothing, so I suppose they 
are free to hack :-)

I'm a JEE developer, so I hope I'll have a little fewer problems, but in 
case I had any, wish me luck :-) I'll post here when I do.

Cheers
Maciek

PS. Great project, I'll be happy to contribute :-)

[Jsynthlib-devel] Java version

[denis q. <dqu...@fr...>]

Hi,

I just checkout the trunk, ant build-run and get an error about :

    [javac] /Users/groumpf/Documents/dev/JSynthLib/trunk/JSynthLib/ 
synthdrivers/RolandD10/message/DisplayMessage.java:23: static import  
declarations are not supported in -source 1.4
     [javac] (try -source 1.5 to enable static import declarations)
     [javac] import static synthdrivers.RolandD10.D10Constants.*;


The build.xml is setting  java source and target to 1.4

It is not true: the source is 1.5, just set to 1.5 and compilation  
was OK.


But I don't think I have a SVN account ...

--
denis queffeulou

Re: [Jsynthlib-devel] Yamaha FB01, Waldorf Micro Q and Roland D-5 drivers

[Robert W. <wi...@op...>]

Hello Maciek,
in fact I have developed Waldort Q driver some time ago.
As I have not used it for long I am not sure about its state.
You can get it from jsynthlib.republika.pl/WaldorfQ.zip
Cheers,
Robert.


On Sep 30, 2009, at 11:08 PM, Maciej Łoziński wrote:

> Hello.
>
> I'm about to write drivers for Yamaha FB01, Waldorf Micro Q and Roland
> D-5. I'll probably start with Yamaha, but later I plan to play with
> Waldorf. And here is my question - I found an entry in "Feature
> Requests" on SourceForge about Waldorf Q. Does it mean that someone is
> working on it? For Yamaha and Roland I found nothing, so I suppose  
> they
> are free to hack :-)
>
> I'm a JEE developer, so I hope I'll have a little fewer problems,  
> but in
> case I had any, wish me luck :-) I'll post here when I do.
>
> Cheers
> Maciek
>
> PS. Great project, I'll be happy to contribute :-)
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9-12, 2009. Register  
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

Re: [Jsynthlib-devel] Java version

[William R. Z. <wrz...@po...>]

denis queffeulou wrote:
> The build.xml is setting  java source and target to 1.4
>
> It is not true: the source is 1.5, just set to 1.5 and compilation  
> was OK.
>
> But I don't think I have a SVN account ...
>   
Fixed.

-Bill

Re: [Jsynthlib-devel] Java version

[Peter G. <pet...@gm...>]

On Sun, Oct 4, 2009 at 10:23 PM, William R. Zwicky <wrz...@po...>wrote:

> denis queffeulou wrote:
> > The build.xml is setting  java source and target to 1.4
> >
> > It is not true: the source is 1.5, just set to 1.5 and compilation
> > was OK.
> >
> > But I don't think I have a SVN account ...
> >
> Fixed.
>
> -Bill
>

Could it be that this new Java version requires
generics<http://java.sun.com/j2se/1.5.0/docs/guide/language/generics.html>to
be used?
I get 100 warnings when compiling with
javac -classpath '.:groovy.jar:asm.jar' org/jsynthlib/*/*/*.java
org/jsynthlib/*/*.java

When I add -Xlint:unchecked to the command, the 100 messages are like these:

org/jsynthlib/utils/XMLWriter.java:46: warning: [unchecked] unchecked call
to addFirst(E) as a member of the raw type java.util.LinkedList
        elements.addFirst(element);
                         ^
org/jsynthlib/editorbuilder/Anchor.java:243: warning: [unchecked] unchecked
call to add(E) as a member of the raw type java.util.Collection
        listeners.add(l);
                     ^
org/jsynthlib/editorbuilder/Anchor.java:283: warning: [unchecked] unchecked
call to add(E) as a member of the raw type java.util.Set
        result.add(c);
org/jsynthlib/jsynthlib/xml/XMLPatch.java:367: warning: [unchecked]
unchecked call to put(K,V) as a member of the raw type java.util.HashMap
        cache.put(p, e);
                 ^
org/jsynthlib/editorbuilder/PGSNode.java:24: warning: [unchecked] unchecked
call to add(E) as a member of the raw type java.util.HashSet
        names.add(p.getName());
                 ^
./core/Device.java:341: warning: [unchecked] unchecked call to add(E) as a
member of the raw type java.util.ArrayList
        driverList.add(driver);
                      ^
./core/JSLFrame.java:199: warning: [unchecked] unchecked call to
WeakReference(T) as a member of the raw type java.lang.ref.WeakReference
        parent = new WeakReference(p);
                 ^

When I Googled for info, I found this forum
post<http://www.coderanch.com/t/381445/Java-General/java/compiling-under>where
it is advised to use generics when compiling for Java 1.5.

Quote from that post: "These warning have to do with generics - a good
starting point is
here<http://java.sun.com/j2se/1.5.0/docs/guide/language/generics.html>.
Basically whenever you declare a Collection or Map in 1.5, you need to tell
the compiler what sorts of things will go *into* the collection. You do this
with the new <> notation shown in the link.

Note that what you're seeing are warnings, not errors. It's possible to
ignore them. But if you use generics and make the warnings go away, you'll
get much better compile-time checking of the rest of your code that
*uses*the collections and maps.

Also, generics aren't *just* for collections and maps, but that's the most
common case - and the one that applies to your code, apparently."

Should I get started fixing those generics? I get many errors when trying to
run JSL, to test the Roland SPD-11 and Yamaha CS2x drivers that I'm writing,
so I won't mind trying to fix them. I'm just not sure if my level of Java
knowledge is appropriate for this job ... but I guess I'm right if the
switch from Java version 1.4 to 1.5 means we can (should?) now use generics,
and we didn't before.

Re: [Jsynthlib-devel] Yamaha FB01, Waldorf Micro Q and Roland D-5 drivers

[Maciej Ł. <loz...@o2...>]

Hi Robert!

Thanks for the link, I'll try this for sure. But why isn't your driver 
included in Jsynthlib?

cheers
Maciek


Robert Wirski pisze:
> Hello Maciek,
> in fact I have developed Waldort Q driver some time ago.
> As I have not used it for long I am not sure about its state.
> You can get it from jsynthlib.republika.pl/WaldorfQ.zip
> Cheers,
> Robert.
> 
> 

Re: [Jsynthlib-devel] Yamaha FB01, Waldorf Micro Q and Roland D-5 drivers

[Peter G. <pet...@gm...>]

Hi
I've setup a new page on the wiki to list all drivers that are being
developed: http://jsynthlib.wikispaces.com/development-list

KorgHAWK800 by Michael Hawkins
Proteus 2500 by fjskinne
Roland SPD-11by freakrush aka Peter Geirnaert
Yamaha AN1X by Gerald Raucamp
Yamaha FB01, Waldorf Micro Q and Roland D-5 by Maciej Łoziński

In case I forgot some, please let me know.

Thanks in advance.

Have a nice day :)
Peter

PS: today I had a member request from "fjskinne" on the wiki, he's working
on a Proteus 2500 driver.


2009/10/22 Maciej Łoziński <loz...@o2...>

> Hi Robert!
>
> Thanks for the link, I'll try this for sure. But why isn't your driver
> included in Jsynthlib?
>
> cheers
> Maciek
>
>
> Robert Wirski pisze:
> > Hello Maciek,
> > in fact I have developed Waldort Q driver some time ago.
> > As I have not used it for long I am not sure about its state.
> > You can get it from jsynthlib.republika.pl/WaldorfQ.zip
> > Cheers,
> > Robert.
> >
> >
>
>