David Seikel wrote:
After a somewhat heated debate in #edevelop yesterday, I decided to
start writing my first E17 code, a module that I like to call emu.
Wish I'd seen that, have a log?
Emu will eventually be a generic scriptable E17 module who's purpose in
life is to allow people to write E17 modules in whatever random
programming language they like. Emu supplies all the E17 gooey
goodness, and the random programming language supplies the backend
logic.
Sounds like a small chunk of what Evoak would provide.
The first version will just be an interface to arbitrary e menus, using
a brain dead, god awful, just off the top of my head text based
stdin/stdout protocol. The second version may use a better protocol
and/or a better IPC method. The final version will use a well thought
out IPC protocol to all things moduly.
Evoak has the simple protocol in place already.
Then there are the multiple copies of the same module running at the
same time issues that I know nothing about. To be useful, emu will
have to cater for that.
I like the idea, but it seems like a neutered version of Evoak. I'd
rather see evoak worked on, even if it's a longer term goal...
-Blake
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
