pop open the hood and get your hands dirty - but how?
Simple: Use an interactive shell (eg. EclipseShell) and a
Beanshell, etc.). This is complemented by the EclipseMonkey DOM concept,
which makes individual Eclipse APIs much easier to use.
This has the potential to heave Eclipse to the level
of flexibility of tools like Smalltalk or Emacs.
The three themes of the talk are:
Example: create a GUI, say a class browser, by building it up
incrementally while working on live data, say a JDT project
Why? Faster turnover and it is quicker than restarting Eclipse a
lot (as is often necessary when building plugins, since Java
update existing class structures).
Example: script Eclipse JDT Debug API to automate queries of
debug model of a Launch or record data gathered at Debug
Breakpoints - create your own customized Debugger.
Why? Life is too short for doing monotonous tasks
Example: open an ECF (Eclipse Communication Framework)
connection to a
interactively find out what is possible with the
APIs and protocols.
Why? In many situations it is easier to just poke a live
object to see
how it works rather than poring over documentation, guessing how to make use of
The talk will show how interactive scripting can help with general programming,
developing Eclipse plugins and learning the ins and outs of Eclipse APIs.
The talk will include a demo showing how to build a Heap Walker using Java 6
the Eclipse Debug API and a demo showing how to explore the JDT APIs using live
The demos are supposed to show how to make use of tools like EclipseShell
DOMs. Samples of
demos are available as screencasts
Werner Schuster (murphee) is a programmer with a focus on Java, Eclipse, and dynamic languages such as (J)Ruby and Mathematica. Among other things, he's developed Eclipse plugins since 2003, both commercially and in the OpenSource space.
His blog is @ http://jroller.com/page/murphee