Hi everyone,

the previous excellent discussion on wrapping emacs seemed to bring up
an interesting topic.

What would be the right messaging architecture to passing information
between components of an IDE?

Something which has impressed me recently is Humanized's Enso. (
http://www.humanized.com/enso/beta/enso-developer-prototype) It's
become indispensible to me in Windows.

I noticed that you write new services for it as XML-RPC servers and
they provide a simple Python example which is easy to get running. I'm
now thinking of putting a couple of my own Python programs behind an
Enso front-end, which effectively means making them XML-RPC servers.

So my question is, is this too loosely coupled an architecture for a
pluggable IDE? Is it too heavy? Is it still likely to be too heavy in
a couple of years time?

phil jones

Reply via email to