The idea here is simple.
If you only change the code for a single part, you would only wish to output the polygon (STL or collada) for that part of those it also changes.
This way the GUI layer will only need to make an update for those parts, rather than regenerate the whole model.
I assume this is NOT implemented yet ?
I am thinking that the compilation stage can use reflection to output a serialisable description of these linkages so that it is understood.
This will allow scaling the creation of the model in a Map Reduce type logic across many nodes for large speed up on complex models whihc i intend to work n with this code.
It would also allow the GUI to show to the end use this relationship between parts of the whole model, and to be taken to the code where that part applies.
Pretty nice i think to maximise the usability of this library.
The serialisation aspect of the linkages i am not sure how to do in c++ myself.
Any ideas / thoughts about this wish ?
The idea here is simple.
If you only change the code for a single part, you would only wish to output the polygon (STL or collada) for that part of those it also changes.
This way the GUI layer will only need to make an update for those parts, rather than regenerate the whole model.
I assume this is NOT implemented yet ?
I am thinking that the compilation stage can use reflection to output a serialisable description of these linkages so that it is understood.
This will allow scaling the creation of the model in a Map Reduce type logic across many nodes for large speed up on complex models whihc i intend to work n with this code.
It would also allow the GUI to show to the end use this relationship between parts of the whole model, and to be taken to the code where that part applies.
Pretty nice i think to maximise the usability of this library.
The serialisation aspect of the linkages i am not sure how to do in c++ myself.
Any ideas / thoughts about this wish ?