It was never really in fashion for Grasshopper 1. Documentation has always sucked, mostly because the framework I wrote for it was cumbersome and inflexible, making it very difficult for someone other than the developer to provide docs.
I agree with you (as does basically everyone I know) that we need to do a lot better, and in fact the documentation system was the first thing we started writing on for GH2. It’s a bit back-burner now since there’s nothing to actually document as such yet, but I imagine as soon as some of the interface stuff becomes mature enough we’ll start again. We got trained linguists and everything on staff now to help out with this.
In the meantime GH1 will remain essentially one giant easter egg.
Yeah that’s clearly a bug, needs to be updated to link to discourse.
Perhaps there could be a more obvious link to this page, like under the “Learn” Dropdown?
I’ve been slowly collecting these Easter Eggs, but more often then not, I discover that @DavidRutten has already mentioned them in answering one question or another on the forum. The use of the “Time” component is pretty nifty.
My favorite (undocumented?) shortcut is in using context menus (RMB over canvas, group, or component) - for any menu selection with a unique first letter, typing that letter will select it. So then turning a wire to “Faint” is <RMB, W, F>. Maybe that solves your second gripe, @osuire?
Yeah, I’m not a big fan of that one.
More often than not, I only need to change the wire display on some of the inputs, and I don’t like dragging this component around to keep it handy.
I organize my components with groups. Any wire going in or out of the group will be faint, and wires inside the group remain standard.
I also tend to separate chunks of definition with panels which I turn black and make into lines.
Between these chunks, I make the wires hidden.
If there was a way to automate this kind of layout, it would save me lots of time.