Tree [d777b8] master / History
| File | Date | Author | Commit |
|---|---|---|---|
| interfaces | 2014-11-14 |
Kevin Rattai
|
[99e208] Added missing interfaces and removed debug files |
| reference_code | 2014-10-12 |
Kevin Rattai
|
[de60a0] Added syscalls as reference code for handling s... |
| src | 2014-11-21 |
Kevin Rattai
|
[d777b8] Added black box API node to prototype developme... |
| .gitignore | 2014-10-02 |
Kevin Rattai
|
[186202] Added reference_code which may be useful for th... |
| LICENSE | 2014-02-13 |
krattai
|
[c71d56] Initial commit |
| README.md | 2014-08-14 |
Kevin Rattai
|
[d9b8f7] Update README.md |
Read Me
monoflow
A monolithic flow based programming application
FBP is "a programming paradigm that defines applications as networks of "black box" processes, which exchange data across predefined connections by message passing, where the connections are specified externally to the processes."
Full explanation here: http://www.jpaulmorrison.com/fbp/
We have examined some 3D applications for IDE use: Possible 3DE application
This is the github version of the sourceforge project: https://sourceforge.net/projects/monoflow/
Why "MonoFlow"?
For all intents and purposes, the application / environment is intended to be fully extensible. In the same way that GNU/Linux is monolithic and extensible. I intend it to comprise specifically of a stub (to start and stop the primary application) as a "kernel equivalent" and will wrap around the developer environment as an IDE / interpreter (in the same manner as a shell) for the time being.