The rules for detecting which part editor to use are as follows:
- if there is part specific editor configured, use that
- if the "Daisy HTML" flag of the part type is true, use the HTML editor
- in all other cases, show the upload-editor
To use a custom editor for a certain part, a file called <partTypeName>.xml should be created in the following directory:
The file should contain some XML like the following:
<?xml version="1.0"?> <partEditor xmlns="http://outerx.org/daisy/1.0#parteditor" class="..."> <properties> <entry key="...">...</entry> </properties> </partEditor>
The class property of the partEditor element should contain the class name of a class implementing the following interface:
The properties element is optional and can be used to configure the part editor.
Besides the default editors, there is one example editor included in Daisy: a plain text editor. Suppose you have a part called MyPlainText and you want to use this editor for it, you need to create a file called MyPlainText.xml in the above mentioned directory, and put the following XML in it:
<?xml version="1.0"?> <partEditor xmlns="http://outerx.org/daisy/1.0#parteditor" class="org.outerj.daisy.frontend.editor.PlainTextPartEditor$Factory"> </partEditor>
Once you save this file, the editor will become immediately active (no need to restart the Wiki). If you do not see the editor, check the cocoon error log.