Grasshopper

algorithmic modeling for Rhino

There is an ongoing debate in my office between those who like to organize their definitions with hidden wires for the sake of cleanliness, and those who hate them because it makes definitions hard to debug. In order to sidestep any drama, I made a little script that lets you switch all the wires in a document between "Hidden" and "Faint." It will leave all wires set to default alone. 

Download it here: WireDisplayToggle.gh

Views: 3281

Comment

You need to be a member of Grasshopper to add comments!

Join Grasshopper

Comment by Pablo on January 19, 2015 at 4:11pm

i think the wires should always accommodate themselves for simple reading, similar to puredata 

Comment by Rémy Maurcot on December 29, 2014 at 8:40am

Thanks.

Comment by Andrew Heumann on December 29, 2014 at 7:51am
Yes, it's possible. But it sounds like a terrible idea to me so I'm going to be difficult and leave it up to you to modify the script :)
Comment by Rémy Maurcot on December 29, 2014 at 5:38am

Hi Andrew,

it's possible to add a function for convert defaut wire on faintwire ?

Thanks

Comment by Thibault Schwartz on December 27, 2014 at 12:00pm

When used:

Comment by Thibault Schwartz on December 27, 2014 at 11:58am

Well, hidden wires are a pain in the ***, except if you properly use "proxy" parameters to cleanly decompose your definition into small, intelligible functions (that eventually can become clusters or custom components), with proper naming, typing etc.

I am using this method for several years now and this is also the one I teach, and I think that it is (to my knowledge of course) the most readable and robust solution to use GH for both small and big projects. In fact, this way of using these hidden wires + local parameters is a straight translation of what we do in text-based programming when we specify arguments (the hidden wire can be considered as a pointer). I also use also a simple color code to simplify the visual rendering in GH: color=input, black=output, white=process. And when a process is only for display, it's grey. When it's a cluster, I mark it as a blue element, which means "waiting to be compiled" ;).

Comment by Andrew Heumann on December 24, 2014 at 1:30pm

couldn't agree more!

Comment by David Rutten on December 24, 2014 at 12:46pm

I'm squarely in the 'hate hidden wires' camp myself. They're a terrible solution to the spaghetti problem.

About

Translate

Search

Photos

  • Add Photos
  • View All

© 2018   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service