Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

VE Source Editor / Code Generation (CodeGen) component

Revision as of 11:49, 18 October 2007 by Unnamed Poltroon (Talk) (New page: Illustration 3:Architecture of the Eclipse VE CodeGen component Illustration 3 shows in more detail the architecture of the Visual Editor CodeGen compone...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Illustration 3:Architecture of the Eclipse VE CodeGen component

Illustration 3 shows in more detail the architecture of the Visual Editor CodeGen component.

The key elements of the VE Source Editor/CodeGen component are;

  • JavaVisualEditorPart
  • JavaSourceTranslator – an implementation of an IDiagramModelBuilder

and an IDiagramSourceDecoder

  • JavaBeanModelBuilder/CodeSnippetModelBuilder
  • the 'BDM', that is an instance of IBeanDeclModel and its related

classes.

  • Decoders and DecoderAdapters

These are described in more detail below.


JavaVisualEditorPart

JavaVisualEditorPart (JVEP) subclasses org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor which is the default Java Editor within Eclipse. This class serves not only as the embedded source editor for the Java code but is also the entry point for Eclipse VE. Hence it does a lot more than just provide editing support.

Illustration 4 summarizes the different roles that JVEP plays. Not only does it create the visual components that users interact with such as the Graphical Viewer and source editor, it also creates the IModelBuilder used to parse the Java code and build the VE Model, creates factory classes used to provide decoder classes as well as provide the source code editing function.

Hence the JVEP is a key class to customize in order to be able to use Visual Editor for a Groovy file.

Back to the top