-
Cause an FBP protocol error to happen. In this case through an unparseable data as an IIP
```
FBP MICROFLO RECV: { protocol: 'graph',
command: 'removeinitial',
payload:
{ src: { data: …
-
All these scenarios are assuming that the Flowhub (Chrome) app is installed, and that the devices do not come bundled with MicroFlo/NoFlo out-of-the-box. It also does not yet consider when a device is…
-
For noflo-nodejs, one currently has to use npm on commandline.
For noflo-browser, one has to change the build of noflo-ui itself to update the runtime. #154
For MicroFlo, change microflo build itself…
-
It is important that people can communicate with MicroFlo programs from other things that NoFlo/JS. Adding a Python library would demonstrate that this is possible, and help people implement it for ot…
-
On my machine `microflo component` and `microflo generate` takes a couple of seconds to kick in, and `microflo runtime` takes around 10 seconds.
Probably due to a huge amount of Node.js modules tha…
-
To build something which uses microflo, one needs to have the right compiler flags. Currently there is some magic/hardcoding in the microflo `Makefile` for this, which is both quite inconvenient and n…
-
For MicroFlo, this would persist the graph to EEPROM (issue jonnor/microflo#7) - so that the microcontroller will always run that program when it starts.
For NoFlo (Node.js / Browser) I'd expect it to…
-
We rely on a standard format for runtime information in the client (typically serialized as JSON)
```
label: "MicroFlo Simulator"
description: "The first component in the world"
type: "microflo"
prot…
-
Currently we use a hand-rolled .JSON format to describe the message (types) that can be sent using the MicroFlo FBCS protocol between host and device.
https://github.com/jonnor/microflo/blob/master/mi…
-
Currently a `MicroFlo::Network` is hardcoded to use `MicroFlo::createComponent()` to instantiate components. This imposes some pretty strict restrictions on where the code for a component comes from a…