Difference between revisions of "Vex"
Revision as of 11:08, 1 January 2010
Visual Editor for XML
Vex is an editor for XML documents. The "visual" part comes from the fact that Vex hides the raw XML tags from the user, providing instead a wordprocessor-like interface. Because of this, Vex is best suited for "document-style" XML documents such as XHTML and DocBook rather than "data-style" XML documents.
Vex is Standards-Based
Vex uses standard DTD files to define document types and CSS stylesheets to define document layout. Vex is Extensible
Vex is based on the Eclipse platform, the same platform used to build the popular Eclipse Java development environment. This foundation provides several advantages.
- The Eclipse platform implements a sophisticated plugin architecture, allowing Vex to be extended with third-party or custom, in-house plugins.
- Vex leverages many of the mature plugins that make up the Eclipse Java IDE such as the CVS interface, document searching and bookmarking facilities, and searchable help system.
- Vex is available with native look-and-feel on many platforms, including Windows, Linux/GTK, and Macintosh OS-X/Carbon.
- Java developers using the Eclipse IDE can import Vex into their IDE as a plugin, making it easy to maintain software documentation with Vex.
Vex is Reusable
The Vex editor widget is available as a pure Java, cross-platform component with bindings SWT. Developers can re-use this widget, for example as an RCP application.
Vex requires the Web Tools XML feature to be installed.
Vex is an incubating project. Integration builds may be retrieved from. http://build.eclipse.org/webtools/committers/
Continuous Integration builds which may or may not be stable, can be found on at https://build.eclipse.org/hudson/view/WTP/job/cbi-wtp-inc.vex//
The CI builds provide P2 update site zip files that can be used to install the latest version of Vex. Vex has been tested on Eclipse 3.4, 3.5, and 3.6.
There are numerous ways to contribute beyond code contributions. The Vex user manual is maintained on the wiki. Please feel free to update and keep it current. If you want to contribute code, please use a team project set to bring in the code you will need to make changes to the Vex code base.
Team Project Set:
Use the VEX Team Project set file to get retrieve the code and to provide patches for bugs and enhancements.