The NoFlo Development Environment is an offline-capable, client-side web application that helps users to build and run flow-based programs built with FBP compatible systems such as NoFlo, imgflo and MicroFlo. The NoFlo Development Environment is available under the MIT license.
This project was made possible by 1205 Kickstarter backers. Check the project ChangeLog for new features and other changes.
Flowhub is a hosted and commercially supported version of the NoFlo Development Environment. It is free to use for open source projects, and for private projects if you do not need Github integration.
If you just want to create applications, we recommend that you use this version instead of building your own from source.
Please read more from http://flowhub.io/documentation/. See also the available support channels.
To be able to work on the NoFlo UI you need a checkout of this repository and a working Node.js installation. Go to the checkout folder and run:
$ npm install
You also need the Grunt build tool:
$ sudo npm install -g grunt-cli
This will provide you with all the needed development dependencies. Now you can build a new version by running:
$ grunt build
You have to run this command as an administrator on Windows.
If you prefer, you can also start a watcher process that will do a rebuild whenever one of the files changes:
$ grunt watch
Serve the UI using a webserver, then open the URL it in a web browser. Example:
$ npm install simple-server
$ ./node_modules/.bin/simple-server . 3005
Where 3005 is the port you want the server to run. Once it is built and the server is running you can access the UI at http://localhost:3005/index.html
In addition to this project, the other repository of interest is the the-graph graph editor widget used for editing flows.
Even though the UI itself is built with NoFlo, it isn't talking directly with that for running and building graphs. Instead, it is utilizing the FBP Network Protocol which enables it to talk to any compatible FBP system.
If you want to integrate the UI with a new environment you need to provide some transport layer (for example, WebSockets) that can talk the protocol, and then implement runtime access for that.