We need your help! 🔥
Please consider disabling your ad-blocker to support this website! 🔑
We are a free, community-supported website! 🥰
We only display small unobtrusive ads which help us stay online! 💯
Thank you in advance! ❤️
We are a free, community-supported website! 🥰
We only display small unobtrusive ads which help us stay online! 💯
Thank you in advance! ❤️
Export Ladybug
Code Developers of Ladybug and Honeybee can use this component to export Ladybug/Honeybee user objects and source code that they create to the Github folder on their computer.
This eases and automates the steps before commiting new components to the Github.
This component was written thanks to Giulio Piacentino a really helpful example.
Inputs
| Name | ID | Description | Type |
|---|---|---|---|
| Components | _components | Any output from a new Ladybug (or Honeybee) component that you wish to export. Right now, only one component can be connected at a time but you can input a "*" (without quotation marks) to search all changed Ladybug components on a grasshopper canvas. | Goo |
| Target Folder | _targetFolder | A file path on your system which you would like to export the user object and source code to. For most code developers, this file path will lead to their Github folder for Ladybug (or Honeybee), which is usually installed in "My Documents" by default. Exported source code will be saved at .\src and exported userObjects will be saved at .\userObjects in this _targetFolder. | Goo |
| Export | _export | Set to "True" to export Ladybug (or Honeybee) components to the _targerFolder. | Goo |
Outputs
| Name | ID | Description | Type |
|---|---|---|---|
| Out | readMe! | ... | String |
Site design © Robin Rodricks.
Site co-created by Andrew Heumann.
Ladybug and associated data © 2024 Ladybug Tools.
Rhinoceros and Grasshopper are registered trademarks of Robert McNeel & Associates.
Hosted by GitHub