Editor configuration
All editors are configured in the Editors.xml configuration file, which maps an instance of either editor API to a key which can be used to reference that editor in project definition files and in the ContentTypes.xml global configuration file.The global configuration sets up default associations of editors with MIME types; in a project definition, those defaults can be overridden at the project level, or at the level of an xml-doc, xml-doctype or resource-directory.
< editor >
Editors are configured with this tag. Multiple editors are configured with several editor tags, and the document order in which they are listed controls the order in which they appear on screen.
key =
The key of the desired editor, as mapped in the Editors.xml document
Included Editors
There are nine editors included with HyperContent, all described in the Authoring section of this manual. Here is a list of each editor, by the key used to refer to it.xml
DTD-based XML editing with WYSIWYG XHTML enabled for any xml element with the name 'html'. Only used for xml documents.dublincore
Supports all 15 of the Dublin Core Metadata terms, which may be applied to files of any content type.text
Plain text editing, useful for any type of text file (e.g. DTDs, javascript, CSS)upload
Allows upload and download of files from the desktop to the server. Useful for any file type, especially arbitrary binary files.vcard
Allows VCard contact information to be stored in metadata. Recommended for use with XML files, which may contain additional data about the person.image
Crop and resize photos directly in the browser, with built in support for GIF, JPEG and PNG with automated conversions.spellcheck
Spell checker. As shipped, it can check words in XML elements and in Dublin Core title, description and keywords.navigation
Drag-and drop reordering of navigation items, plus easy addition of links and relabeling of items.