Re: Java 1.6.0 pre12 with JOGL 2.3.1 crashes under OpenSUSE 13.2 with Mesa
Posted by Sven Gothel on Oct 13, 2015; 6:46am
URL: https://forum.jogamp.org/Java-1-6-0-pre12-with-JOGL-2-3-1-crashes-under-OpenSUSE-13-2-with-Mesa-tp4035401p4035457.html
On 10/13/2015 08:30 AM, Andreas [via jogamp] wrote:
> I want to ask for an advice. Due to this bug an other shortcomings Julien is
> pointing to in this forum, I'm thinking about switching from Java3D to another
> library like JogAmp's Ardor3D Continuation or pure jogl. What I want to do is
> just visualising and viewing 3D shapes and rotate them with the mouse (for
> Java3D these are QuadArrays and TriangleArrays with automatic calculated
> normals or manually calculated normals). This has to work in a
> multitab/multicomponent environment. You can find examples screen shots at
> http://www.elamx.de .
> Why I was using Java3D up to now? It was quite simple with tons of tutorials
> and example code. I just had to add the JCanvas3D to my application, put some
> Shapes3D into a Branchgroup with a Transform for rotation, put everything
> together and I was done. So I'm really just a user and not able to help with
> resolving bugs and stuff like that.
> I thought the easiest way is switching to jReality. But there seems to be no
> further development. The actual stable still works and only works with jogl
> 2.0.0 or something.
>
> What would you do?This is a hard question!
It depends .. of course.
Probably the main criteria is whether your work
shall survive for a few more years, hence you need
your tools to be maintained.
In this case, contact the vendor/maintainer and ask them
about future development / maintenance.
Here, it surely is essential that you don't pick an EOL component,
especially if it is a complex one.
Otherwise you simply can use any tool, ship it and forget it,
i.e. for just a demo covering a scientific paper :)
For a real product, well, it has often been realized
that starting w/ a tool is a good idea.
Later, usually development moved to a custom scenegraph solution
matching requirements and hence sweetens performance.
Yes, tools are always a hard choice!
~Sven
>
> Andreas
>
URL: https://forum.jogamp.org/Java-1-6-0-pre12-with-JOGL-2-3-1-crashes-under-OpenSUSE-13-2-with-Mesa-tp4035401p4035457.html
On 10/13/2015 08:30 AM, Andreas [via jogamp] wrote:
> I want to ask for an advice. Due to this bug an other shortcomings Julien is
> pointing to in this forum, I'm thinking about switching from Java3D to another
> library like JogAmp's Ardor3D Continuation or pure jogl. What I want to do is
> just visualising and viewing 3D shapes and rotate them with the mouse (for
> Java3D these are QuadArrays and TriangleArrays with automatic calculated
> normals or manually calculated normals). This has to work in a
> multitab/multicomponent environment. You can find examples screen shots at
> http://www.elamx.de .
> Why I was using Java3D up to now? It was quite simple with tons of tutorials
> and example code. I just had to add the JCanvas3D to my application, put some
> Shapes3D into a Branchgroup with a Transform for rotation, put everything
> together and I was done. So I'm really just a user and not able to help with
> resolving bugs and stuff like that.
> I thought the easiest way is switching to jReality. But there seems to be no
> further development. The actual stable still works and only works with jogl
> 2.0.0 or something.
>
> What would you do?
It depends .. of course.
Probably the main criteria is whether your work
shall survive for a few more years, hence you need
your tools to be maintained.
In this case, contact the vendor/maintainer and ask them
about future development / maintenance.
Here, it surely is essential that you don't pick an EOL component,
especially if it is a complex one.
Otherwise you simply can use any tool, ship it and forget it,
i.e. for just a demo covering a scientific paper :)
For a real product, well, it has often been realized
that starting w/ a tool is a good idea.
Later, usually development moved to a custom scenegraph solution
matching requirements and hence sweetens performance.
Yes, tools are always a hard choice!
~Sven
>
> Andreas
>
signature.asc (828 bytes) | Free forum by Nabble | Edit this page |