Hello Karsten,
>> Nevertheless a bigger review is necessary, but I can't do that....
.....Some of [the nodes] have the same or a similar function, <<
I think you are right that the starting point is to pare down the extensions by removing redundant nodes, before rationalising them into agreed menus.
With a view to that I have a couple of questions:
1) Does new node Points2/PTS2pts perform any functions beyond Objects/ObjtoArray?
2) Are Transform2/FlowObj & Transform2/mFlowObj now fully redundant since Max's version Transform/Flow?
3) Is Objects2/intersectObj now redundant since new Objects2/intersectObjMP?
4) Does Points2/Path_Array do anything not already done by Points2/mPath_Array?
5) Was Construct2/mLoft made redundant by the addition of Construct2/mLoft2?
6) Is Construct2/Project now redundant since new Construct2/ProjectMP?
7) Wasn't Objects2/Concat2 made redundant by Max's updated Basic/Concat?
Generally, I already think I know the answers to all these questions, but I need your verification in case I missed something.
I need also to do some analysis of r2d3 nodes before posing similar questions for Raif (AKA r2d3), but ultimately as part of a rationalisation, we need IMHO to move any of his non-redundant nodes into the relevant menus.
Once that is done, I will post a full listing of node menus for comment, and if agreed upon post new extensions.js
I recognise that this will create issues of backwards compatibility but it is IMHO a necessary step to promote greater adoption of NE
Thank you for your enduring support
James
|