[EclipseShell-developer] Re: About a groovy shell

[Werner S. (murphee) <wer...@gm...>]

Note: I didn't see this mail before due to a mailing list problem, so 
I'm answering this mail from the Web MailingList Archive:


Venkatesh Prasad Ranganath wrote:

>I am involved in a project in which I plan to provide access to the guts
>of an Eclipse plugin via Groovy.  

Interesting; take a look at the EclipseMonkey project, that might be helpful too (not for Groovy, but for
making access to Eclipse internals easy). The link:
http://www.eclipse.org/dash/


>provided by EclipseShell, I was planning on porting the Beanshell to
>operate with Groovy.  Is anybody in EclipseShell project working on such
>a plugin?  If not, would the project welcome such a contribution?

Yes, that'd be great.
As with the pnuts effort, I'll add links to the plugin when it's done or I'll think about
some other way of making it easy for users to access it. 


BTW: just a tip: maybe you want to use the Rhino Language provider as a starting point rather than 
the Beanshell one, as it's smaller and easier to change (I guess, maybe that's just my perception). 


>Also, is there as fixed naming scheme by which various Eclipse plugins
>can be accessed from within the shells?

Hmm... not sure what you mean. The language provider plugins need to have 
Eclipse-BuddyPolicy: global
in your language providers plugins Manifest.mf, which allows your plugin to see all exported classes of all 
installed plugins. This means you have access to all exported classes in your Eclipse installation.

Or do you want to access other information of plugins? 


murphee

-- 
Blog @ http://jroller.com/page/murphee
Maintainer of EclipseShell @ http://eclipse-shell.sourceforge.net/