Skip to content
Merged

V2.1 #48

Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion __init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"name": "Node to Python",
"description": "Convert Blender node groups to a Python add-on!",
"author": "Brendan Parmer",
"version": (2, 0, 1),
"version": (2, 1, 0),
"blender": (3, 0, 0),
"location": "Node",
"category": "Node",
Expand Down
21 changes: 13 additions & 8 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,21 +7,19 @@
## About
A Blender add-on to create add-ons! This add-on will take your Geometry Nodes or Materials and convert them into legible Python add-ons!

It automatically handles node layout, default values, subgroups, naming, colors, and more!
Node To Python automatically handles node layout, default values, subgroups, naming, colors, and more!

I think Blender's node-based editors are powerful, yet accessible tools, and I wanted to make scripting them easier for add-on creators. Combining Python with node based setups allows you to do things that would otherwise be tedious or impossible, such as
Blender's node-based editors are powerful, yet accessible tools, and I wanted to make scripting them easier for add-on creators. Combining Python with node based setups allows you to do things that would otherwise be tedious or impossible, such as
* `for` loops
* creating different node trees for different versions or settings
* interfacing with other parts of the software or properties of an object

NodeToPython recreates the node networks for you, so you can focus on the good stuff.

## Supported Versions
NodeToPython v2.0 is compatible with Blender 3.0 - 3.4 on Windows, macOS, and Linux. I generally try to update the addon to handle new nodes around the beta release of each update.
NodeToPython v2.1 is compatible with Blender 3.0 - 3.6 on Windows, macOS, and Linux. I generally try to update the add-on to handle new nodes around the beta release of each update.

## Installation
1. Download the `NodeToPython.zip` file from the [latest release](https://github.com/BrendanParmer/NodeToPython/releases)
* If you download other options, you'll need to rename the zip and the first folder to "NodeToPython" so Blender can properly import the module
* If you clone the repository or download other options, you'll need to rename the zip and the first folder to "NodeToPython" so Blender can properly import the add-on
2. In Blender, navigate to `Edit > Preferences > Add-ons`
3. Click Install, and find where you downloaded the zip file. Then hit the `Install Add-on` button, and you're done!

Expand All @@ -37,19 +35,26 @@ Just select the one you want, and soon a zip file will be created in an `addons`
From here, you can install it like a regular add-on.

## Future
### v2.2
* A "copy" mode, where just the functionality to build the node group is just copied to the clipbaord
* Choose the location where to save the add-on

### v2.3
* Expansion to Compositing nodes
* Add all referenced assets to the Asset Library for use outside of the original blend file

### Later
* Auto-set handle movies and image sequences
* Automatically format code to be PEP8 compliant
* Automatically detect the minimum version of Blender needed to run the add-on

## Potential Issues
* As of version 2.0.1, the add-on will not set default values for
* As of version 2.1, the add-on will not set default values for
* Scripts
* IES files
* Filepaths
* UV maps
* This add-on doesn't currently set default values in Geometry Nodes modifiers, just the node groups themselves
* Currently when setting default values for the following, the add-on must be run in the same blend file as the node group was created in to set the default, otherwise it will just set it to `None`:
* Materials
* Objects
Expand All @@ -67,4 +72,4 @@ When submitting an issue, please include
* A short description of what you were trying to accomplish, or steps to reproduce the issue.
* Sample blend files are more than welcome!

Suggestions for how to improve the add-on are more than welcome!
Got suggestions? Create an issue, happy to hear what features people want.
Loading