algorithmic modeling for Rhino
Hi Mohamed,
I think it's confusing to speak of 'scripting' here. In RhinoScript, you use the "Rhino." prefix to indicate a certain function is defined in the RhinoScript plugin, not the VBScript platform.
In VB.NET, "Rhino" and "Grasshopper" are namespaces. In this case they are both top-level namespaces that coincide with individual assemblies (i.e. separate dll files). The "Rhino" namespace contains all of the classes and types and functions from the RhinoCommon SDK, the "Grasshopper" namespace contains all the classes and types and functions from the Grasshopper SDK.
So, yes, in a way 'Grasshopper has its own scripting syntax', but that is an incorrect way of stating it. In fact, in a very real sense, Grasshopper is the Grasshopper namespace.
--
David Rutten
david@mcneel.com
Turku, Finland
thanks David,
i have few questions about grasshopper namespace
is there manuals for it
is it really useful to start using it rather than other syntaxes like rhino one, i mean, what is special about it? is it enough to stop using rhinoscript ?
is it importable to Python for rhino ?
kind regards,
Mohamed
Hi Mohamed,
you can download the help for the Grasshopper SDK via the Grasshopper Help menu (Download SDK Help).
Grasshopper is not like Rhino, the question "is it really useful to start using it rather than other syntaxes like rhino one" does not make sense. The Grasshopper SDK allows you to write code that works with and inside Grasshopper. You cannot do this using only the Rhino SDK.
What are you trying to accomplish? Do you want to write custom components? If yes, then you'll absolutely need the Grasshopper SDK and probably also the Rhino SDK.
--
David Rutten
david@mcneel.com
Turku, Finland
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by