[dash-dev] Re: EclipseShell and DOMs

[Ward Cunningham <ward.cunningham@xxxxxxxxxxx>]

Werner -- Thanks for bringing this work to our attention. I watched  
the screencast and was very impressed. I would encourage you to  
support Rhino as our experience with Rhino has been very positive. We  
are also very interested in cooperating as we have a strong interest  
in scripting applied to many different problems in software  
development. So far we have focused only on teams sharing development  
procedures, a narrow scope, I admit.

We are also strongly interested in exploiting the plug-in  
capabilities of Eclipse. I'm pleased that you have made the  
interpreter pluggable. Was this difficult?

We have recognized the importance of specialized DOMs in order to  
make scripting have the feel one would expect when writing scripts.  
Would you be willing to work with us to develop a language  
independent plug-in interface for DOMs? We think we are language  
independent now. We have achieved this by keeping our interfaces very  
simple.

One experiment would be to try using one of our test DOMs in one of  
your scripts. Our api is still flexible. We would like to exercise it  
as much as possible before we tighten it up. Will you help?

We will be talking a lot about scripts at EclipseCon. Do you think we  
could have some experience sharing DOMs by then? I hope you are  
planning to attend. Best regards. -- Ward


On Feb 8, 2006, at 5:05 AM, Werner Schuster (murphee) wrote:

> hello Ward, hello Bjorn,
>
> I'm very interested in your work on DOMs to facilitate scripting of  
> Eclipse.
>
> I'm currently working towards a first release of EclipseShell, a  
> project that
> facilitates scripting in Eclipse with an interactive editor that  
> acts like a shell.
> I currently have support for
> - JRuby
> - Beanshell
> but the plugin is extensible, so support for Rhino is very simple  
> to do.
> If you're interested and would like to use EclipseShell, I could  
> put together some support for Rhino.
>
>
> I have a Flash demo and a pre-release ready for you to look at, I'd  
> just
> ask you *not to publish the sites just yet*, because I'd like to  
> wrap up my full release first.
>
> DEMO
> If you're still interested, see this Flash screencast that demos  
> some of the features of EclipseShell:
>
> http://eclipse-shell.sourceforge.net/screencasts/ 
> rdthelpersEclipseShell.htm
>
> Here the update site:
> http://eclipse-shell.sourceforge.net/update/
>
>
>
>
>
> Here a more detailed feature list:
> - customized Editor that acts as the shell
>  This is better than all the readline/textfield based shells I  
> know, as it allows
>  you to freely edit your code before *and* after execution.
> - AutoComplete
> the extension plugins can easily provide AutoComplete for objects  
> in their interpreter
> All the available runtimes support this, even the IRB one
> - SyntaxHighlighting
> it's possible to add in your own SyntaxHighlighting in the  
> extensions. The current
> ones are rather crude (just keyword highlighting), but they're  
> available
> - TextHovers
> textHovers can easily be provided, also in the extension plugins.
> - saving execution history
> this allows you to build up your code incrementally in the shell;  
> if you want to
> keep your code, simply do "Save as..." in your editor shell and save.
> If you used the file extension that the editor showed (rbij for  
> JRuby),
> re-opening the files will re-construct the code regions, ie. your  
> code groupings.
> This feels a bit like Workspace editors in Smalltalk.
> - some other features, like launching an external Java based script  
> language interpreter and
> control it from Eclipse. This will automatically setup CLASSPATHs  
> for the currently
> selected projects. This is still a bit wobbly and might not work  
> for you yet.
>
> Thanks,
>
> murphee
> --
> Blog @ http://jroller.com/page/murphee