algorithmic modeling for Rhino
We don't like to make promises, as we're very bad at estimating. Basically Grasshopper releases follow one of two patterns. There are slow releases that roll minor version number (0.6, 0.7, 0.8 etc.). These sometimes take weeks or even months. One of these is usually followed by a flurry of revisions (0.8.0001, 0.8.0002, 08.0003) where reported bugs are fixed.
Current version 0.8.0066 and was released on January 22, 2012 (yes, a long time ago).
The next version will be 0.9.0001 and will hopefully be released in late May or Early June. I pasted the release notes below, as they were on May 18th:
The main focus of 0.9+ is to improve cluster GUI and implementation.
Yea, I think they are the only two components that are not so kangaroo specific but are really helpful in many definitions, I often find myself downloading kangaroo on other computers just for those two components, not that I don't also love the rest of kangaroo in general. and as I said before I think main functionality would be desired as
a:removing all the duplicates and keeping one (a sort of duplicate flattening)
b:put duplicates into lists with each other (a sort of duplicate grafting)
So, will this :
"Added Evaluate Mesh component for sampling position, normal and colour at a mesh parameter (Mesh.Analysis panel)."
involve somehow mesh parameterization ? Or it's just something that sounds to me familiar ?
Thanks for posting the list of changes early. When I finally finish going through the whole list the new version will be posted already.
"The main focus of 0.9+ is to improve cluster GUI and implementation."
Does this mean that 0.90001 will have improved clusters or you mean more serious cluster development will begin after the next release?
It means that 0.9.0001 should have better clusters.
please would you consider also returning the edge valence (how many faces are connected to an edge) while returning the edge lines?
I would suggest merging the string compare into the equal function. Just like the add or subtract component, which worked for vectors now. I know vector can be considered math too.
But for beginners, strings compare seems legit to be considered "logic", despite I know it is wrong, I just think an auto-cast might be helpful for them.
Big appreciation to your hard work David, thank you.
I can't fall asleep tonight, more suggestions for you when you have time:
The graph mapper, very useful, but can never be precise to repeat. Could the four grips location be editable inside the double-clicked interface.
Iso curve component: uv input, should be clearer to receive u and v in separated inputs. Point input are confusing since the Z component for the point is disregarded anyway.
MultiDimensional Slider: If the curent value can be set via the double-clicked interface, it would be fantastic. Also if Galapagos could move it too.
Keyword search: Since 0.8.0052, loved the quick slider initiation. Cheers for the negative value fix, wanted it so long. However, I lost the ability to find 3Pt plane, Vector 2pt, Circle 3pt and some of my own user objects, by typing the number to start with. Because the slider is the only option. Can the other recommendation (apart of the slider)also shows in the list, so at least we could pick them?
Alt-click behavior is strange, I thought the norm to Alt-Drag to copy, is first press down Alt, then Drag. However, in GH, you need to start the drag first before pressing the Alt, otherwise doesn't work. I'm too used to the old Alt first gesture.
The offset by point function should be implemented. Right now I'm using the code from Andrew Heumann in this post http://www.grasshopper3d.com/forum/topics/offset-problems?commentId... This is very useful in general, and should be implemented on both offsetting curves and surfaces.
Have you considered a new connection type that is a "bus", not just a wire. Which can handle multiple in and out with only one wire. For example if I'm working with a "set" of input, mixed type, and wiring it to a lot of stuffs. It is a nightmare to manage the "set" now. I will sometimes wire them to a "Generic Data" component, one for each input. Another way I have tried is to place the set of input into 1 branch of a tree, and combine them, later accessing them by the index number inside the path. However, as design changes, often we need to add or subtract parameters, right now, it is quite difficult to manage.
A bus could be a labeled in, labeled out system. Allow quick change to another set of input. I dont know yet, I dont have the picture in mind. But I feel that something is missing.
MultiSave exit dialog should allow SaveAs. Sometimes I ran to that point and I realize I need a SaveAs.
Save State is a pretty cool feature, esp for business, but need a better interface (Think about the layers panel in Rhino). Allow renaming and reordering. Allowing saving panels text, value list. Way of selecting all the inputs of a previously saved state, for generating a new Saved State. (Think about the "Select Objects" in the layer panel. Easier way of selecting which datatype to include, eg: Highlight selected datatypes on canvas indicate which one is included, also to easily spot/modify what is missing or needed. Clicking on canvas to choose what to include. (Same principle on the Stored views)
Nice if Export High Res dialog gives you an idea of the resulting resolutions (px X px) in advance. It is rare that I could find the right zoom setting in the first attempt.
I would be really professional software if the following window could be docked: data viewer, saved status panel, saved views panel, copy paste management (retains a few items of clipboard, since you have developed an internal clipboard now).
Do you have ways of obtaining user statistics for yourself, so you know how users user GH, it will be more helpful for you I guess. I'm curious about them too. For eg, I always use the Clean Tree component with the Clean input = True, however the default is False, I wonder how many people use False verse True.
I hope my suggestions are contributing to the developing of GH to a more professional future, not meant to add more work for you.
Thanks for the hard work again, David. Thank you.
Don't know if this is the place to add requests but hey here's mine..
1. Add an option to the tree branch component for user to output original paths in the same way as tree split works as currently i have to use a replace branch work around alot of the time to match the paths again.
2. Input options on the record component, such as reset and stop start , as the firefly recorder will only rec single numeric values.
3. Any chance of a Collapse Mesh Vertex Component for reducing heavy meshes.
Thanks for all the great work
looking forward to next release and a big thank you for your stunning work.
i have got one little suggestion:
Since you announced that MultiDimensional Sliders can now be part of states, could you also include for "Value List" aka Pulldown Menu?
Would be a great help for a running project.
just found this wish in victor's list.
so: +1 ;-)