OK guys! Prepare yourself for one amazing ride
MB3D project will be rebooted, and I am going to spear head the development.So, what's the plan?
We know how the original works from the point of view of the end user. We also have the source code, so we know how it works from the point of view of algorithms and programming. So this is what we are going to do:
1. Restart from scratch. There are far to many things wrong with the original code base to try to continue to work with it.
2. From the start, think of design and structure of the project.
3. Come up with a list of features that definitely need to make their way into the new project from the old one.
4. Tackle the problem of MB3D custom functions. This will be the most time consuming part. The original custom functions will have to be reverse-engineered so that they can be made to work in the new code base. From a technical point of view - this is a straight forward task. It's just going to take a lot of time. And I mean A LOT OF TIME!
5. Create a new UI design. We have been using 3D fractal programs for about 5 years now. So we have some kind of expectations from what the UI should look like, and how it should behave.Why am I doing this?
1. This is a tremendously difficult technical task. I want to work on something really challenging.
2. I want to save all the work put into MB3D. I think it was a great project, and all the work people did for it (with it) should not go to waste.
3. All this time I have been using other people's 3D fractal software. Now I want to give something back to the community.Brainstorming
I need your input in this thread on the following:
1. Project name. Should we keep the original name, and just call it version 2? Should we name it something different?
2. List of features that you'd like to see carried over from MB3D.
3. Any new features you want. For example something that is currently in other 3D fractal programs.
4. UI design mock ups, sketches, ideas, etc.
5. Technical side of things. Suggestions for programming language, UI library, architecture, etc.
6. Input on anything else I am forgetting right now.
Even if you don't plan to contribute something in the form of code, visual designs, etc., I still want to hear from you!
!!! For the summary of this thread see comment #68 !!!