> Nascif Abousalh-Neto wrote: > > As for avoiding learning Lisp, I think people who want to write Java > > extensions to Emacs are better off putting their effort in learning > > elisp than in learning a Java wrapper around elisp. > Paul, what about people that want to write a Java plug-in for *any* > editor? In that sense It's simple: they can't. Not all Java editors are written in Java - you'll always have different languages standing in the way of re-use... For maximum pluggability, you can go below programming language level and communicate using structured data - Emacs supports that (note how pluggable javac and other compilers are), but of course it has its own problems...
> JDEE/Emacs is too far away from the other IDEs out there. Not better > or worse, but different. It isn't just the case of Emacs - I wouldn't expect (for example) Microsoft tools to be scriptable in Java either... > True, there is no "standard" for plug-ins at this point, but the ones > already available (from NetBeans, > JEdit, JBuilder, just to name a few) don't rely on elisp... > Not to mention the plug-ins and tools that have already been written. > Is it a good position to simply > ignore them, or to have to rewrite them from scratch? Porting (much faster than clean-room implementation, but probably also less fun) would IMHO make sense - if there's interest, of course... A closed tool can't be ported, but I see that as a choice of its owners - nothing to argue about... > I think JDEE would greatly benefit by providing a true Java-based > plug-in architecture and removing the elisp "language barrier". What is I disagree. IMHO it's Emacs which would greatly benefit from being scriptable in multiple languages - but I don't see that happening this century... :-) > and easy to use way for Java designers to extend JDEE? Nothing against > learning elisp, but code re-use and standardization are worthwhile Well, Emacs is standartized on elisp. I agree that most Java tools are standartized on something entirely different, but if someting has to give, I'd try to push the Java tools first - Emacs is just too heavy to push around... Bye Vasek