Python in Grasshopper (guid and geometry)

Grasshopper
4

I’m not sure you will find a common practice as such, but I certainly prefer and advocate to implement RhinoCommon directly (for many reasons, if you search this forum and the old Grasshopper one you’ll find many topics related to this).

Edit: A few of my key preference points for RhinoCommon:

  1. No GUID/coercing business.
  2. No missing functions/methods (i.e. that have not been ported).
  3. Better performance.
  4. Easy porting to C#/VB.
  5. OOP.

That said, I still implement rhinoscriptsynax when interfacing the Rhino document.

6 Likes