Coral has something too, but he's going to have to document it himself.
I have heard of a program that takes dia files and generates perl code. It's not specific to POE, but it could be warped for someone's nefarious purposes. Muah ha ha ha ha!
When coral makes a page for his project, don't forget to list these issues:
- Need a way to tie graphical component representations to their interface hooks (emitted and accepted messages).
/POE DFA is a work in progress, if you can call neglect progress. It accepts meta-code files (often containing real code) that describe the flow of execution from one state to another. The code generator program will output perl code for POE. It also can generate GraphViz input files that generate "pretty" flow diagrams of the resulting program.
Rocco: POE's original purpose (and the second acronym expansion) was to be a Perl Object Environment. The idea was to create a programming environment that worked like a MUD.
- Multiple developers and users (actors)
- Autonomous, roving objects (bots, agents)
- Natural-language interaction
- Object persistance and inter-system transferrence (roaming agents)
- Security (intra- and inter-system sandboxes)
- Cause and effect rules built into the low-level object system (basic design and interaction by contract)
- Object, will you do this for me?
- Object, you are doing this for me.
- Object, this has been done.
- Referential integrity amongst objects.
- Probably others which currently escape me.
There is a lot of stuff to put up here, but there is no time to do it right now. ToDo: Post prototypes, design documents, and notes. Oh, gods, the notes.