Henri Bergius

@automata that might be interesting for space-saving! Original plan looked like this: 

We can also utilize the `source` and `getsource` methods of the FBP API here, and show a source code card for the component, or a graph preview for subgraph

At least for now you can delete the local graph and it can be pulled in on the next sync. Similarly, you can pull over it if there are newer...

Idea: specify "breakpoints" in edge metadata, then make runtime automatically dump a flowtrace when these are hit

Here is a vim FBP highlighter: https://github.com/ninegrid/vim-fbp In action: 

FBP syntax highlighting rules for the ACE editor: https://github.com/johnrees/visualize/blob/37692009de167ca2b9864ca39d3d0a9ee12da6e5/browser/mode-fbp.js

Potentially useful also: [supervisord example](https://github.com/c-base/c-flo/tree/master/config/supervisord)

@ensonic in the _fluxify_ branch we're already transmitting the loading state to the UI, though not yet visualising it in any way. Spinning that button might indeed be a good...

Two cases where this might be good to use: * There are packets on the edge that user hasn't seen yet (the packet inspector not open, etc) * When hovering...

This is something we took into account with the [runtime protocol](http://noflojs.org/documentation/protocol/#runtime). However, it is not yet utilised in either the runtimes or the UI