existence of rhinocommon counterparts for GH components for porting purposes

Dear reader,

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?

Is there a table containing GH component <=> rhinocommon methods/properties?

We have recursively scanned our definitions/clusters for used grasshopper components (Name) and categorized them. Just to give you an idea, below you'll find a subset of what I think are rhino/cad specific components that we use. Most of them are very obvious but some of them I'm not really sure. I'm interested in the ones that are not covered by rhinocommon.

Area
Area Moments
Boundary Surfaces
Bounding Box
Box Properties
Box Rectangle
Brep Closest Point
Brep Edges
Circle
Circle CNR
Closed
Connect Curves
Construct Point
Curve | Line
Curve | Plane
Curve Closest Point
Curve Proximity
Curve To Polyline
Deconstruct
Deconstruct Box
Deconstruct Brep
Distance
Divide Curve
Divide Length
End Points
Evaluate Curve
Evaluate Length
Evaluate Surface
Explode
Extend Curve
Flip Curve
Join Curves
Line
Loft
Move
Offset
Plane Closest Point
Point In Brep
Point In Curve
Point Polar
Polygon Center
PolyLine
Rectangle
Seam
Shatter
Sub Curve
Surface Closest Point
To Polar
Unit Z
Vector 2Pt
Vector XYZ
Volume
XY Plane

Replies to This Discussion

Permalink Reply by Michael Pryor on July 31, 2017 at 12:47pm

Check the API to see what is there or not.

Permalink Reply by WP Lee on July 31, 2017 at 3:10pm

Thanks Michael, I will do that. Currently, I'm quite familiar with the GH components but not quite with the API. I noticed that some things are just named differently or require "preparations" beforehand. So at this stage if I'm unable to figure something out I don't know whether it's because I just don't understand how things are setup with the API or it just doesn't exist in Rhinocommon.

I hope someone can glimpse at the list and points out which ones need more attention. This would be easy for an expert in both grasshopper and the rhinocommon API, I imagine. Having this information can help a lot for planning the whole porting exercise of our grasshopper "code base". Our code base is becoming to big to maintain and build on with grasshopper components.

Permalink Reply by Michael Pryor on July 31, 2017 at 5:31pm

Permalink Reply by WP Lee on July 31, 2017 at 6:00pm

What the … thanks man! Just a short list of the more "problematic" ones would have been fine. I would have digged in those myself then to set the priority. All these links however are more then I ever expected. I think you saved us a lot of time and hope I haven't wasted too much of yours.

Permalink Reply by Michael Pryor on July 31, 2017 at 9:17pm

Sure thing, Hope it helps!

RSS