This shows you the differences between two versions of the page.
labs:explicithistory:home [2015/09/14] |
labs:explicithistory:home [2020/08/14] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Grasshopper Main Page====== | ||
+ | |||
+ | | {{: | ||
+ | | // | ||
+ | |||
+ | ---- | ||
+ | |||
+ | > **Summary: | ||
+ | |||
+ | **Grasshopper now has its own site - www.grasshopper3d.com\\ | ||
+ | Go there for downloads, more info, the Grasshopper forum, etc.** | ||
+ | |||
+ | [[http:// | ||
+ | [[http:// | ||
+ | [[http:// | ||
+ | |||
+ | **It is //highly recommended// | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Installation instructions===== | ||
+ | |||
+ | |||
+ | **The Grasshopper plug-in cannot be loaded over a network. Be sure to put it on a local disk!** | ||
+ | |||
+ | |||
+ | The current versions of Grasshopper are self-installing .exe' | ||
+ | |||
+ | Grasshopper will automatically install in the current Rhino version, (usually V4) but you can load it from another version (like V5) by following the manual plug-in install procedure from within that version and pointing the installer at the existing installation. | ||
+ | |||
+ | Once installed, the command **Grasshopper** will load the plug-in. | ||
+ | |||
+ | Grasshopper is bit-independent, | ||
+ | |||
+ | ===== Grasshopper pages===== | ||
+ | |||
+ | * [[labs: | ||
+ | * [[labs: | ||
+ | * [[labs: | ||
+ | * [[labs: | ||
+ | * [[labs: | ||
+ | * [[labs: | ||
+ | * [[labs: | ||
+ | * [[labs: | ||
+ | * [[http:// | ||
+ | |||
+ | |||
+ | | {{: | ||
+ | |||
+ | ===== Why Grasshopper? | ||
+ | |||
+ | Rhino 4 came with a basic history feature built-in, which is a non-intrusive layer around the workflow that allows automatic updates of certain modeling steps. The current implementation of history in Rhino 4 is implicit, that is, it is recorded as you go. This means there is no extra overhead required at model-time. This is exactly the sort of thing we like to see in Rhino: more features, no additional limitations. Still, implicit history cannot do some things which are possible with explicitly defined history. | ||
+ | |||
+ | First, the history tree is hidden from the user. The behavior of the different history stages cannot be adjusted. For example, there is only one chance to set the properties of a history based Loft. Once the surface exists, the only way to change the Loft settings is to recreate the surface. This breaks all downstream history records and is thus potentially an extremely expensive limitation. It is also impossible to add or replace curves from a history Loft. | ||
+ | |||
+ | Grasshopper tackles these issues by letting the user construct their own history tree or better // | ||
+ | |||
+ | There are limitations that come with the process. It is no longer possible to record the history tree transparently; | ||
+ | |||
+ | |||
+ | But, the advantages speak for themselves: | ||
+ | |||
+ | - The tree is exposed, thus can in whole or in part be reused throughout different models. | ||
+ | - The components on the tree are exposed, so can be replaced or adjusted. | ||
+ | - The operations are not tied to geometry in the model. It is possible to make a tree which only deals with mathematics. | ||
+ | - Mathematical and logical relationships can be constructed. | ||
+ | - External (to Rhino) sources can be used to retrieve and store data. | ||
+ | |||
+ | This makes Grasshopper a marvelous tool to be explored by anyone interested in generative modeling of complex objects or interested in more control over the characteristics of even simple objects. | ||
+ | |||
+ | Grasshopper is a Work-in-Progress. | ||
+ | |||
+ | |||