Node code editor

Description of the main features in the node editor

To open the node editor, in the node details page click on the top-right side button Open the Node, the node editor page will open. Initially, default code will be existing, and you can override it to the code for your task.

  • Any node must follow nodes formats, which have these classes:

    • Inputs class: input of that node

    • Outputs class: output of that node

    • Node class: define objects of inputs and outputs and execute the required operations on the inputs to get the outputs.

  • The connection between nodes will be between these inputs and outputs as will be illustrated later.

  • Any node has in the left-side panel a container to upload/create any file/folder required for the node code.

  • You must click on Save button or CTRL+S to save your updates.

  • To compile the code, click on Compile button.

Install additional libraries offers wide range of the main libraries for machine and deep learning models, but if your node needs a library not installed, then you can easily install them by creating a new file with name packages.txt and add to it the libraries names; each library in a line with the version you want or the default version as follows:

Node preview and Run a node test:

From the greet features offers is the ability to preview the interactive inputs of the nodes such as text box, dropdown list, date calendar, and other items as will be illustrated in details in the annotations section. Then can run the node with the user inputs to check the node works as required.

As a simple example, this node calculate the sum of x and y:

The result will be shown in the output tab:

This feature is important for developers to make sure of the node functionality and discover if there is any logical error in the code gradually before connect all the nodes in the app.

Note: to preview the node inputs and run a test, you must firstly compile your node without any error.

Add contributors

You can invite any user in by email to contribute in the node based on the permissions you give as shown below:

You can give multiple access to the contributor. To add a contributor, click on Add contributors in the right-top side of the code editor.

Fork node

You can fork (copy) a node you created or a community node so you can easily create a copy and edit nodes based on your needs by clicking on Fork in the right-top side of the code editor.

Clone node

If you are used to code using git and prefer to edit files from there, then offer this option by click on Clone in the right-top side of the code editor, as each node created in has a repository in Github.

Any commit on the files in Github will be reflected directly on the node code editor and vice versa.

Sharing options

As mentioned previously, you can determine the node privacy option when create the node if it will be a private or a community nodes:

  • private: only the owner user can open it, edit it, and use it in applications.

  • community: other users can open the node and fork it to use it in their apps.

Here in the node code editor, you can change your choice from the sharing settings in the left-bottom side of the code editor:

Node deployment

This is the build version (development version) and you can use it in your applications. But to share the node with community without able to fork (copy) it, click on Deploy, determine the version and choose if the community can use it with the ability to inspect the code or without, as shown in the following figure:

The deployed versions will appear in the nodes' search menu in the application work-space.

If you want to create a new version of the node, you must open the code of the main build (development version).

So the difference between sharing node as a community and deploy a public version of the node as follows:

In community node: other users can show your node code, can't edit it, and can fork it to use the forked version in their apps.

In the private node: only the owner user can show, edit, and use it in the apps, and if want to share with others, there are different options:

  • If the owner wants to make other users able to use the nodes in their apps without able to show it's code, then choose option Deploy and check public option only.

  • If the owner wants to make other users able to use the nodes in their apps and able to show it's code, then choose option Deploy and check both public and inspectable options.

In all private options, other users can not fork the node.