The grand plan should be a full IDE for BeanShell in the long run but
the priority (in decreasing importance, and increasing longer term plan)
(1)Get the existing <beanshell.jar> recognized as one of the plugin to
allow use of embeded mode beanshell in programs. I already done it,
email me if you want this minimalist plugin. This is nothing more than
writing a plugin.xml file for <beanshell.jar>
(2)Create a viewer. This viewer behave like the BeanShell Console.
(3)Enhance the viewer by providing command history logging + write
history to file so the history can serve as a starting point for Bean
Shell Script. Syntax coloring of the viewer should help.
(4)Full integration into Eclipse, allowing BeanShell Scripts to be
edited in the editor, and executed.
In essence, job 2 really looks like creating a SWT wrapper for
BeanShell. Hopefully this is a wrapper that programmers can reuse in
their program, e.g., Displaying the viewer in a dialog box or having its
I/O piped such that programmers can display as a dialog to help
formatting an apporpriate Bean Shell command if using the viewer (a
separate window is inappropriate).
Step (4) is probably a bit too grand, i.e., it is creating a full IDE
for BeanShell Script.
As you can see, I had structured the priority in a way that the higher
numbered one is build on the lower numbered one. Of course, this is not
the only way of planning for BeanShell development for Eclipse.
Please keep me posted. I might be able to contribute to this effort.
>I am toying with the idea (as a learning experience) of creating a BeanShell
>plugin for eclipse. It may not go anywhere but I was wondering what you
>would like to see included.
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>Beanshell-users mailing list