Re: [Java-player-users] JavaClient for Player/stage 2.1.x ?

[Leo N. <leo...@gm...>]

I agree with Radu. Wrappers are there to solve very specific problems, not
to wrap every C or C++ program or library to say it works on Java.

Obviously I will not complain if you develop the wrappers and they work
properly, it's your work and your effort, but I guess it will be more
painless and useful to design and develop a correct java solution.

The first and biggest drawback of a JNI approach I think will be the fact
that you will be developing a JavaClient tight to an specific OS (likely
linux). For me it's not a solution coz I work with all three major OS
(usually in MAC) but ... if it's enough for you and some other people, once
more I will not complain about that :)

Probably the best solution I see is to design a correct and proper Java
based solution, having in mind what is already developed, but not
compromising a good solution due to a not too good but already done
solution, and then consider a collaborative development.

Radu and I, do not have much free time, but I hope we will be able to
develop or at least give a ray of light in some aspects or some peaces of
the code.

Hope to be of any help.

Bests
Leo

2008/11/7 Radu Bogdan Rusu <ru...@cs...>

> Actually I haven't. When I started coding JavaClient, the swig interfaces
> that we were using for the python library were
> crap.
>
> Personally I don't like wrappers all that much, but hey, if it works, and
> people are happy, why not :)
>
> Radu.
>
> Tung Nguyen wrote:
> > Hi Radu and Leo,
> >
> > Thanks for your replies to my previous question, I really appreciate
> > them. I have another question for you though:
> > I'd like to know if using JNI to wrap around the player C (or C++)
> > client lib is another feasible/reasonable solution for communicating
> > with the player server.
> > I saw elsewhere people were considering using either JNI or CORBA for
> > this purpose.
> >
> > I guess you guys have already considered this option instead of writing
> > a java client completely from the ground up. If this is true, I would
> > really like to know the drawbacks of the JNI approach (if it's
> > reasonable at all) as opposed to writing a client from scratch
> > (JavaClient2).
> >
> > Thanks,
> >
> > Tung,
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> > Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> > Grand prize is a trip for two to an Open Source event anywhere in the
> world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Java-player-users mailing list
> > Jav...@li...
> > https://lists.sourceforge.net/lists/listinfo/java-player-users
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Java-player-users mailing list
> Jav...@li...
> https://lists.sourceforge.net/lists/listinfo/java-player-users
>



-- 
**************************************
Leonardo Nomdedeu Calvente
leo...@gm...