alberich wrote: ↑
Tue May 08, 2018 10:19 pm
Also, a question. For all of us cheering your progress down the field, where is the goal line? That is, what milestone is needed to be reached for A3 to be merged into the daily build?
A3 is developed as a test and demo to show that my core changes of FC works. And I think my branch is ready for merging now. There are of course lots of bugs expected, but the design of all the changes is to maintain backward compatibility first. I am not sure what the lead developers think about this, although I can understand that this is a huge changeset, approaching 50K lines of changes.
If my branch is merged, it doesn't really matter if A3 is in the master or not. It can exist as an Add-on. And I personally think it will be better to have the assembly workbench written in C++, but that won't happen until we can find a proper solver with compatible license, or write our own.
As for the road map of A3 itself, I have two big features in mind.
* Import assemblies built with A2. I personally need this, because I have huge assemblies built with A2 long time ago. I considered of doing the import since the beginning. But A3 was not matured enough to do this. I think it is ready now.
* DOF analyzer and animator. I studied SolverSpace's code for this already, and I had a rough idea how it works. I may need to patch SolveSpace solver library a little bit in order to bring out this functionality.