Share 'existence of rhinocommon counterparts for GH components for porting purposes'
We are at the verge of "porting" partial grasshopper definitions and clusters to actual code build against the rhinocommon API. We are trying to assess the risks to some degree. The main question is whether we have used GH components that don't have a rhinocommon counterpart. If so, can those components be easily written with the rhinocommon API or do we require extra effort?
You can share this discussion in two ways…
Share this link:
Send it with your computer's email program: Email this