NoFlo

Flow-Based Programming (FBP) is a programming paradigm that defines applications as networks of processes, which exchange data across predefined connections.

While this sounds complex, FBP is very useful in managing dynamic applications, which are quite a lot on the Web these days.

Basically any large AMD and AJAX-based application can reap the rewards of asynchronous flows via NoFlo.

NoFlo is actually written in CoffeeScript and was developed thanks to a daring Kickstarter project.

Getting started with NoFlo is a little bit harder than any other framework, so make sure to check out their documentation first.

What is new in this release:

• Hotfix reverting backwards-incompatible changes in subgraph loading.

What is new in version 0.5.17:

• Hotfix reverting backwards-incompatible changes in subgraph loading.

What is new in version 0.5.13:

• Hotfix reverting backwards-incompatible changes in subgraph loading.

What is new in version 0.5.11:

• Hotfix reverting backwards-incompatible changes in subgraph loading.

What is new in version 0.5.6:

• Custom icon support for subgraphs via the icon key in graph properties.
• Parameter support for WirePattern components, allowing them to have configuration parameters that need to be set only once.

What is new in version 0.5.5:

• Fixed an issue with StreamSender affecting WirePattern components dealing with multiple levels of grouping.
• New CustomizeError helper for passing information with Error objects in NoFlo.

What is new in version 0.5.4:

• The WirePattern helper has a new ordered option for choosing whether the output should be in same order as the incoming packets
• Options group and forwardGroups of WirePattern are made independent, so make sure to use forwardGroups: true if you need this feature together with group: true.
• Added support for multiple outputs and reading/writing substreams as solid objects in WirePattern.
• Added load outport handing in WirePattern to make it a complete replacement for AsyncComponent.
• Added helpers for advanced error handling, see #185.
• Added caching option for OutPorts that makes them re-send their latest value to any newly-added connections, see #151 for example use cases.

What is new in version 0.5.2:

• Fixed a minor packaging issue.

What is new in version 0.4.3:

• Subgraphs now support closing their internal NoFlo network via the shutdown method
• Component Loader is able to load arbitrary graphs outside of the normal package manifest registration via the loadGraph method
• Component Loader of the main NoFlo network is now carried across subgraphs instead of instantiating locally
• Libraries can provide a custom loader for their components by registering a noflo.loader key in the manifest pointing to a CommonJS module
• Exported ports can now contain metadata
• It is possible to create named groups of nodes in a NoFlo graph, which can be useful for visual editors

What is new in version 0.4.2:

• Port errors now contain the name of the NoFlo graph node and the port.

Requirements:

• Node.js 0.6 or higher