compas-dev / compas-actions.ghpython_components Goto Github PK

Hi @gonzalocasas
I am trying to use this AMAZING feature but there is something that doesn't work in my workflow.

The action seems to be completed with positive result but I am not sure if everythings is correct.
Can you please assist?
Can you maybe create a quick .gif to show me?

I can not find a way to find the file on github at the end of the action

Thanks,
Marco

I created a definition for a component in the procedural mode ("isAdvancedMode": false).

What's wrong?
In the built component all "description" values are ignored and a default text is displayed instead, except for the very first input parameter.

Example/Demo
code.py contains only:
c = a+b

metadata.json:

{
    "name": "TestSum",
    "nickname": "TestSum",
    "category": "Componentizer",
    "subcategory": "Test",
    "description": "Tests if the componentizer is working in procedural mode.",
    "exposure": 4,
    "ghpython": {
        "isAdvancedMode": false,
        "iconDisplay": 0,
        "inputParameters": [
            {
                "name": "a",
                "description": "First number",
                "typeHintID": "float",
                "scriptParamAccess": 0
            },
            {
                "name": "b",
                "description": "Second number",
                "typeHintID": "float",
                "scriptParamAccess": 0
            }

        ],
        "outputParameters": [
            {
                "name": "c",
                "description": "Sum of a and b."
            }
        ]
    }
}

Preview:
Correct:

Wrong/default:

Feature Request:

It some situations it would be helpful to set, for example, a "Flatten" action on the input params as default, so that certain assumptions about the structure of the input can be imposed.
Would it be possible to add a corresponding flag to the metadata?

Hello!

Big fan of the action and loved the brilliant way to generate .ghuser components from python and allow easy ci. Thanks!

I was wondering if there were any plans to update this to Python3 with the new Script component of Grasshopper.

I quickly got a look at the python and use pythonnet to replace some functionnalities of IronPython (e.g. the clr module's clr.AddReference(gh_io)), and it outputs the .ghuser files but they are still marked as "old" if imported into the grasshopper canvas.

Would you have any clue how to modify the componentize.py file to port this properly to the new CPython Script component? Would love to give it a go and open a PR if of any utility.

Cheers!

Hi,

I think, there is no type for GeometryBase from the default list below.
How can I add a geometry-base type to this list?

Thank you :)

Hello :)

I am running the componentize from my machine and it looks like that GH_IO needs to be inside the folder ./lib
I would suggest to look for the GH_IO in the same folder where the .py is runned.