jmatlink-devel — discussion about development of JMatLink

[Jmatlink-devel] Release of JMatLink 1.2.0

[Stefan M. <st...@he...>]

Dear everybody,

I would like to inform you that a new release of JMatLink is available:

Release ID: JMatLink 1.2.0
WWW:        http://jmatlink.sourceforge.net/
Files:      http://sourceforge.net/projects/jmatlink

Changes:
-  added mechanism to stop and start the engine
    thread. If no connection to matlab is active the
    engine thread is terminated. Upon opening a new
    connection the thread is started again.
    No need to call jmatlink.kill() any more.

- added ant build script for windows

- added more useful text if loading of the native the library failed.

- changed some return values in JMatLink.c from "NULL" to "0"

- added more testcases for JUnit

- updated the javadoc documentation

- bugfix for engGetArray(int ,) -> engGetArray(long, )

Please download the package and give feedback about you needs for future
releases.

In case you require a special feature please send me an email.


With kind regards,
    Stefan Mueller.

[Jmatlink-devel] Release of JMatLink 1.1.0

[Stefan M. <st...@he...>]

Dear everybody,

I would like to inform you that a new release of JMatLink is available:

Release ID: JMatLink 1.1.0
WWW:        http://sourceforge.net/projects/jmatlink
Changes:
- fixed some problems with engOpen, engClose, engOutputBuffer
- added engOutputBuffer(length) as function for engOpen(),
   engEvalString(String), engClose()
- implemented first working version of different output buffers.
   New behavior of engOutputBuffer(ep, len) and engGetOutputBuffer(ep)
- changed CoreJMatLink.java to support original engGetVariable() and
   engPutVariable() methods
- added EnduranceTest01.java to test the engine interface over
   a long period of time (>1hour). I already found a memory
   leak with the help of this new program.
- fixed  JMatLink.c memory leak in engPutVariableNATIVE


Examples for the new features:
- Close all connections to matlab
   long a,b;
   JMatLink engine = new JMatLink();
   engine.engOpen();                    // start the general session
   engine.engEvalString("x=rand(5)");
   a = engine.engOpenSingleUse();       // start first  matlab session
   b = engine.engOpenSingleUse();       // start second matlab session
   engine.engEvalString(b, "surf(peaks)");
   engine.engEvalString(a, "array = randn(23)");
   engine.engCloseAll();      // Close all connections to matlab

- Get the outputs of previous command from matlab's workspace.
    String buffer;
    JMatLink engine = new JMatLink();
    engine.engOpen();
    engine.engOutputBuffer();
    engine.engEvalString("x=rand(4)");
    buffer = engine.engGetOutputBuffer();
    System.out.println("workspace " + buffer);
    engine.engClose();


Please download the package and give feedback about you needs for future
releases.

In case you require a special feature please send me an email.


With kind regards,
    Stefan Mueller.

[Jmatlink-devel] Release of JMatLink 1.0.1

[Stefan M. <st...@he...>]

Dear everybody,

after picking up the development of JMatLink again. I would like to 
inform you that a new release of JMatLink is available:

Release ID: JMatLink 1.0.1
WWW:        http://sourceforge.net/projects/jmatlink
Changes:
- moving to a new development environment at sourceforge.net
- moving all classes into the package called "jmatlink"

Please download the package and give feedback about you needs for future 
releases.

Current activities:
- adaptation of JMatLink to the new engine API of MATLAB
- creation of testcases for JUnit
- creation of more examples
-....

With kind regards,
   Stefan Mueller.

[Jmatlink-devel] Re: JMatLink directory structure

[Keith M. <mas...@ya...>]

That sounds pretty good to me.  I am in favor of
leaving JMatLink.h named JMatLink.h -- it's easier on
the eyes, and it will not be re-generated very often.

Keith


--- Stefan Mueller <st...@he...> wrote:
> Dear Keith,
> 
> these are my current ideas for a directory structure
> in CVS at 
> sourceforge.net
> 
> jmatlink/  	main directory (CVS module)
> 
> jmatlink/src    source directory
> jmatlink/src/jmatlink/JMatLink.java
> jmatlink/src/jmatlink/JMatLink.c
> jmatlink/src/jmatlink/JMatLink.h
> jmatlink/src/jmatlink/ui         directory for user
> interfaces
> jmatlink/src/jmatlink/testsuite  directory for junit
> testcases
> 
> jmatlink/bin/            directory for all classes,
> DLLs
> 
> jmatlink/doc/            directory for documentation
> files
> 
> Maybe JMatLink.h should be renamed to
> jmatlink_JMatLink.h as it comes 
> out of "javah -jni ...".
> 
> Would do you think?
> 
> Best regards,
>    Stefan.
> 
> 


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new Resources site
http://smallbusiness.yahoo.com/resources/