X3D has been in development for over a year now. At times, progress has been very fast, and other times, it's gone painfully slow. I've learned many hard lessons on how to become a good developer over the course of writing it. However, I have tended to rush things and, overall, have made a terrible mess of the project. While I am not totally starting over, I am creating a development plan on how to move forward because, right now, the code is too terrible to continue. It's time to do things right so that the project actually makes some progress.
The new version of X3D will following the following development strategy:
- Development will be broken into phases, or iterations. That way, we have a goal that we're moving towards.
- At the end of each phase will be a small, working game that the community can play around with.
- Feedback will be welcome at anytime and bugs will no longer hang around for months :) It would be awesome if some programmers would be willing to mess around with the library and create some things so I can get feedback!
- A phase must be stable before moving onto the next one.
- No hacky solutions will be implemented to rush things, as this just creates technical debt that must be dealt with later. Also, code must be kept clean at all times!
- The entire development process will be transparent so people know what's being developed. Also, people can join the project anytime if they want to contribute.
If you're curious as to what the current development plan looks like, take a look here. (https://www.evernote.com/shard/s729/sh/78e79545-620a-453d-adee-d4aea2dfece0/443de23bbdf9df2d941f4479e35ad06f)
At anytime, to see what's currently in development, please see the Trello board here (https://trello.com/b/K4dywfJa/x3d).
Please let me know if you have any feedback or suggestions!
As long as it's not the beginning of an endless series of rewrites, then it's a good move :). Hopefully you can maximize speed while keeping the size down from this. :3=