3 ms·
Lots of similar concepts to what we do with NoFlo and MicroFlo in Flowhub (http://flowhub.io/ http://flowhub.io/) -- and actually interesting that they went wit
by bergie 12y ago
Lots of similar concepts to what we do with NoFlo and MicroFlo in Flowhub (http://flowhub.io/ http://flowhub.io/) -- and actually interesting that they went with the more limited editor from Node Red instead of our open source UI (https://github.com/noflo/noflo-ui https://github.com/noflo/noflo-ui)
Here's one fun IoT project we did in Flowhub: http://bergie.iki.fi/blog/ingress-table/ http://bergie.iki.fi/blog/ingress-table/
In any case, great that SkyNet is open source. I'll look at wrapping the APIs to NoFlo components when I find a bit of time...
- cmatthieu 12y agoOur Octoblu designer is a MUCH more robust version of NodeRED. It's multi-tenant and sandboxed via Docker. Our goal with NodeBLU was to release a very simple client-side designer that didn't require setup and at the same time incorporated more client-side technologies such as: WebRTC, Google Speech APIs, HTML5 notifications, Game controllers, Chrome DB datastores, as well as SkyNet nodes.
- bergie 12y agoSounds very similar to NoFlo UI still. We have pretty much all those client-side features as components already :-) One thing that might be interesting to you is the protocol we use to talk between UI and runtimes, and runtime-to-runtime: http://noflojs.org/documentation/protocol/ http://noflojs.org/documentation/protocol/