Abstract:
delicious | 
digg | 
dzone
This screen cast demonstrates features that are implemented in the first version of the Rich Text Editor widget.
Currently, the only way to get rich text editing capabilities inside an Eclipse RCP application is to use the native browser widget. This is powerful, but not a very flexible solution. The goal of the Rich Text Editor project is to create WYSIWYG Markup editor, which will be based on StyledText widget and will allow basic HTML authoring, as well as support most features from jface text editing infrastructure.
delicious | digg | dzone
Votes: 2 
Comments
Is the goal to support editing of arbitrary...
Is the goal to support editing of arbitrary markup, or only markup required for font formatting and special "characters" like Images? The reason I ask is the use of StyledText, which is more of a source editor than a structured DOM editor. You could take a DOM tree and try to flatten it into StyleItems, but that seems like a painful exercise if you want to support real markup. Ultimately, you'd have to keep some other structured model external to the widget and just use the widget for rendering, which is not one of its strengths.
How would you make StyleText render:
<OL>
<LI>This should be a 1</LI>
<UL>
<LI>Sub A</LI>
<LI>Sub B</LI>
</UL>
<LI>This should be a 2</LI>
</OL>
With proper numbering, spacing, and indentation?
According to goal: The goal is to support...
According to goal: The goal is to support arbitrary (but not very complex) markup. For example we are planning to support nested lists and and simple html tables, but we are not planning to support complex styling and css).
According to reasons to use styled text: The goal is to be able to reuse eclipse JFace text api in applications that require rich text markup.
For example we are planning to create a editor for trac wiki wich will allow inline editing of code in snippets in some moment.
According to rendering: For a complex cases like case mentioned by you, we have our own extension of StyledText class wich is distributed as fragment to the org.eclipse.swt bundle