algorithmic modeling for Rhino
For example, storing the workflow or calculation components in one file, and call the data or geometry from another GH files if needed.
This is to prevent from the GH file from getting larger and larger as components storing data increasing ...
Appreciate your suggestions!
Tags:
Hi,
you can write your data in text files or you can save your data as a class. This data can be loaded in other GH instances.
===> some C# knowledge will be needed
Cheers,
Raul
there are lots of ways to think about this. Personally I rely on storing data OUTSIDE of GH files - in text files, like raul suggests, or in Rhino files when the data is specifically geometric (Human or elefront both let you embed arbitrary additional user data into objects). It is also possible to embed persistent data into a file (by "internalizing" the data into a param) and then read this data back out later from another file. Unless there's a strong reason to store the data directly IN the GH file I would encourage you to use a text/database-based solution (I am personally fond of Pack/Unpack data from TreeSloth)
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by