Since I haven't personally used Unity in many years, and nobody came forward to fix it themselves, the project is currently in a broken state. Namely UndoPro, a dependency also developed by me, needs minor updates due to internal changes by Unity. I do not have the time anymore to dedicate to the project myself, and so unless someone comes forth to at least maintain it, I would recommend to look for another solution. This should be easy, since the creation of the project a lot of alternatives (and even an official solution) have been developed.
WebGL Demo -
Forum Thread -
Documentation
- Extensible interface
- Extensive controls including zooming/panning
- Runtime-fetching of custom nodes, connections, canvas, traversal routines and controls
- Full Save- and cache system (Scene, Asset and XML)
- Runtime support (see WebGL demo)
- Full Undo support using UndoPro (editor only)
The LTS distribution version is just the base framework, intended to be installed as a package using the Unity Package Manager and used by different tools simultaneously, without any framework modifications by individual tools. With the options the framework gives, this still allows custom windows for each tool with custom look and behaviour. This is recommended for smaller tools that are released as a UPM package or through github with installation instructions. However it prevents you from using the Node Editor at runtime (see RTNodeEditor).
For detailed installation instructions see the latest LTS release.
- Install Undo Pro:
UPM/Add from git (latest): https://github.com/Seneral/UndoPro.git#release-pkg - Install Node Editor Framework:
UPM/Add from git (latest): https://github.com/Seneral/Node_Editor_Framework.git#release-pkg
This is intended to be used in tools aiming to modify the framework core and embed the framework in their distribution. This requires them to modify the namespace and make sure it does not conflict with other tools. This is the version to choose for Asset Store releases, as they cannot specify a UPM package as dependency.
For the development version, take the latest release from develop.
Examples can be found in the Examples subfolder or packaged in the latest LTS release.
In addition to those there are several other examples that are more involved, found as branches in this repo.
- The Texture Composer, as seen in the title screen, is a very simple setup of a few texture nodes built upon the default calculation canvas in the framework. Start here to get a basic idea on how to create simple extensions of the framework with custom functionality.
- A great, but complex example is the Dialogue System, developed and maintained by ChicK00o and atrblizzard. Making excellent use of the framework's modularity to extend the frameworks capability and behaviour to get a basic dialogue system, including the editing and runtime execution (with an example scene), up and running. Check it out if you want to get an idea of a bigger setup expanding on the Node Editor Framework with custom rules.
- Another set of nodes is the 'Expression Node' example. These are a bit different as they use reflection to inject any type of variable into the framework, to convert or execute code on. It's main purpose is to show complex modifications of the Node Knobs and general extended use of the framework.
- A small example of extending the editor controls can be seen in the included Node Group. It contains custom controls to handle without modifying any framework code.
If you want to contribute to this framework or have improved this framework internally to suit your needs better, please consider creating a Pull Request with your changes when they could help the framework become better. The issues section serves as a feature discussion forum and I encourage you to check it out to get an idea of the future plans for the framework. You can also PM the main developer Seneral directly if you wish so.
The project was started as a part of the thread "Simple Node Editor" in may 2015 by Seneral. Big thanks to Baste Nesse Buanes who helped to set up this repository initially, without his help the framework could not have expanded to the point where it is now! Also, thanks to Vexe, who has greatly helped with the reflection related stuff which is used for the zooming functionality of the editor. And of course thanks to everyone contributing or simply motivating the developers by sharing their work with the Node Editor Framework! You can find the full list of contributors here.
The license used is the MIT License - see license.md