Jump to: navigation, search

Difference between revisions of "Vex"

Line 1: Line 1:
 +
__NOTOC__
 
= Vex - A '''V'''isual '''E'''ditor for '''X'''ML =
 
= Vex - A '''V'''isual '''E'''ditor for '''X'''ML =
 
[[Image:Egg-incubation.png|right]]
 
[[Image:Egg-incubation.png|right]]

Revision as of 11:20, 1 January 2010

Vex - A Visual Editor for XML

Egg-incubation.png

Vexbanner.png

Vex hides the raw XML tags from the user, providing instead a wordp rocessor like interface. Vex uses standard DTD files to define document types and CSS stylesheets to define document layout. Vex contains definitions for DocBook and DITA. To edit other XML formats a DTD and a CSS are needed.

Vex is based on the Eclipse platform, the same platform used to build the popular Eclipse Java development environment:

  • 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.
  • The Eclipse platform implements a sophisticated plugin architecture, allowing Vex to be extended with third-party or custom, in-house plugins.
  • 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 instal Vex into their IDE as a plugin, making it easy to maintain software documentation or other XML files 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.
Note.png
Vex has moved from the SourceForge project site to Eclipse (see Original Project Proposal). John Krasney has contributed the code of Vex to Eclipse as of August 2008. All code is now licensed under the Eclipse Public License.


Download

New and Noteworthy

Vex requires the Web Tools XML feature to be installed.

Documentation

Contributing

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.

Other Resources