On Sat, Mar 23, 2002 at 04:10:45PM +0000, Vaclav Barta wrote:
[ snip ]
> Hmm, I believe it can be made to work, but I don't like the circular
> dependency - if Emacs depends (for some functionality) on your tool,
> then Emacs should be the front end, your tool the back end and it
> doesn't need to know it's driven from Emacs at all... It would make
> testing easier, allow plugging in new front and back ends
> independently - all the standard arguments apply...
I should explain the structure of my system:
Emacs/JDE Another Tool
| |
Java plumbing Java plumbing
\ /
\ /
Tool Interface
|
|
Refactoring Framework
As you can see from my rather poor ASCII artwork, the framework is well
separated from the front end as it is. It doesn't really matter how
closely coupled the Java plumbing code is to the particular tool in
question because it will only be used for that tool.
So I think that the following setup should work ok:
| --- gnuclient ---> |
Java plumbing | | Emacs/JDE
| <--- jde-jeval --- |
This seems like quite a neat solution to me, because it doesn't involve
hacking up the gnuclient/gnuserv protocol. It also doesn't involve me
doing too much elisp, which is a good thing since I know very little
about it.
Got a bit carried away with diagrams there :)
Thanks for your time,
--
Graham Bennett
[EMAIL PROTECTED] ICQ: 17566658
