algorithmic modeling for Rhino
Hi all !
(and especially to David Rutten)
After the response to this thread , i decided to make a thread with only my ideas. everyone is welcome to comment on them, but if you have your own ideas, please don't post them here, but make a separate thread in respect to Davids request.
I keep adding new ideas (from small useful tweaks to component proposals), but you have to check the latest pages.
1st idea: receivers for everyone! (the crowd goes wild)
i'm thinking, why not make each input hook be able to work as a receiver. it could be chosen from the right-click menu, and the waves graphic can appear (as in the receiver component) around that hook.
an advantage of this would be, that if you start with a bunch of components near the input components area, and then decide to make room in between this two sets for a new set, it is useful to get rid of the current connection lines that would make that area messy. it would be easier to just change the status of the hooks, rather then create a receiver for each input data needed, and redraw the connections.
2nd idea: preview selected only button
near the "preview mode" button, there could be an on-off "preview selected" button,that when is pushed, only displays the component(s) that is/are selected
it happens often that i am working in one part of the definition, that generates a certain geometry and i need to see how this geometry relates to other stuff in the scene, so i need other components visible, but i also need just to check if the resulted geo looks right, and it's hard to see with other objects overlapping in the display. i currently do this: bake the current component, and then close grasshopper, or chose no preview, then switch back to shaded preview. that button would make things easier.
thanks for the interest!
awaiting some feedback
Tags:
17th idea: more primitive solids
regular and semiregular primitives would be nice to have in grasshopper, especially since rhino doesn't provide them
(mmmm...dodecahedron...)
18th idea: "bake visible" component
Bakes whichever components are currently set to visible
I'm guessing i'm not the only one that keeps just a few components visible - the ones i'm interested in and the ones i would like to bake at some point (at the end of the def, or as a test bake on the way). Would be easier then selecting each visible component to bake them or feed them all into a general geometry parameter component.
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