F3D 3.0.0 Roadmap

[mwestphal]

Context

F3D is a collaborative project, let's collaboratively construct the roadmap for 3.0.0 release!

Suggested solution

Comment and discuss below, maintainers will take suggestions into account to add to the roadmap.
Please refer to existing issue when adding comments. Feel free to create issues if your ideas are not in issues already.

3.0.0 is a major release, so breaking change are allowed and even expected at this point.

Current roadmap

This part may be updated but may not contains all issues that will be addressed.
Please look at the milestone and the board for the exhaustive list.

1. Options rework

A core development that is required for many features below:

• Rework libf3d options to use strong typing #1244

2. Interaction configuration

Initially planned for 2.3.0, it requires the option rework:

• Key Interaction management in libf3d is not great and should be improved #443

This one matters a lot because we are running out of keys and more flexibility for the users is good.
Prototype here: #1066

3. ImGui

So many issues and features rely on this one. We have been holding ideas because of it.
We need to move forward however it is probably best to wait to the options rework before working on it seriously:

• Rework UI using ImGui #1245

Prototype here: #1077

4. Generalizing loading data

When I worked on the generic importer and the renderer with options, it struck me that it should be possible to do with importers what we do with reader if we have an API for it. It is a complex one and require some VTK changes but definitely needed for the future of F3D. Does not require the options rework imo:

• The future of loading files with F3D and the libf3d #653

5. Interactive scripting from F3D

Something I've dreamt of since the begining of the project and would expose a bit of the libf3d to users:

• Command line / Scripting interactions in a vim-like manner #595

Require ImGui first though.

6. Consolidate WebASM feature

Opening F3D to website is critical for reaching many more users and developers interested to show 3D models in different context.

• Consolidate WebASM feature #1252

7. F3D options improvements

Something I've been complaining about for ages and easier to do in the context of a breaking change.

• Implicit values are causing issues in options #1114
• Limitations of cxxopts in F3D #434

[mwestphal]

Here is what I have in mind. Any of this changes will break the retrocompatibility of F3D or the libf3d and once merged, next release will be 3.0.0

1. Options rework

A core development that is required for many features below: #1244

2. Interaction configuration

Initially planned for 2.3.0, it requires the option rework: #443
This one matters a lot because we are running out of keys and more flexibility for the users is good.
Prototype here: #1066

3. ImGui

So many issues and features rely on this one. We have been holding ideas because of it.
We need to move forward however it is probably best to wait to the options rework before working on it seriously: #1245

Prototype here: #1077

4. Generalizing loading data

When I worked on the generic importer and the renderer with options, it struck me that it should be possible to do with importers what we do with reader if we have an API for it. It is a complex one and require some VTK changes but definitely needed for the future of F3D. Does not require the options rework imo: #653

5. Interactive scripting from F3D

Something I've dreamt of since the begining of the project and would expose a bit of the libf3d to users: #595

Require ImGui first though.

6. F3D options improvements

Something I've been complaining about for ages and easier to do in the context of a breaking change.

#1114, #1193, #434

[Meakk]

Maybe webasm consolidation too?

[mwestphal]

There is no issue at all for the WASM work. Could you open it and state the status and what we need to do in the future ?

[Meakk]

#1252

[mwestphal]

Thanks! Ill add that to the roadmap!

[mwestphal]

Issue text have been updated to reflect all suggestions. Comments are welcome though :)