Difference between python script and python in grasshopper

Hello, this question has confused me for a while.

What is the main difference between the python script in Rhino and the component in grasshopper?

For now, I know:

1. script one is more efficient in debugging, etc.

2. the grasshopper one allow interaction with the other component in GH, etc.

I mainly use python to do things that GH cannot or inefficient, like loop, etc.

My really concern is whether there is anything that the script can do while the GH one cannot, and if there is huge efficiency difference of different one.

Or any other thing I missed.

Replies to This Discussion

Permalink Reply by Giulio Piacentino on April 4, 2014 at 3:02am

Hi Arthur

the main difference is, of course:

- a script in the _EditPythonScript component is a .py file and runs on the Rhino document
- the GhPython component runs in Grasshopper and is stored in the .gh file

I would not focus on any difference in efficiency (today maybe the Grasshopper one, because it is not showing preview and does not have undo's, can at time be slightly faster with rhinoscriptsyntax) and does not (at present) have debugging. These latter two are properties that can change with newer updates.

There is also another property that I can think of, where things are slightly different. Here it is a more "structural" change: there is no "time" in Grasshopper to really make use of picking object parts, so that, while technically possible, is discouraged, and the interface to pick things is not the usual command line but other Grasshopper input. Subobject picking is therefore, as usual in Grasshopper, more difficult.

Does it make sense?

Giulio
--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Permalink Reply by X.Arthur.Ma on April 4, 2014 at 8:21am

The GH one can also load .py file, right? (Though the other component will be lost.)

The picking object thing... yes it is. But what I find interesting is if there is relatively more input than usual, and once you input something wrong during the process, you have to start again the script. While for the GH one, you can simply connect the line into another input component.

Thus, I wouldn't read it as a negative aspect.

Permalink Reply by Giulio Piacentino on April 4, 2014 at 8:40am

"Load" is a bit ambiguous as a term. It can import, or interpret them. But not edit (at present) .py files.

On the lower part, I don't think there is anything bad in general. :) It's a bit like comparing two similar tools, for similar but anyways different purposes. Like a fork and spoon maybe?

Giulio

--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Permalink Reply by X.Arthur.Ma on April 4, 2014 at 10:34am

OK, I understand.

for the "import", I think we can import and then export so that it act as "edit"?

RSS