Yes but it's too trivial to implement as something separate from
Nick's JUCI. It should be included in it.
I think this is a great idea! Did I miss the post about JUCI? I presume this
does some sort of reflected invocation scheme so that Emacs looks like a
Java class to the Java side and vice
Andy Piper writes:
Yes but it's too trivial to implement as something separate from
Nick's JUCI. It should be included in it.
I think this is a great idea! Did I miss the post about JUCI? I presume this
does some sort of reflected invocation scheme so that Emacs looks like a
Java
PK == Paul Kinnucan [EMAIL PROTECTED] writes:
PK Yep. I'm looking forward to seeing what Nick comes up with.
Here's the package documentation that I have so far. I plan to expand
more on the later sections. I'm also willing to package up what code
I have and send that along, but I don't want
From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
Sent: Saturday, December 07, 2002 8:45 AM
To: Nick Sieger
Cc: [EMAIL PROTECTED]
Subject: RE: BanInfo wizard anyone?
Well, I didn't, but the beanshell is still directly
involved. Elisp
sends strings to the beanshell which invokes java
From: Nascif Abousalh-Neto [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 09, 2002 11:46 AM
To: Nick Sieger; Galen Boyer; [EMAIL PROTECTED]
Cc: Graham Bennett
Subject: Java - elisp communication (was RE: BanInfo wizard anyone?)
Hi Nick,
Well, I didn't, but the beanshell is still
Nick Sieger writes:
The translation layer could handle things like the java method
signature returning, say, a hashmap. The layer could have a
hashmap to alist converter.
I've actually got a working prototype of a generic
interface/translation layer that does just that.
Hi Christian,
The basic trick to integrating a bsh script with the
JDEE is to have the script write a Lisp form to
standard out and then invoke the script via the JDEE's
jde-eval function. The jde-eval function sends
an arbitrary beanshell expresion via standard I/O
to the beanshell and then
Paul Kinnucan writes:
Hi Christian,
The basic trick to integrating a bsh script with the
JDEE is to have the script write a Lisp form to
standard out and then invoke the script via the JDEE's
jde-eval function. The jde-eval function sends
an arbitrary beanshell expresion via
On Fri, 6 Dec 2002, [EMAIL PROTECTED] wrote:
Another idea would be to add options to the jde-jeval
function or new commands to
* evaluate a bsh expression (e.g., a script invocation)
and insert the result in a new Java source buffer
* evaluate a bsh expression and insert the
From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Galen Boyer
Sent: Friday, December 06, 2002 8:45 AM
To: [EMAIL PROTECTED]
Subject: Re: BanInfo wizard anyone?
On Fri, 6 Dec 2002, [EMAIL PROTECTED] wrote:
Another idea would be to add options to the jde-jeval
function or new commands
On Fri, 6 Dec 2002, [EMAIL PROTECTED] wrote:
From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Galen
Boyer Sent: Friday, December 06, 2002 8:45 AM To:
[EMAIL PROTECTED] Subject: Re: BanInfo wizard anyone?
[...]
The translation layer could handle things like the java method
signature
The translation layer could handle things like the java method
signature returning, say, a hashmap. The layer could have a
hashmap to alist converter.
I've actually got a working prototype of a generic
interface/translation layer that does just that. For now, I'm
calling it JUCI
12 matches
Mail list logo
