The Visual Editor (VE) was designed in the image of Eclipse itself; a high
function end point built on a powerful and extensible API. This tutorial is a
deep dive into the internals of the Visual Editor framework to show how to
extend its capabilities as well as support new widget toolkits.
The tutorial will divided into three parts:
1) An introduction to the VE's internals; the Java EMF Model (JEM), the
file extension mechanism, the target VM architecture, and the use of GEF & JDT.
To illustrate the VE, three simple scenarios will be covered; a) adding a
SWG custom control to the palette with bespoke design time behavior, b) adding
a new layout manager, and c) adding general support for "morph" capability to
2) Using an alternative persistence format other than Java, such as XML. This
is useful for those who are using technologies such as XSWT, XAML, SwingML and
other markup languages to describe their GUI
3) Using a Java GUI toolkit that isn't Swing or SWT. This example will use a
MIDP LCDUI toolkit and show how the VE's target VM architecture works. It can
be used in a fashion where a peer design time class library is used to create a
rich GUI building experience. This illustrates how code generation decoders
should be used to ensure that the correct runtime code is created and parsed.
IBM employee and comitter on the Visual Editor project. Interested in anything to do with Java GUIs, and am on the expert group for JSR 273 "Design time API for JavaBeans" and was on the expert group for JSR 75 - "Long term persistence of JavaBeans". Desktop Java Editor for the "Java Developers Journal".
After receiving his B.S. and M.S. in Computer Science from Penn State University he started working for IBM. Over the years he has worked on many different projects. For the past 12 years he has worked on Visual Editors for VisualAge Smalltalk, VisualAge Java, VisualAge C++, and currently the Visual Editor project in Eclipse and for IBM Rational VE tooling to support Web/J2EE development.