Is this really a good idea or should IronCAD be developing
much more robust surfacing rather than trying to rely on
Rhino ? I watched the presentation on IronCAD's website and
could not figure out for the life of me why someone would
want to go back and forth between IronCAD and Rhino for
something as simple as what they show.
Am I missing something and if I am missing something what
*exactly* am I missing in regards to why this integration is
a good thing vs IronCAD having decent surfacing on it's own.
For example, VX's Vision and think3's thinkdesign could do
this on their own. In either Vision or thinkdesign you would
not have to constantly boogie back and forth between two
separate applications with two separate interfaces.
Please enlighten me because I sure don't see why this is a