Visual programming and dataflow authoring for EmbeddedOS, layered on EoStudio and eBuild.
Status: Planned. There is no implementation in this repository yet. The
code that will become eFlow lives in eos
today, at (not yet started; EoStudio is the host).
This repository exists so the component has a home, an issue tracker, and a place to record decisions before any code moves. It is deliberately not a mirror: duplicating the sources here would give the platform two copies to keep in step, and §24 of the architecture document is explicit that internal modules should not be promoted into separate brands until they have stable interfaces and users.
- Visual/dataflow authoring of embedded applications
- Generation into the same project shape
ebuild newproduces - Round-tripping against EoStudio's editors
There is no implementation anywhere yet. §29 lists a full graphical IDE among the things to defer until the CLI and VS Code workflows are excellent.
| Implementation | eos → (not yet started; EoStudio is the host) |
| Maturity | eos/STATUS.md |
| Decision of record | Repository taxonomy — §22 |
The architecture document sets one condition, and it has not been met:
Visual programming inside EoStudio initially. — §22
Until then, work on eFlow happens in eos. Opening the split earlier would
cost a release cycle, a CI pipeline and a versioning story for a component
whose interface is still changing.
- Architecture & Ecosystem Design Document — §18 (Tooling / Later)
- Repository taxonomy — §22
- Organization model — §23
MIT. See LICENSE.