algorithmic modeling for Rhino
Comment
I'm a little bit obsessed with order in definitions too, hehehe. I guessed that but it would be very nice to have them as customizable native components.
Off topic: The sub-canvases idea was one that I suggested some time ago arguing that the linear (left to right) gh definition growing logic clash directly with an efficient workflow with big definitions (limited with the one-core only support too).
Angel: Guess I'm a bit of a stickler when it comes to keeping definitions "clean" :) Those are just scribbles and a line loaded from Rhino by the way. But yes, some super-system of groups might be an idea (sub-canvases maybe?).
Greg: Great to see you onboard, loving those gifs as you well know ;) Michel and I were discussing some ideas for how to better deal with connecting the various modelling environments. Should talk soon..
Alexander: Thanks, that's correct. The width of the knitting machine was a pretty hard constraint, so getting every little bit into the knit bounding box was crucial.
This is great. Very believable. That end bit with galapagos.. Are you just matching a best fit rectangle? Maybe for fabrication? Thats a fun solution if so.
Great stuff! And for those of you who wondered what we engineers do with Anders' geometries:
Loving how you organizr the gh definition layout :) Those separation lines and titles could be a great request to David for the next release :)
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
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by
You need to be a member of Grasshopper to add comments!