Adding Repositories as new Nodes
Adding an existing repository
Heron can add repositories that have the correct folder structure (see below) as symbolic links into its own folder structure and thus allow Heron’s GUI to see code in these repositories as Nodes. This is the principal way of adding new Nodes to Heron’s GUI.
The first step in that process is to create or download a repository designed to be a Heron Node or group of Nodes. Once such a repository is in place on the hard disk somewhere (do not put it in Heron’s folder structure) then do Menu Bar -> Operations -> Add new Operations Folder (as Symbolic Link from Existing Repo). Point Heron to the top folder of the repository and it will add the correct parts of it in Heron’s Operations folder as symbolic links.
In Windows, in order for an app to make symbolic links it needs to have Administrator rights, so to do the above in Windows, Heron must have been started with a Run as administrator (Linux does not require anything like this). If the above is not the case then Heron will give a warning reminding the user to give it elevated privileges. Another error will be generated if the directory Heron is pointed to does not contain a valid Heron Nodes folder structure.
Downloading a repository from inside Heron
Currently this functionality (Menu Bar -> Operations -> Download Operations from the Heron-Repositories page) is not implemented. In the future you will be able to download a repository straight from a repository website and into a new repository on your machine with the symbolic links taken care of.
Creating a valid Heron Nodes repository from scratch
The only requirement for a valid Heron Node repository is its correct folder structure. This is as follows
Here is an example with 4 Nodes in it, a Source called Weird Camera (under Vision), a Transform called Super Motor Controller (under Motion) and two Sinks called Saving CSVs (under Saving) and Some Other Sink Node (under General).
The actual name of the Node as seen on Heron’s GUI is set in the xxx_com.py script. It is good practice to give the folder holding the Node (i.e. the Python scripts) the same name but with underscores instead of spaces. Heron doesn’t mind if the name of the folder is different but it does mind spaces so pretend it is 1980 and make folder names without spaces.
The folder __top__ needs to exist if the Subcategory you are making under the Sources/Transforms/Sinks folder doesn’t already exist in your Heron folder structure. Otherwise it can be skipped. In general it is a good idea to just include it. The ignore.gitignore file is an empty file that gets added to the git repository so that the __top__ folder is also added to the repository.
The file / folder structure inside the Node folder can be anything as long as the xxx_com.py and xxx_worker.py scripts are also present.
The Heron repos organisation on GitHub has plenty of examples of Node repositories.