I have posted something similar to this before but I would like to hear by some other users if they also think this would be greatly advantageous to how Rhino and Grasshopper interact, and to be honest I am kind of hoping someone could for now maybe make a VB script component that could kind of do this for now.
I find more and more instances where I need data from Rhino objects in Grasshopper but that data cannot stay saved in the Rhino file, many reasons for that but moving on, for now Grasshopper can only reference to geometry in rhino but not save it.
Three things I can quickly think of where this could be useful.
- An accompanying separate Rhino file will no longer be needed. This then obviously also takes away the need to every time you open a rhino file having to select all the parameters again.
- Sometimes you cannot have the rhino geometry you needed to work off(Input) in the Output file you would present/deliver to someone and in that case the Input needs to be REDRAWN in Grasshopper and having the ability to have a component that has saved Rhino geometry in GH will save huge amounts of time.
- As much as I love creating geometry in GH, sometimes it is much faster to create it quickly in Rhino and then save it in GH and then use it for the definition. Now I realize this would probably change a lot in the way people work in GH, for some they would probably create less in GH and more in Rhino and use GH more as a utility for certain actions with the geometry.
I am very interested in others opinions on this.
Theunis
Tags: