Horde3D

Next-Generation Graphics Engine
It is currently 13.04.2021, 11:52

All times are UTC + 1 hour




Post new topic Reply to topic  [ 21 posts ]  Go to page 1, 2  Next
Author Message
PostPosted: 03.06.2012, 01:50 
Offline

Joined: 03.06.2012, 01:41
Posts: 2
Hi I would like to know if there is a up to date roadmap for horde3d.


Top
 Profile  
Reply with quote  
PostPosted: 04.06.2012, 08:58 
Offline
Tool Developer

Joined: 13.11.2007, 11:07
Posts: 1149
Location: Germany
Next step would be focusing on GLES support and Android and IOS examples.


Top
 Profile  
Reply with quote  
PostPosted: 20.09.2013, 10:35 
Offline

Joined: 08.01.2008, 14:57
Posts: 66
I think it's time to write down a new roadmap plan for the next planned releases.

Something like:

Horde3D 1.0.0
    * OpenGL ES2 backend.
    * Improved animation API.
    * Other bug fixes.

Horde3D 1.5.0
    * Direct3D 11 backend.
    * Other bug fixes.

Horde3D 2.0.0
    * Moving scene graph to utility lib.
    * Model resources.
    * Other bug fixes.

Each final release could be composed by multiple-stage releases (i.e. alpha -> beta -> release candidate).

I also propose to edit the out-of-date roadmap page on the wiki to point at the milestones page of the official GitHub repository (that we need to populate).


Top
 Profile  
Reply with quote  
PostPosted: 20.09.2013, 12:38 
Offline
Tool Developer

Joined: 13.11.2007, 11:07
Posts: 1149
Location: Germany
I agree with the plans for 1.0.0
But before this can be released, a working example for all current samples (terrain,chicago and knight) on Android and IOS are IMHO mandatory. So there's still a lot to do regarding shadows and fallbacks in case of no floating point, depth texture support or shadow samplers.


Top
 Profile  
Reply with quote  
PostPosted: 20.09.2013, 16:15 
Offline

Joined: 08.01.2008, 14:57
Posts: 66
Yes, of course these basic samples are mandatory.

If you agree you can add a new "1.0.0" milestone to the GitHub repository so we can start to assign issues to it (well, only you have the rights, in reality) .


Top
 Profile  
Reply with quote  
PostPosted: 30.09.2013, 15:05 
Offline

Joined: 08.01.2008, 14:57
Posts: 66
I moved the old community roadmap to a new page called Community Roadmap deprecated, while the official page lists now a cleaner status of current development focuses:

http://www.horde3d.org/wiki/index.php5? ... ty_Roadmap

Feel free to post here your comments and suggestions about improving it.


Top
 Profile  
Reply with quote  
PostPosted: 30.09.2013, 15:29 
Offline

Joined: 21.08.2008, 11:44
Posts: 354
Regards to the 1.1.0 release, doesn't double precision variables support require a new OpenGL4 backend? Or is it going to be done through some OpenGL extensions wizardry?


Top
 Profile  
Reply with quote  
PostPosted: 30.09.2013, 16:22 
Offline

Joined: 08.01.2008, 14:57
Posts: 66
You're right.

My point was that also DirectX 11 supports them, according to this page:

http://rastergrid.com/blog/2011/10/open ... -from-over

BTW, I changed the page with a new milestone (1.2.0) with OpenGL4 backend and support for double precision (on both OGL and DX).


Top
 Profile  
Reply with quote  
PostPosted: 01.10.2013, 08:29 
Offline

Joined: 28.12.2010, 21:38
Posts: 5
Location: Wilkes, Barre Pa
The road-map looks good except "Direct3D 11" hardly any games even use DirectX anymore with the exception to Windows and Xbox only games. other than that everyone uses OpenGL.

I would focuses on ..
    GLES.
    Different Types of Scene-graphs.
    Shaders.
    More work done on the Blender Exporter.


Top
 Profile  
Reply with quote  
PostPosted: 01.10.2013, 12:34 
Offline

Joined: 08.01.2008, 14:57
Posts: 66
Well, Windows (also on mobile devices) it's a big piece of the cake (note: I'm a Linux user)...

BTW, the reason is that the DirectX 11 renderer is already working in progress by attila, so it's a good idea to not waste his efforts.


Top
 Profile  
Reply with quote  
PostPosted: 04.10.2013, 12:45 
Offline

Joined: 08.01.2008, 14:57
Posts: 66
I'm also thinking if, maybe, it's better to plan a 1.0.0 (final) release only with the current API and renderer (>OpenGL2) to provide a basic release for the current Horde3D-based applications (which requires simply something official, stable and with all the fixes contained in the old community svn repo to link to).

After this basic milestone, we can safely continue adding new renderers or doing big changes to the engine structure. This also allows us to release often with quite atomic changes between releases, providing a better development work-flow.

What do you think?


Top
 Profile  
Reply with quote  
PostPosted: 04.10.2013, 13:16 
Offline
Tool Developer

Joined: 13.11.2007, 11:07
Posts: 1149
Location: Germany
I aggree. I discussed that with marciano several month ago. He didn't want to release Horde3D as a "final" 1.0 because he wanted to improve several things before making a final release.

After all I think because of the lack of time, it would be better to have a stable 1.0 release based on the current state and let the community add new fundamental changes in a new development repository based on git (as we already started now). I will then try to merge nearly every pull request into that development branch. If development settles and the state becomes stable and compilable on all supported platforms again, we can release a new version (in the release branch, as well as on SourceForge file downloads).


Top
 Profile  
Reply with quote  
PostPosted: 04.10.2013, 13:57 
Offline

Joined: 08.01.2008, 14:57
Posts: 66
Changed the roadmap, accordingly.

Now, before the final 1.0.0 release, I think we should make a call for a in-deep bug testing.

BTW, we don't really need a "releases" branch on GIT, we already have the tag system (at the end, a release is simply a specific revision, fixed in time, of the repo tagged with a name).


Top
 Profile  
Reply with quote  
PostPosted: 04.10.2013, 14:31 
Offline
Tool Developer

Joined: 13.11.2007, 11:07
Posts: 1149
Location: Germany
I thought there should be a branch that always have the latest bug fixes for the current stable release, that what the releases branch was created for, shouldn't it?


Top
 Profile  
Reply with quote  
PostPosted: 04.10.2013, 16:41 
Offline

Joined: 30.09.2010, 03:06
Posts: 21
Have you read about "git-flow" is only something about how to organize tags (you can do it without the extension, is only organization)


For example:

Production branch: default
Development branch: develop

Feature branch prefix: feature
Release branch prefix: release
Hotfix branch prefix: hotfix
Version tag prefix: -----


http://nvie.com/posts/a-successful-git-branching-model/
https://github.com/nvie/gitflow
perhaps http://danielkummer.github.io/git-flow-cheatsheet/

(by the way, and for the one that like to know, this "model/organization" was also migrated to a mercurial extension)


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 21 posts ]  Go to page 1, 2  Next

All times are UTC + 1 hour


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group