algorithmic modeling for Rhino
I'm posting this python component because I have a feeling it will be redundant/unnecessary in the near future due to the upcoming implementation of Yak. (which sounds awesome).
This component was a good learning experience for me and I thought I would share. Hopefully there are some bits that might help you too.
With that said it will analyze the current GH document, and perform 2 actions:
This type of (de)serialization of information is valuable when multiple people are working/sharing files. Perhaps a more interesting/future development would be writing the information to a database, and over time, your organization could start to see trends.
I am posting two versions of the user objects.
1 - the procedural version, done in rhino 5. (GetComponents3.ghuser)
2 - the SDK mode version, done in rhino 6, ready to be compiled...as of the current WIP. (this will not work in rhino 5). (GetUsedComps_SDKMode)
There are too many people to thank for continually contributing to this forum, but I would be remiss if I did not specifically mention
Giulio Piacentino, Andrew Heumann, Anders Holden Deleuran, and Brian Ringley. I have learned a lot from your discussions and contributions to the forum. Thanks!