(New page: CKEditor offers a powerful and flexible output formatting system, giving developers full control on how the HTML produced by it must look like. It's possible to control every single tag on...) |
(→The HTML Writer: Typo in code corrected) |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | CKEditor offers a powerful and flexible output formatting system | + | CKEditor offers a powerful and flexible output formatting system. It gives developers full control over what the HTML code produced by the editor will look like. The system makes it possible to control all HTML tags and can give a different result for each one of them. |
== The HTML Writer == | == The HTML Writer == | ||
+ | Technically speaking, writing the final output is a task executed by the <code>[http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.htmlWriter.html CKEDITOR.htmlWriter]</code> class ("writer"), used by the <code>CKEDITOR.htmlDataProcessor</code> class. Therefore, the current writer instance for a specific editor instance can be retrieved by the <code>''editorInstance''.dataProcessor.writer</code> property. | ||
− | + | It is possible to configure several output formatting options by setting the writer properties. The following example summarizes the most used of them, giving their default values: | |
− | + | <source language="js"> | |
− | + | var writer = editor.dataProcessor.writer; | |
− | < | ||
// The character sequence to use for every indentation step. | // The character sequence to use for every indentation step. | ||
writer.indentationChars = '\t'; | writer.indentationChars = '\t'; | ||
− | // The way to close self closing tags, like | + | // The way to close self closing tags, like <br />. |
− | writer.selfClosingEnd = ' / | + | writer.selfClosingEnd = ' />'; |
// The character sequence to be used for line breaks. | // The character sequence to be used for line breaks. | ||
writer.lineBreakChars = '\n'; | writer.lineBreakChars = '\n'; | ||
− | // | + | // The writing rules for the <p> tag. |
writer.setRules( 'p', | writer.setRules( 'p', | ||
{ | { | ||
// Indicates that this tag causes indentation on line breaks inside of it. | // Indicates that this tag causes indentation on line breaks inside of it. | ||
− | indent | + | indent : true, |
− | // | + | // Inserts a line break before the <p> opening tag. |
− | breakBeforeOpen | + | breakBeforeOpen : true, |
− | // | + | // Inserts a line break after the <p> opening tag. |
− | breakAfterOpen | + | breakAfterOpen : true, |
− | // | + | // Inserts a line break before the </p> closing tag. |
− | breakBeforeClose | + | breakBeforeClose : false, |
− | // | + | // Inserts a line break after the </p> closing tag. |
− | breakAfterClose | + | breakAfterClose : true |
}); | }); | ||
− | </ | + | </source> |
+ | |||
== Setting Writer Rules == | == Setting Writer Rules == | ||
− | + | Because the writer is a property of each editor instance, and also due to its dependency on the writer plugin to be loaded, the best way to modify it is by listening to the <code>[http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.html#event:instanceReady instanceReady]</code> event, so it is safe to assume that the <code>dataProcessor</code> property will be loaded and ready for changes. The following code shows an example of this approach used when creating an editor instance: | |
− | Because the writer is a property of each editor instance, and also | + | <source language="js"> |
− | < | + | CKEDITOR.replace( 'editor1', |
{ | { | ||
− | on | + | on : |
{ | { | ||
− | instanceReady | + | instanceReady : function( ev ) |
{ | { | ||
− | // Output paragraphs as | + | // Output paragraphs as <p>Text</p>. |
this.dataProcessor.writer.setRules( 'p', | this.dataProcessor.writer.setRules( 'p', | ||
{ | { | ||
− | indent | + | indent : false, |
− | breakBeforeOpen | + | breakBeforeOpen : true, |
− | breakAfterOpen | + | breakAfterOpen : false, |
− | breakBeforeClose | + | breakBeforeClose : false, |
− | breakAfterClose | + | breakAfterClose : true |
}); | }); | ||
} | } | ||
} | } | ||
}); | }); | ||
− | </ | + | </source> |
− | Another | + | Another method is to use the <code>[http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.html CKEDITOR]</code> object, so all editor instances will be changed: |
− | < | + | <source language="js"> |
+ | CKEDITOR.on( 'instanceReady', function( ev ) | ||
{ | { | ||
− | // | + | // Ends self closing tags the HTML4 way, like <br>. |
− | ev.editor.dataProcessor.writer.selfClosingEnd = ' | + | ev.editor.dataProcessor.writer.selfClosingEnd = '>'; |
}); | }); | ||
− | </ | + | </source> |
Latest revision as of 14:53, 13 January 2011
CKEditor offers a powerful and flexible output formatting system. It gives developers full control over what the HTML code produced by the editor will look like. The system makes it possible to control all HTML tags and can give a different result for each one of them.
The HTML Writer
Technically speaking, writing the final output is a task executed by the CKEDITOR.htmlWriter
class ("writer"), used by the CKEDITOR.htmlDataProcessor
class. Therefore, the current writer instance for a specific editor instance can be retrieved by the editorInstance.dataProcessor.writer
property.
It is possible to configure several output formatting options by setting the writer properties. The following example summarizes the most used of them, giving their default values:
var writer = editor.dataProcessor.writer; // The character sequence to use for every indentation step. writer.indentationChars = '\t'; // The way to close self closing tags, like <br />. writer.selfClosingEnd = ' />'; // The character sequence to be used for line breaks. writer.lineBreakChars = '\n'; // The writing rules for the <p> tag. writer.setRules( 'p', { // Indicates that this tag causes indentation on line breaks inside of it. indent : true, // Inserts a line break before the <p> opening tag. breakBeforeOpen : true, // Inserts a line break after the <p> opening tag. breakAfterOpen : true, // Inserts a line break before the </p> closing tag. breakBeforeClose : false, // Inserts a line break after the </p> closing tag. breakAfterClose : true });
Setting Writer Rules
Because the writer is a property of each editor instance, and also due to its dependency on the writer plugin to be loaded, the best way to modify it is by listening to the instanceReady
event, so it is safe to assume that the dataProcessor
property will be loaded and ready for changes. The following code shows an example of this approach used when creating an editor instance:
CKEDITOR.replace( 'editor1', { on : { instanceReady : function( ev ) { // Output paragraphs as <p>Text</p>. this.dataProcessor.writer.setRules( 'p', { indent : false, breakBeforeOpen : true, breakAfterOpen : false, breakBeforeClose : false, breakAfterClose : true }); } } });
Another method is to use the CKEDITOR
object, so all editor instances will be changed:
CKEDITOR.on( 'instanceReady', function( ev ) { // Ends self closing tags the HTML4 way, like <br>. ev.editor.dataProcessor.writer.selfClosingEnd = '>'; });