Feature request

[obucklin]

Howdy!

I was hoping to implement some GH_Component override methods that only work on compiled components. See this image for reference:

This action creates a .ghpy file for the component, which is no longer editable as a python component on the canvas, but allows various overrides. have you guys considered this? Will the new cPython workflow for Rhino8 implement this?

Thanks!

[gonzalocasas]

I think the major downside of .ghpy is that it doesn't work on Mac, or to be precise: it used to be that, we haven't tested if .ghpy + rhino 8 works on mac

[gonzalocasas]

A quick check seems to indicate that this is still not supported on cpython + rhino 8 for mac:

[9and3]

Howdy!

I was hoping to implement some GH_Component override methods that only work on compiled components. See this image for reference:

That would actually be cool. It's quite a pity that the compilation doesn't work on mac.

Still, I wonder if a component using modules, when compiled, would not require the modules to exist locally as .py somewhere. Do you know @gonzalocasas ?

[gonzalocasas]

Howdy! I was hoping to implement some GH_Component override methods that only work on compiled components. See this image for reference:

That would actually be cool. It's quite a pity that the compilation doesn't work on mac.

Still, I wonder if a component using modules, when compiled, would not require the modules to exist locally as .py somewhere. Do you know @gonzalocasas ?

I'm not entirely sure, but I think it would anyway be preferable to have those required modules as a python lib and use the # r: syntax in components to handle installation. Especially now that even the "pip from git" syntax works (i.e. # r: git+https://github.com/something/somerepo.git)

[gonzalocasas]

Should we close this? Because I think it's not actionable on our side