Requests: Improved usage of groups for mananging large definitions

Hi David,

I've been using grasshopper in a context that uses series of large scripts to create fabrication drawings. These scripts pretty much use this work flow: (a) Take a bunch of geometry > (b) Take it apart, trim holes, connections, and other stuff needed for the fabrication > (c) Make 2d drawings out of them. (d) exporting them

I've got a few findings that might be useful in that context:

1. When using large amount of components, the show selected only is pretty much the weapon of choice to debug. In this context it would be useful if the Custom Preview components (also the custom vector preview component)  would not turn green when selected in "Draw Only Selected Geometry" mode, since it turns them pretty much useless in this mode.

2a. A second step up to the same problem would be if turning objects on/off (enable/disable) (preview/disable preview) could be done at the group level. (Perhaps the ZUI-kung fu you've introduced could be the way to go?). This would make creating scripts that can have different stages that do not always have to be enabled a bit easier to manage.

2b. This would of course even be better if the groupwise-enable/disable operations are overrides. (in the sense that a component is only enabled when the group and the component are enabled).

3. Colours. Would it be possible to add a small pallette to the GH colour picker? Right now if we for example pick a convention "Let's make all the functionality that's for debugging yellow, all operating code that should not require messing about with green, and the parts that require human interaction Red", is a bit cumbersome, because picking the same yellow will require me to remember the colour values to get the same colour (The pipet tool will also give different colours)

4. Scribble: Can I please easily align text to 0,90,180 or 270 degrees rotation? :)