Grasshopper

algorithmic modeling for Rhino

Can anyone tell me the limits of customization of the GUI/Menus/Params, etc. from within a Python component?

I can see from Ladybug/Honeybee how to set certain metadata, tooltips, etc.

Is this all we can do though? Can we not also add menu items, input and output params, or, even better, can we call Window.Forms in a meaningful way to customize new input interfaces such as done with ArcSim and other C# based custom components?

Don't want to waste time trying to figure this out of it's just not possible...

I see no references to these in the discussion so if this is possible I will try and share code as I go along.

Update: I have found making straight Windows.Forms.Form is quite easy.

There is a good tutorial here:

ftp://91.193.236.10/pub/docs/linux-support/programming/Python/Profe...[John%20Paul%20Mueller]%20(2010)/Professional.IronPython.John.Paul.Mueller.2010.pdf

goto chapter 8

I am still wondering if there are some special menus, etc. which Grasshopper implements.

Views: 1112

Replies to This Discussion

I think you will be pretty limited in your ability to change the appearance of a python script component. This is also true for the c# and vb.net scripting components - they are fundamentally different beasts from true compiled components, which inherit from the GH_Component class, allowing them to define their own "attributes" class which dictates how each component is drawn/rendered to the canvas. 

Yeah... I came to this realization slowly after trying a few different things. It seems the only option then would be to compile our own Python component, but with the GUI, params, etc. that we wanted. This could be a good next step for the guys in charge of the Python side of things.

In the meantime, window forms seems worth investigating.

Thanks for the response...

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service