algorithmic modeling for Rhino
(Edit. David sez: Please append your (well explained) ideas/suggestions/wishes. I don't care much for what you want, I care why you want it.)
Perhaps this topic has been covered recently, but I don't see any active threads. We're looking for a plugin project and I'd like to get some feedback from the power users before choosing something.
What is missing from grasshopper?
What would you like to connect to that you can't already connect to?
What kind of bottlenecks do you run into?
What secret wish do you have for Grasshopper that doesn't even seem possible?
What project have you been meaning to undertake but haven't had/won't have the time?
Just trying to brainstorm a few ideas here. There are so many great and useful plugins out there, it's hard to discover the gaps anymore.
Looking forward to your thoughts!
My only suggestion
What about a good help system. With graphical explanations and some link to tutorials.
So I was just trying to use the solid and mesh intersection components and I have to say they are the worst so far in GH. So many times it comes up with errors. It says "Boolean intersection set is empty" but displays some intersected geometry. Sometimes it just fails for no reason at all. Sometimes simpler things make it fail more than more detailed ones.
All in all a very frustrating few hours trying to use them. David, we have come to know better than that!
ps: if anyone knows a plugin that can do solid or mesh booleans in GH properly, please let me know.
- Wire shouldn't have a gradient colour effect applied to it when selected, as this makes it get lost when I have to search through a nest of crisscrossing wires all connecting in roughly spot of the canvas. Usually i have to pull the component out to a strange angle so i can more easily track the wire. (This is particularly a pain when the components are within a group).
- Assign wire colours, transparency, lineweights, other settings, etc.
Rhino Commands ported to Grasshopper:
- FlowAlongSrf rhino command to be built as a Grasshopper component. Would enable design methodology of drawing facade design in unrolled elevation and then "wrapping" it around façade, delaying the creation of 3d geometry until the last necessary moment
- Build the "Unroll Srf, Create UV Crv, Apply Crv" Rhino workflow as grasshopper commands to avoid the need to custom build this process within grasshopper. This method is used particularly when creating spiral staircases with a landing half way up it and the design task is to create a simple, elegant accompanying balustrades that is able to mediate between the slopes and the flat area. Much easier to design in 2D and then wrap around the shape.
I understand that there are ways to achieve these results in Grasshopper already, but they are cumbersome, so considering the rhino commands exist, hoping they can be reinterpreted.
I also vaguely recall that there was move to ensure that Grasshopper was 64-bit, and that each of the commands within grasshopper were being rebuilt to these new specs to utilize available processing power.
Hoping this is still the case.
David, you give an opportunity to the transparent canvas?
Most likely no. One thing I'm interested in in getting GH to run in a viewport rather than a separate window, but no more.
What happens with the menu bar/components tabs and so on when GH is docked as a viewport ?
(I would prefer it to disappear, so there is only canvas).
A new pain point that could be solved more or less easily (depends on how deeply the wishes are satisfied :P):
When you are coding a custom component (using python, c#...) it's very annoying when you have lot of inputs/outputs and you cannot visually differentiate them in clear blocks/groups (for instance numeric values, geometry, etc).
So I propose to create graphic separators in coding components. It could be done creating not usually legal inputs-outputs names as "-", "_", etc. This could be improved even more letting the user name those input/output groups, changing the background colour behind them, etc...
This could be integrated with ZUI so in smaller zoom levels you will only display perhaps different colours/separators, and if you zoom in the names will appear...
What do you think about it?
I have been thinking about separators, but every time I try and come up with a solution I end up thinking that it's a mistake to have many inputs/outputs to begin with. If a component requires 6 numeric and 4 geometric values to run, there should be other components that aggregate these values (like the Loft component does).
So the 'final' (C#) component would only have two inputs, and there'd be two other components which collect some values each and group them into a single structure.
The latter is of course possible, but requires a lot of coding at the moment. I'm thinking the most useful thing to do is to make it possible to very easily add data types that are just collections of other data types.
The scope of a variable in GH seems to be defined explicitly by the wires carrying a variable to other components. Is there currently a way to declare a variable as being accessible in any component on the canvas by just typing its name?
I don't think variables have names in GH to begin with (correct me if I'm wrong), but in the design process, most variables are not humanly considered 'important enough' to have names, however there are always a few variables that need names, and are intuitively given names by designers because they become part of the language of the project they are working on.
David, have you considered addressing this in GH2?
I've started addressing it. There will be a way to specify certain values using global names (I haven't decided on a naming rule yet) which will make them accessible to all other parameters in the same document and all expressions in the same and all nested documents.
So you can have a slider which is called @width (let's assume for the time being everything with a @ prefix becomes a global variable, which I don't particularly like) and then width becomes available in all expressions (even expressions inside input parameters).
I've made sure that expressions in GH2 can handle remote variable names (or rather, I've made sure that code which runs an expression can resolve variable names)*.
There are several problems with this approach still:
Major benefit of course is that it will allow people to drastically cut down on wires, which is what ultimately chokes a large file. It's not a large amount of components that make a file hard to read, it's having too many wires. Unfortunately global variables will also make it possible to create very hard to read files.
Yes I'm trying very hard to get this to work in GH2. Numerous problems (both logically and user-interface wise) remain unsolved.
* I've also rewritten expressions to allow for multi-line C#/VB code (python will probably follow suit some day), so they'll be a lot more powerful and a lot faster.
Can't we just simplify that by having a list of global variables for the document ? Like an additional canvas widget visible with some shortcut ?