A new binary build available soon

classic Classic list List threaded Threaded
45 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Re: A new binary build available soon

gouessej
Administrator
This post was updated on .
Hello

The examples based on ardor3d-craft are working.

I'll add a roadmap into the project:

1.0.0:
- Inconsistent management of relative and absolute positions in ardor3d-math (for example in the way of managing the position of the buffers)
- Revamping and improvements in the exporters (allowing exports of complicated scenegraphs with hierarchies of nodes)
- Strengthening of the documentation (mostly done but the user's guide still lacks some explanations)
- Import MD2 models more accurately as an option (i.e add an option to split the models into more parts without the useless links that may cause some problems when trying to detect collisions)
- Drive some core utilities overridable (i.e avoid (ab)using the "static" keyword in those utilities)
- Drive all render state utilities overridable
- Switch to JOGL 2.4.0
- ardor3d-jogl-jfx based on NewtCanvasJFX
- Java 11 (but I'm blocked by a bug in Maven)

1.1.0:
- Constructive Shape Geometry
- BVH import
- Support TrueType fonts (I don't remember where the contribution on this is :s)
- OFF import (very low priority)

2.0:
- GLTF import and export
- Vulkan renderer
- ardor3d-web-ui
- Improvements of ardor3d-math in order to compete with JOML
- A brand new name for the project?

P.S: I've just uploaded the new binary build.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: A new binary build available soon

gouessej
Administrator
Hello

JogAmp's Ardor3D Continuation will use the JogAmp's bug tracker from now on:
https://jogamp.org/bugzilla/buglist.cgi?product=Ardor3D

I'll add the known bugs into it very soon.

I've just updated the wiki section about JogAmp's Ardor3D Continuation:
https://jogamp.org/wiki/index.php?title=Main_Page#Ardor3D
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: A new binary build available soon

Sven Gothel
Administrator
On 9/5/19 12:42 PM, gouessej [via jogamp] wrote:
> Hello
>
> JogAmp's Ardor3D Continuation will use the JogAmp's bug tracker from now on:
> https://jogamp.org/bugzilla/buglist.cgi?product=Ardor3D
>
> I'll add the known bugs into it very soon.
>
> I've just updated the wiki section about JogAmp's Ardor3D Continuation:
> https://jogamp.org/wiki/index.php?title=Main_Page#Ardor3D

Great Julien, thank you!

~Sven


Reply | Threaded
Open this post in threaded view
|

Re: A new binary build available soon

gouessej
Administrator
Sven Gothel wrote
Great Julien, thank you!
You're welcome. Actually, in my humble opinion, JogAmp stuff should be in one place and JogAmp sub-projects should have similar policies on licensing, bug reporting, communication, ... It would be easier to explain for us, easier to understand for newcomers and easier to manage for us.

For example, if we systematically encourage our users to ask their questions preferably here, the people most able to answer (often the maintainers and the contributors) won't have to waste some time on social media and third party websites, they will be able to focus on their tasks and they will have a single place to control. Personally, I won't register everywhere on Internet to answer questions about JogAmp APIs and I'm probably not alone in this case. The situation is becoming problematic on Github because I seriously plan to leave it and it would be a more comfortable change for me if all maintainers refrained themselves from managing issues and pull requests on it because I often have to reply. Charity begins at home, I've repeated for years on StackOverflow that JOGL specific questions should be posted on our forum and I'll leave StackOverflow one day. Github should have been used only as a mirror from the very beginning and it's perfectly fine for me not to use it at all. I don't want to get much visibility at the price of giving much power to Microsoft.

It reminds me that some precious resources should be moved or at least copied into the wiki.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: A new binary build available soon

Sven Gothel
Administrator
On 9/6/19 9:55 AM, gouessej [via jogamp] wrote:
>     Sven Gothel wrote
>     Great Julien, thank you!
>
> You're welcome. Actually, in my humble opinion, JogAmp stuff should be in one
> place and JogAmp sub-projects should have similar policies on licensing, bug
> reporting, communication, ... It would be easier to explain for us, easier to
> understand for newcomers and easier to manage for us.

Julien, what you describe below is surely the default recommendation
and I agree of course.

Official channels are from jogamp.org: git, bugzilla, wiki, forum, etc.

The github repo and others are, as you said, just a backup for convenience.

If anybody answers other questions, they might want to drop the answer in
this forum, wiki, bugzilla and give the source a link.
Just an example to not lose valuable information, if so.

~Sven

>
> For example, if we systematically encourage our users to ask their questions
> preferably here, the people most able to answer (often the maintainers and the
> contributors) won't have to waste some time on social media and third party
> websites, they will be able to focus on their tasks and they will have a
> single place to control. Personally, I won't register everywhere on Internet
> to answer questions about JogAmp APIs and I'm probably not alone in this case.
> The situation is becoming problematic on Github because I seriously plan to
> leave it and it would be a more comfortable change for me if all maintainers
> refrained themselves from managing issues and pull requests on it because I
> often have to reply. Charity begins at home, I've repeated for years on
> StackOverflow that JOGL specific questions should be posted on our forum and
> I'll leave StackOverflow one day. Github should have been used only as a
> mirror from the very beginning and it's perfectly fine for me not to use it at
> all. I don't want to get much visibility at the price of giving much power to
> Microsoft.
>
> It reminds me that some precious resources should be moved or at least copied
> into the wiki.
123