NOFLO | FLOW-BASED PROGRAMMING FOR JAVASCRIPTEXAMPLESDOCUMENTATIONSUPPORT CHANNELS NoFlo is a JavaScript implementation of Flow-Based Programming (FBP). Separating the control flow of software from the actual software logic. Helping you organize large applications easier than traditional OOP paradigms, especially when importing and modifying large data
sets.
GETTING STARTED WITH NOFLO If this doesn’t work, read the Node.js installation instructions for your operating system.. Project folder. To create a new project, you should create a new folder in the file system. This folder will contain all the files specific to your project, including dependency declarations, unit
EXAMPLES | NOFLO
Simple example of building a database-backed REST API with NoFlo and noflo-xpress. Demonstrates using middlewares, and integrating request handling with regular NoFlo components. Open in Flowhub. Related Resources. Source code. Video presentation. NOFLO API | NOFLO
Component Loader. The ComponentLoader is responsible for finding and loading NoFlo components. Component Loader uses fbp-manifest to find components and graphs by traversing the NPM dependency tree from a given root directory on the file system. EMBEDDING | NOFLO
Embedding. It has always been easy to wrap existing JavaScript code into NoFlo graphs — just write a component that exposes its functionality via some ports. Going the other way and exposing a NoFlo graph to an existing JavaScript codebase can be accomplished easily using the noflo.asCallback API. This can also be useful for utilizing NoFlo
PUBLISHING MODULES
The possible values for the @runtime annotations include:. noflo-browser for browser-based components; noflo-nodejs for Node.js components; noflo-gnome for GNOME desktop components; microflo for microcontroller components; Aliasing components. If you want to provide the same component interface on multiple platforms, but need different implementations for each, you can use NEED HELP WITH NOFLO? Need help with NoFlo? NoFlo is a Flow-Based Programming environment built together by NoFlo team and a number of open source contributors. Tweets by @noflo.
KICKSTARTER BACKERS
Thank You! Together we funded the NoFlo Development Environment — Flowhub — on Kickstarter. GRAPHS | NOFLO
TUTORIAL: DATA TRANSFORMATION NOFLO | FLOW-BASED PROGRAMMING FOR JAVASCRIPTEXAMPLESDOCUMENTATIONSUPPORT CHANNELS NoFlo is a JavaScript implementation of Flow-Based Programming (FBP). Separating the control flow of software from the actual software logic. Helping you organize large applications easier than traditional OOP paradigms, especially when importing and modifying large data sets.
GETTING STARTED WITH NOFLO If this doesn’t work, read the Node.js installation instructions for your operating system.. Project folder. To create a new project, you should create a new folder in the file system. This folder will contain all the files specific to your project, including dependency declarations, unit
EXAMPLES | NOFLO
Simple example of building a database-backed REST API with NoFlo and noflo-xpress. Demonstrates using middlewares, and integrating request handling with regular NoFlo components. Open in Flowhub. Related Resources. Source code. Video presentation. NOFLO API | NOFLO
Component Loader. The ComponentLoader is responsible for finding and loading NoFlo components. Component Loader uses fbp-manifest to find components and graphs by traversing the NPM dependency tree from a given root directory on the file system. EMBEDDING | NOFLO
Embedding. It has always been easy to wrap existing JavaScript code into NoFlo graphs — just write a component that exposes its functionality via some ports. Going the other way and exposing a NoFlo graph to an existing JavaScript codebase can be accomplished easily using the noflo.asCallback API. This can also be useful for utilizing NoFlo
PUBLISHING MODULES
The possible values for the @runtime annotations include:. noflo-browser for browser-based components; noflo-nodejs for Node.js components; noflo-gnome for GNOME desktop components; microflo for microcontroller components; Aliasing components. If you want to provide the same component interface on multiple platforms, but need different implementations for each, you can use NEED HELP WITH NOFLO? Need help with NoFlo? NoFlo is a Flow-Based Programming environment built together by NoFlo team and a number of open source contributors. Tweets by @noflo.
KICKSTARTER BACKERS
Thank You! Together we funded the NoFlo Development Environment — Flowhub — on Kickstarter. GRAPHS | NOFLO
TUTORIAL: DATA TRANSFORMATION COMPONENTS | NOFLO
By default, NoFlo discovers and loads components from the components/ folder of your project, as well as the components/ folders of any of your NPM dependencies. Components placed in this folder get named based on the filename, so components/DoSomething.js becomes available as component DoSomething. To prevent name clashes, you can also use the
TESTING | NOFLO
Testing. Testing with fbp-spec. Running fbp-spec; Writing fbp-spec tests; Testing with Mocha; Testing with fbp-spec. fbp-spec is a test runner designed for testing any flow-based graphs or components. RELATED TOOLS
There is an ecosystem of tools around NoFlo and the fbp protocol that make it more powerful. Here are some of them: Flowhub – browser-based visual programming IDE for NoFlo and other flow-based systems. noflo-nodejs – command-line interface for running NoFlo programs on Node.js. noflo-browser-app – template for building NoFlo programs for
NOFLO DEVELOPMENT ENVIRONMENT V0.29.1 Flow-Based Programming Environment. Projects 0 On device; New project Create; Runtimes 1 / 1. New runtime HELPERS API
NoFlo WirePattern helper. Note: WirePattern is no longer the recommended way to build NoFlo components. Please use Process API instead.. WirePattern makes your component collect data from several inports and activates a handler proc only when a tuple from all of these ports is complete. The signature of handler function is: IP API | NOFLO
Creates as new IP object Valid types: ‘data’, ‘openBracket’, ‘closeBracket’ @param {string} type * @param {any} data * @param {Object
