upgrading tinymce to 2.0.5.1

This commit is contained in:
JT Smith 2006-04-15 20:03:31 +00:00
parent cb2a8d025e
commit 00d46f6148
342 changed files with 13043 additions and 11487 deletions

View file

@ -1,3 +1,156 @@
Version 2.0.5.1 (2005-03-22)
Fixed bug where emtpy paragraphs sometimes got removed in MSIE.
Fixed bug where autosave plugin was running even in fullscreen mode.
Fixed bug where browse and color image button urls in form_utils.js where hardcoded.
Version 2.0.5 (2005-03-21)
Added API docs for the TinyMCE_Popup class that is used by all dialogs in TinyMCE.
Added new TinyMCE_Layer class to the core of TinyMCE plugins will be using this later on.
Added new loadPlugin function, use this to load external plugins.
Added instructions on how to contribute language packs.
Added new support for multiple content_css files, based on contribution by Man-Chicken.
Added new table_cell_limit, table_row_limit, table_col_limit options, based on contribution by Man-Chicken.
Added new fix_list_elements option, if this is set to true UL/OL lists will be forced XHTML valid on cleanup.
Added new fix_table_elements, if this is set to true tables will be moved outside paragraphs.
Fixed so input and button as closed elements in the cleanup logic.
Fixed so the mceButtonSelected is more visible with darker background in the editor_ui.css.
Fixed issue where charmap.js was calling switchClass that's reserved for buttons.
Fixed issue where the directionality option wasn't used in the preview plugin.
Fixed issues with nestled bullet lists pasted from Word 2003.
Fixed bug where button wasn't selected correctly in MSIE due to a CSS issue.
Fixed bug where ask mode wasn't working on DIV elements in Firefox and Opera.
Fixed bug where the mceAddFrameControl command wasn't working correctly.
Fixed bug where language packs wasn't imported correctly in plugins loaded externaly.
Fixed bug where focusing external input elements was visible in element path under MSIE.
Fixed bug where fullscreen plugin wasn't opening the window fullscreen in Firefox.
Fixed bug where style select dropdown wasn't working in Firefox when used in fullscreen mode.
Fixed bug where the fix_content_duplication wasn't working anymore.
Fixed bug where MSIE sometimes generated empty paragraphs.
Fixed bug where MSIE sometimes generated tags like <//tag>.
Fixed bug where the directionality option produced a error for the color picker dialog.
Fixed bug where configured callback options wasn't executed correctly in fullscreen mode.
Fixed bug where tags got generated as <*> some times in Gecko.
Fixed bug where the cursor was placed within a the anchor when inserting a new one in Gecko.
Fixed bug where convert_fonts_to_span option wasn't working correctly with new cleanup engine.
Fixed various language pack issues such as invalid characters.
Fixed naming conflict with zoom plugin and the format select box.
Fixed so that the initialization of the editor is slightly faster.
Removed all language packs except the english one from the core package. [BREAKS COMPATIBLITY]
Version 2.0.4 (2006-02-24)
Fixed bug where fullscreen plugin was using the tinymce_dev.js script.
Fixed bug where events where having a return true; statement infront of them.
Fixed bug where theme_advanced_toolbar_location option wasn't working.
Fixed bug where select lists wasn't working if you touched them with the tab key.
Fixed bug where auto reset design mode wasn't working correctly.
Fixed bug where null was inserted in paste button action in MSIE.
Fixed bug where _template plugin had a , instead of . character on e.type.
Fixed bug where src, href where replaced to xsrc and xhref in comments.
Fixed bug where paste_cleanup_on_paste option wasn't working correctly with the paste plugin.
Fixed bug where MSIE was reporting an error when TinyMCE was placed in a frame and not focused.
Fixed bug where clipboard_msg wasn't entity decoded corectly before displaying it in confirm box.
Fixed bug where mceRemoveControl wasn't working correctly on DIV elements.
Fixed bug where mceInsertContent/mceReplaceContent produced error when a empty string was inserted.
Fixed so the default valid_elements option is more XHTML valid.
Fixed issue where style formatting wasn't handled when pasting content from Word.
Fixed issue where ' characters wasn't entity encoded, they are now encoded into &#39; and not &apos;.
Fixed issue with empty paragraphs, these are now filled with &nsbp; if they are empty.
Added documentation on how the # prefix can be used in the valid_elements option.
Added new options paste_remove_styles and paste_remove_spans to paste plugin.
Added possibility to have empty default attributes values.
Version 2.0.3 (2006-02-13)
Added missing buttons to button reference page in documentation.
Added dt,dl,dd elements to default_valid elements config value.
Added new support for self registrering plugins.
Added new callback for themes and plugins handleEvent and the handle_event_callback option.
Added new execcommand_callback option, this enables you to add custom execcommand logic on page level.
Added new custom_shortcuts option, this enables you to disable plugin/theme specific keyboard shortcuts.
Added new addShortcut to TinyMCE_Control, this enables plugin to register custom keyboard shortcuts.
Added new getButtonHTML function to TinyMCE core, this function makes it easier for plugins/themes to make buttons.
Added more documentation on how to write plugins and updated the _template plugin.
Added more documentation on how to write custom themes.
Fixed so the default window size of the source editor is larger in the advanced theme.
Fixed so all internal plugins use the new auto registration and separation logic.
Fixed so all internal themes use the new auto registration and separation logic.
Fixed so the Safari warning is switched off by default.
Fixed so cursor position isn't moved when performing a cleanup.
Fixed so cursor position is correct when performing undo/redo actions.
Fixed so all themes/plugins now use a:hover to produce the mouse over button effect.
Fixed so it uses the DOMContentLoaded and onreadystatechange instead of onload.
Fixed so the simple theme also supports the button_tile_map option.
Fixed so the selection/cursor is moved to the beginning of area on search/replace.
Fixed callback handling to reduce logic, improve performance and flexibility.
Fixed documentarion error for the paste plugin, contributed by Jochen Metzger.
Fixed bug that made the cleanup process to hang MSIE on specific content.
Fixed bug with absolute to relative URL convertion logic if the absolute URL didn't have a path.
Fixed bug where about.htm in advanced theme refered to a non existing css file.
Fixed bug with defParam and the event_elements option.
Fixed bug where fullscreen plugin wasn't correctly setup with editor contents.
Fixed bug where paste/drop converted relative URLs incorrectly in MSIE.
Fixed bug with inlinepopups not restoring selection on close window in MSIE.
Fixed bug where selection was lost when a new column/row was inserted in a table running in Gecko.
Fixed bug where save plugin wasn't working in fullscreen mode.
Fixed bug where fullscreen plugin wasn't working in Opera.
Fixed bug where editor resizing in advanced theme wasn't working in Opera.
Fixed bug where cursor position was placed at the end of instance on word paste.
Fixed bug where a tinyMCE is undefined error was reported in Firefox.
Fixed compatiblity issues with new cleanup plugin and the prototype.js library.
Renamed the mceItemEditable/mceItemNonEditable to mceEditable/mceNonEditable.
Renamed the TinyMCEControl class to TinyMCE_Control, TinyMCE_ is the valid class prefix.
Removed the getInsertLinkTemplate and getInsertImageTemplate functions from themes and from API.
Removed insertImage and insertLink from TinyMCE core, they are moved to the advanced theme.
Removed opacity workaround made for Opera Preview 1, download Opera Preview 2 instead.
Removed search backward function from replace dialog since it could result in a infinite loop.
Marked insertlink_callback, insertimage_callback options as deprecated these can be replaced with execcommand_callback.
Moved selection specific methods to a new class. For example inst.selectNode is now inst.selection.selectNode.
Updated German language pack, contributed by Ace Man.
Version 2.0.2 (2006-01-24)
Added updated Danish language pack contributed by Jan Moelgaard, John Dalsgaard and Bo Frederiksen.
Added updated Czech language pack contributed by michi aka mishal.
Added new Slovenian language pack contributed by Domen Kosir.
Added new Turkish language pack contributed by Engin Dumlu.
Added new save_onsavecallback option to the save plugin, this function is called on save.
Added new save_enablewhendirty option to the save plugin, this will disable the button until changes are made.
Added new onpageload callback event, this event is called when the page is loaded but before instances are made.
Added new accessibility_focus option, this enables you to control if buttons should be tab focusable or not.
Added new greek alpha character to charmap dialog.
Added new Scaron,scaron,Alpha entities to the default value of the entities option thanks to Kevin Rodgers.
Added new contextmenu items link.unlink,advhr contributed by Speednet.
Added new paste_insert_word_content_callback option for the paste plugin.
Added new cleanup plugin, this will replace the one inside the core ones it's considered stable.
Added cancel button to color picker contributed by Speednet.
Fixed various documentation errors and typos, modified the FAQ.
Fixed issue where the first handleNodeChange call was done to early in initialization.
Fixed issue with Dutch language pack for advlink plugin.
Fixed issue where dialogs was to short when dialog_type option was set to modal in MSIE.
Fixed bug where insert image under Gecko resulted in a broken image if it was inserted a the beginning of a element.
Fixed bug where mceVisualAid class wasn't removed from TH elements on save.
Fixed bug where the href attribute area elements gets converted to xhref.
Fixed bug with document relative anchors being forced absolute even when the convert_urls was set to false.
Fixed bug where some plugins produced &gr; intead of &gt; entities on string encoding.
Fixed bug where some characters in charmap dialog was double encoded in Firefox/Gecko.
Fixed bug with XML core entities wasn't encoded when using raw or numeric value in entity_encoding option.
Fixed bug where classes was removed from table,td,th elements when the verify_css_classes option was enabled.
Fixed bug where elements was getting a visual aid class if a default or force class attribute value rule was used.
Fixed bug where strong/em rules didn't handle the -/+ prefixes correctly under Firefox/Mozilla.
Fixed bug where non textarea elements didn't work when submiting content.
Fixed bug where a access denied error was produced when using contextmenu together with modal dialogs under MSIE.
Fixed bug where fullscreen plugin didn't call custom cleanup functions when passing content back and forth.
Fixed issue where default rule for font tags didn't have a + prefix in valid_elements.
Fixed issue with CSS where "arrow" was used instead of "default" for cursor replacement.
Fixed issue where the replace button replaced the current selection first time it was used.
Fixed issue with missing title for the advhr dialog.
Fixed issue with div not beeing usable in the theme_advanced_blockformats option.
Fixed issue in with translation in the German language pack.
Fixed so the word wrap toggle for source view functions in Firefox/Mozilla.
Fixed so title attribute of emotion images gets inserted aswell as alt.
Fixed so the insert return on popups is checked by default in advlink.
Fixed so url gets filled when empty if a user selects a popup url.
Fixed so some init settings gets trimmed from whitespace.
Fixed so charmap closes when a char is selected since most of the time users only need one char.
Fixed so the link and image dialogs of advanced theme are styled with the new 2.x layout.
Fixed accessibility issuew with the link, image and advhr dialogs.
Fixed so the advhr dialog uses the new 2.x layout.
Fixed XHTML compliance for Preview plugin contributed by Bo Frederiksen.
Fixed entity decoding problem with insert button of the advhr plugin contributed by Bo Frederiksen.
Version 2.0.1 (2005-12-02)
Fixed critical bug in some MSIE versions when submiting content.
Version 2.0 (2005-12-01)

View file

@ -13,7 +13,7 @@
<div class="content">
<h2>General information</h2>
<div class="section">
<p>TinyMCE is a powerful WYSIWYG editor control for web browsers such as MSIE or Mozilla that enables the user to edit HTML contents in a more user friendly way. The editor control is very flexible and it's build for integration purposes for example usage within systems like Intranets, CMS, LMS and so forth.</p>
<p>TinyMCE is a powerful WYSIWYG editor control for web browsers such as MSIE or Mozilla that enables the user to edit HTML contents in a more user friendly way. The editor control is very flexible and it's built for integration purposes for example usage within systems like Intranets, CMS, LMS and so forth.</p>
<p>
TinyMCE is developed by <a href="http://www.moxiecode.com">Moxiecode Systems AB</a> and is currently released under the &quot;LGPL&quot; license, read the license agreement for details.
</p>
@ -33,7 +33,7 @@
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -76,7 +76,7 @@
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -24,6 +24,7 @@
<ul>
<li class="list_subtitle">Code / Solutions / Features</li>
<ul>
<li>donadoni</li>
<li>Michael Keck</li>
<li>Victor Nilsson</li>
<li>Jürgen Baute</li>
@ -73,7 +74,7 @@
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -16,15 +16,15 @@ body {
h1 {
font-size: 18px;
font-weight: bold;
padding: 0px;
padding: 0;
margin: 4px;
}
h2 {
font-size: 14px;
font-weight: bold;
padding: 0px;
margin: 0px;
padding: 0;
margin: 0;
margin-top: 4px;
margin-bottom: 4px;
}
@ -32,8 +32,8 @@ h2 {
h3 {
font-size: 11px;
font-weight: bold;
padding: 0px;
margin: 0px;
padding: 0;
margin: 0;
margin-bottom: 3px;
}
@ -57,19 +57,19 @@ p {
.helpindex {
margin-left: 20px;
padding-left: 0px;
padding-left: 0;
}
.optionlist {
margin: 0px;
padding: 0px;
margin: 0;
padding: 0;
margin-bottom: 10px;
}
.optionlist li {
padding: 0px;
margin: 0px;
padding: 0;
margin: 0;
margin-top: 3px;
margin-bottom: 3px;
margin-left: 10px;
@ -90,8 +90,8 @@ p {
}
code, pre {
margin: 0px;
padding: 0px;
margin: 0;
padding: 0;
background-color: #E6EBF1;
}
@ -142,4 +142,27 @@ a {
thead {
background-color: #E6EBF1;
}
.btable {
}
.btable th {
border: 1px solid gray;
vertical-align: top;
}
.btable td {
border: 1px solid gray;
vertical-align: top;
}
.plist {
list-style-type: none;
margin: 0;
padding: 0;
}
.plist li {
padding-bottom: 3px;
}

View file

@ -28,7 +28,8 @@ paste_desc : 'Paste (Ctrl+P)'
<p>
Remember the last translation line should not have a , character at the end. The first parameter to the addToLang is the prefix to add before each variable, this was added to reduce the overall size of the language packs to reduce the overall download time.
</p>
<p><h3>Files to edit</h3>
<h3>Files to edit</h3>
<p>
When translating TinyMCE, these are the files that currently needs to be translated:
</p>
<p>
@ -39,11 +40,16 @@ paste_desc : 'Paste (Ctrl+P)'
<p>
Notice some language variables may include a name/url of a gif image or simmilar, for example the button for bold has a "F" character in the Swedish language pack. There are also relative window sizes located in the language packs, for example is the link dialog needs to be bigger inorder to fit a specific translation you can alter the width of the window by modifying these variables.
</p>
<h3>Contributing your language pack</h3>
<p>
Go to the <a href="http://sourceforge.net/tracker/?atid=635684&group_id=103281&func=browse">sourceforge patch page</a> and upload a zip containing all the language files in the correct directory structure.<br /><br />
Please translate all the plugins, even if you aren't using them.<br />
</p>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -14,239 +14,212 @@
<h2>Creating your own plugins</h2>
<p>
Creating you own plugins for the TinyMCE application is fairly easy if you know the basics of HTML, CSS and Javascript. The most easy way is to copy the &quot;_template&quot; directory or one of the other core plugins and work from there. The &quot;_template&quot; directory is a tutorial plugin that shows how to create a plugin. After you copy the template you need to change the red sections marked below to the name of your plugin this is needed so that plugins don't overlap in other words it gives the plugin a unique name. Then just alter the source code as you see fit remember that your custom plugins needs to be located in tiny_mce's &quot;plugins&quot; directory. If you want you may add plugin specific options/settings but remember to namespace them in the following format &quot;&lt;your plugin&gt;_&lt;option&gt;&quot; for example &quot;yourplugin_someoption&quot;.
Creating you own plugins for the TinyMCE application is fairly easy if you know the basics of HTML, CSS and Javascript. The most easy way is to copy the &quot;_template&quot; directory or one of the other core plugins and work from there. The &quot;_template&quot; directory is a tutorial plugin that shows how to create a plugin. After you copy the template you need to change the red sections marked below to the name of your plugin this is needed so that plugins don't overlap in other words it gives the plugin a unique name.
</p>
<p>If you want you may add plugin specific options/settings but remember to namespace them in the following format &quot;&lt;your plugin&gt;_&lt;option&gt;&quot; for example &quot;yourplugin_someoption&quot;.</p>
<p>Specific callback functions that you don't need or doesn't do anything can be removed.</p>
<div class="separator"></div>
<h3>Plugin directory structure</h3>
<p>
The example below has three functions, these are explained in greater detail below.
<table class="btable">
<thead>
<th>File/Directory</td>
<th>Description</td>
</thead>
<tbody>
<tr><td>css</td><td>Plugin specific CSS files</td></tr>
<tr><td>docs</td><td>Plugin specific documentation</td></tr>
<tr><td>images</td><td>Plugin specific images</td></tr>
<tr><td>jscripts</td><td>Plugin specific jscripts for HTML dialogs</td></tr>
<tr><td>langs</td><td>Plugin specific language files</td></tr>
<tr><td>editor_plugin.js</td><td>Editor plugin file (compressed).</td></tr>
<tr><td>editor_plugin_src.js</td><td>Editor plugin file (source).</td></tr>
<tr><td>somedialog.htm</td><td>Plugin specific dialog HTML file.</td></tr>
</table>
</p>
<div class="separator"></div>
<h3>Plugin example source</h3>
<p>
The example below shows a simple empty plugin and all possible callbacks.
</p>
<p>
<div class="example">
<pre>
function TinyMCE_<span class="marked">yourplugin</span>_getInfo() {
// Should return info about the plugin to be presented in about dialog
return {
longname : 'Some plugin name',
author : 'Your name',
authorurl : 'http://www.yoursite.com',
infourl : 'http://www.yoursite.com/docs/..',
version : '1.0'
};
var TinyMCE_<span class="marked">SomeName</span>Plugin = {
/**
* Returns information about the plugin as a name/value array.
* The current keys are longname, author, authorurl, infourl and version.
*
* @returns Name/value array containing information about the plugin.
* @type Array
*/
getInfo : function() {
return {
longname : 'Your plugin',
author : 'Your name',
authorurl : 'http://www.yoursite.com',
infourl : 'http://www.yoursite.com/docs/template.html',
version : "1.0"
};
},
/**
* Gets executed when a TinyMCE editor instance is initialized.
*
* @param {TinyMCE_Control} Initialized TinyMCE editor control instance.
*/
initInstance : function(inst) {
// You can take out plugin specific parameters
alert("Initialization parameter:" + tinyMCE.getParam("<span class="marked">somename</span>_someparam", false));
// Register custom keyboard shortcut
inst.addShortcut('ctrl', 't', 'lang_<span class="marked">somename</span>_desc', 'mceSomeCommand');
},
/**
* Returns the HTML code for a specific control or empty string if this plugin doesn't have that control.
* A control can be a button, select list or any other HTML item to present in the TinyMCE user interface.
* The variable {$editor_id} will be replaced with the current editor instance id and {$pluginurl} will be replaced
* with the URL of the plugin. Language variables such as {$lang_somekey} will also be replaced with contents from
* the language packs.
*
* @param {string} cn Editor control/button name to get HTML for.
* @return HTML code for a specific control or empty string.
* @type string
*/
getControlHTML : function(cn) {
switch (cn) {
case "<span class="marked">SomeControl</span>":
return tinyMCE.getButtonHTML(cn, 'lang_<span class="marked">someplugin</span>_<span class="marked">button</span>_desc', '{$pluginurl}/images/<span class="marked">someimage</span>.gif', '<span class="marked">mceSomeCommand</span>');
}
return "";
},
getControlHTML : function(cn) {
switch (cn) {
case "advhr":
return tinyMCE.getButtonHTML(cn, 'lang_insert_advhr_desc', '{$pluginurl}/images/advhr.gif', 'mceAdvancedHr');
}
return "";
},
/**
* Executes a specific command, this function handles plugin commands.
*
* @param {string} editor_id TinyMCE editor instance id that issued the command.
* @param {HTMLElement} element Body or root element for the editor instance.
* @param {string} command Command name to be executed.
* @param {string} user_interface True/false if a user interface should be presented.
* @param {mixed} value Custom value argument, can be anything.
* @return true/false if the command was executed by this plugin or not.
* @type
*/
execCommand : function(editor_id, element, command, user_interface, value) {
// Handle commands
switch (command) {
// Remember to have the "mce" prefix for commands so they don't intersect with built in ones in the browser.
case "mce<span class="marked">SomeCommand</span>":
// Do your custom command logic here.
return true;
}
// Pass to next handler in chain
return false;
},
/**
* Gets called ones the cursor/selection in a TinyMCE instance changes. This is useful to enable/disable
* button controls depending on where the user are and what they have selected. This method gets executed
* alot and should be as performance tuned as possible.
*
* @param {string} editor_id TinyMCE editor instance id that was changed.
* @param {HTMLNode} node Current node location, where the cursor is in the DOM tree.
* @param {int} undo_index The current undo index, if this is -1 custom undo/redo is disabled.
* @param {int} undo_levels The current undo levels, if this is -1 custom undo/redo is disabled.
* @param {boolean} visual_aid Is visual aids enabled/disabled ex: dotted lines on tables.
* @param {boolean} any_selection Is there any selection at all or is there only a cursor.
*/
handleNodeChange : function(editor_id, node, undo_index, undo_levels, visual_aid, any_selection) {
},
/**
* Gets called when a TinyMCE editor instance gets filled with content on startup.
*
* @param {string} editor_id TinyMCE editor instance id that was filled with content.
* @param {HTMLElement} body HTML body element of editor instance.
* @param {HTMLDocument} doc HTML document instance.
*/
setupContent : function(editor_id, body, doc) {
},
/**
* Gets called when the contents of a TinyMCE area is modified, in other words when a undo level is
* added.
*
* @param {TinyMCE_Control} inst TinyMCE editor area control instance that got modified.
*/
onChange : function(inst) {
},
/**
* Gets called when TinyMCE handles events such as keydown, mousedown etc. TinyMCE
* doesn't listen on all types of events so custom event handling may be required for
* some purposes.
*
* @param {Event} e HTML editor event reference.
* @return true - pass to next handler in chain, false - stop chain execution
* @type boolean
*/
handleEvent : function(e) {
return true;
},
/**
* Gets called when HTML contents is inserted or retrived from a TinyMCE editor instance.
* The type parameter contains what type of event that was performed and what format the content is in.
* Possible valuses for type is get_from_editor, insert_to_editor, get_from_editor_dom, insert_to_editor_dom.
*
* @param {string} type Cleanup event type.
* @param {mixed} content Editor contents that gets inserted/extracted can be a string or DOM element.
* @param {TinyMCE_Control} inst TinyMCE editor instance control that performes the cleanup.
* @return New content or the input content depending on action.
* @type string
*/
cleanup : function(type, content, inst) {
return content;
},
// Private plugin internal methods
/**
* This is just a internal plugin method, prefix all internal methods with a _ character.
* The prefix is needed so they doesn't collide with future TinyMCE callback functions.
*
* @param {string} a Some arg1.
* @param {string} b Some arg2.
* @return Some return.
* @type string
*/
_someInternalFunction : function(a, b) {
return 1;
}
};
function TinyMCE_<span class="marked">yourplugin</span>_initInstance(inst) {
// Gets executed when a editor instance is initialized
}
function TinyMCE_<span class="marked">yourplugin</span>_getControlHTML(control_name) {
// Gets executed when a button is to be generated
}
function TinyMCE_<span class="marked">yourplugin</span>_handleNodeChange(editor_id, node, undo_index, undo_levels, visual_aid, any_selection) {
// Gets executed when the selection changes
}
function TinyMCE_<span class="marked">yourplugin</span>_execCommand(editor_id, element, command, user_interface, value) {
// Add your own custom commands here
return false;
}
function TinyMCE_<span class="marked">yourplugin</span>_cleanup(type, content) {
// Add your own custom cleanup here
return content;
}
// Adds the plugin class to the list of available TinyMCE plugins
tinyMCE.addPlugin("<span class="marked">someplugin</span>", TinyMCE_<span class="marked">SomePlugin</span>Plugin);
</pre>
</div>
</p>
<div class="separator"></div>
<h3>Creating popup HTML files</h3>
<p>
When creating a popup you need to include the &quot;tiny_mce_popup.js&quot; this enables you to retrive the tinyMCE global instance in all popup windows. All variables and language definitions gets replaced in the page when it loads. So language variables such as {$lang_something} can be places in the HTML code, if you need to get a language string in JavaScript simply use the tinyMCE.getLang function.
</p>
<h3>Example of simple popup file:</h3>
<div class="example">
<pre>
&lt;html&gt;
&lt;head&gt;
&lt;title&gt;{$lang_plugin_sample_title}&lt;/title&gt;
&lt;script language=&quot;javascript&quot; src=&quot;../../tiny_mce_popup.js&quot;&gt;&lt;/script&gt;
&lt;script language=&quot;javascript&quot;&gt;
// getWindowArg returns any arguments passed to the window
alert(tinyMCE.getWindowArg('some_arg'));
&lt;/script&gt;
&lt;body&gt;
&lt;strong&gt;{$lang_plugin_sample_desc}&lt;/strong&gt;
&lt;/body&gt;
</pre>
</div>
<div class="separator"></div>
<h3>The TinyMCE_&lt;plugin&gt;_initInstance function (Optional)</h3>
<p>
This function is called when a editor instance gets initialized.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Parameters</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>inst</strong></td>
<td>Reference to editor instance that was initialized.</td>
</tr>
</tbody>
</table>
</p>
<div class="separator"></div>
<h3>The TinyMCE_&lt;plugin&gt;_handleNodeChange function (Optional)</h3>
<p>
This function is called when the cursor/selection of a editor instance changes. Then the currenly selected/focused node is passed to this function. This can be useful when you want to change the UI depending on what the user has selected.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Parameters</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>editor_id</strong></td>
<td>Unique editor id, this is the same as the $editor_id variable in getEditorTemplate.</td>
</tr>
<tr>
<td><strong>node</strong></td>
<td>Reference to the Node element where the cursor is currenly located.</td>
</tr>
<tr>
<td><strong>undo_index</strong></td>
<td>Current undo index, this value is -1 if the custom undo/redo support is disabled.</td>
</tr>
<tr>
<td><strong>undo_levels</strong></td>
<td>Current number of undo levels, this value is -1 if the custom undo/redo support is disabled.</td>
</tr>
<tr>
<td><strong>visual_aid</strong></td>
<td>True/false state of visual aid/guidelines mode.</td>
</tr>
<tr>
<td><strong>any_selection</strong></td>
<td>Is any text or image selected.</td>
</tr>
</tbody>
</table>
</p>
<div class="separator"></div>
<h3>The TinyMCE_&lt;plugin&gt;_execCommand function (Optional)</h3>
<p>
This function is called when a command is executed for example &quot;bold&quot; or &quot;createlink&quot; this callback/plugin function may then intercept plugin specific commands and do custom logic. If this command returns true the command handling is terminated and the default tinyMCE command handeling never gets executed.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Parameters</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>editor_id</strong></td>
<td>Unique editor id, this is the same as the $editor_id variable in getEditorTemplate.</td>
</tr>
<tr>
<td><strong>element</strong></td>
<td>Reference to the document DOM root element of the editor instance.</td>
</tr>
<tr>
<td><strong>command</strong></td>
<td>Command that is to be executed for example &quot;myCommand&quot;.</td>
</tr>
<tr>
<td><strong>user_interface</strong></td>
<td>true/false option if a user insterace is to be used or not.</td>
</tr>
<tr>
<td><strong>value</strong></td>
<td>Custom data value passed with command, may be any data type.</td>
</tr>
</tbody>
</table>
</p>
<p>
Returns: <br />
true - Command intercepted and handled do not continue with command handling.<br />
false - Continue with execCommand handling, bubble.<br />
</p>
<div class="separator"></div>
<h3>The TinyMCE_&lt;plugin&gt;_getControlHTML(control_name) function (Optional)</h3>
<p>
This function is called when a editor needs to render a specific control/button. This function should return the HTML template of that control or a empty string if the control_name wasn't recognized. Notice the variable {$pluginurl} gets replaced with the URL prefix for the current plugin directory.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Parameters</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>control_name</strong></td>
<td>Control name to match against.</td>
</tr>
</tbody>
</table>
</p>
<p>
Returns: return the HTML template of that control or a empty string if the control_name wasn't recognized.
</p>
<h3>The TinyMCE_&lt;plugin&gt;_cleanup(type, content) function (Optional)</h3>
<p>
This function is called when a editor does cleanup of contents. This function has the same format as the one defined in the <a href="option_cleanup_callback.html">cleanup_callback</a> option.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Parameters</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>type</strong></td>
<td>Type of cleanup, insert_to_editor or get_from_editor. Insert to editor is passed when new content is placed within the editor and get_from_editor is when content is passed out from the editor. When dealing with the DOM representation of the same content insert_to_editor_dom or get_from_editor_dom gets passed as a type.</td>
</tr>
<tr>
<td><strong>content</strong></td>
<td>HTML contents to be cleaned up, this string contains the HTML code or with the _dom types the body DOM object gets passed instead.</td>
</tr>
</tbody>
</table>
</p>
<p>
Returns: return the cleaned up HTML code.
</p>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -11,55 +11,221 @@
</div>
<div class="content">
<h2>Creating your own Themes</h2>
<p>
Creating you own themes for the TinyMCE application is fairly easy if you know the basics of HTML, CSS and Javascript. The most easy way is to copy the &quot;default&quot; or the &quot;advanced&quot; template and rename it as your own name to for example &quot;mytheme&quot;. After you copy the template you need to change the red sections marked below to &quot;mytheme&quot; this is needed so that themes don't overlap in other words it gives the theme a unique name. Then just alter the HTML code as you see fit but notice some elements needs to be there so check the docs below on each function also remember that your custom themes needs to be located in tiny_mce's &quot;themes&quot; directory. If you want you may add theme specific options/settings but remember to namespace them in the following format &quot;theme_&lt;your theme&gt;_&lt;option&gt;&quot;.
Creating you own themes for the TinyMCE application is fairly easy if you know the basics of HTML, CSS and Javascript. The most easy way is to copy the &quot;simple&quot; or the &quot;advanced&quot; template and rename it as your own name to for example &quot;mytheme&quot;. After you copy the template you need to change the red sections marked below to &quot;mytheme&quot; this is needed so that themes don't overlap in other words it gives the theme a unique name. Then just alter the HTML code as you see fit but notice some elements needs to be there so check the docs below on each function also remember that your custom themes needs to be located in tiny_mce's &quot;themes&quot; directory. If you want you may add theme specific options/settings but remember to namespace them in the following format &quot;theme_&lt;your theme&gt;_&lt;option&gt;&quot;.
</p>
<div class="separator"></div>
<h3>Theme directory structure</h3>
<p>
The example below has three functions, these are explained in greater detail below.
<table class="btable">
<thead>
<th>File/Directory</td>
<th>Description</td>
</thead>
<tbody>
<tr><td>css</td><td>Theme specific CSS files</td></tr>
<tr><td>docs</td><td>Theme specific documentation</td></tr>
<tr><td>images</td><td>Theme specific images</td></tr>
<tr><td>jscripts</td><td>Theme specific jscripts for HTML dialogs</td></tr>
<tr><td>langs</td><td>Theme specific language files</td></tr>
<tr><td>editor_template.js</td><td>Editor theme template file (compressed).</td></tr>
<tr><td>editor_template_src.js</td><td>Editor theme template file (source).</td></tr>
<tr><td>somedialog.htm</td><td>Theme specific dialog HTML file.</td></tr>
</table>
</p>
<div class="separator"></div>
<h3>Theme example source</h3>
<p>
The example below shows a simple empty theme and all possible callbacks.
</p>
<p>
<div class="example">
<pre>
function TinyMCE_<span class="marked">default</span>_getEditorTemplate(settings) {
var template = new Array();
var TinyMCE_<span class="marked">SomeName</span>Theme = {
/**
* Returns information about the theme as a name/value array.
* The current keys are longname, author, authorurl, infourl and version.
*
* @returns Name/value array containing information about the theme.
* @type Array
*/
getInfo : function() {
return {
longname : 'Your Theme',
author : 'Your name',
authorurl : 'http://www.yoursite.com',
infourl : 'http://www.yoursite.com/docs/template.html',
version : "1.0"
};
},
template['html'] = '&lt;Some HTML&gt;';
template['delta_width'] = 0;
template['delta_height'] = -40;
/**
* Gets executed when a TinyMCE editor instance is initialized.
*
* @param {TinyMCE_Control} Initialized TinyMCE editor control instance.
*/
initInstance : function(inst) {
// You can take out theme specific parameters
alert("Initialization parameter:" + tinyMCE.getParam("<span class="marked">somename</span>_someparam", false));
return template;
}
// Register custom keyboard shortcut
inst.addShortcut('ctrl', 't', 'lang_<span class="marked">somename</span>_desc', 'mceSomeCommand');
},
function TinyMCE_<span class="marked">default</span>_getInsertLinkTemplate(settings) {
var template = new Array();
/**
* Returns the HTML code for a specific control or empty string if this theme doesn't have that control.
* A control can be a button, select list or any other HTML item to present in the TinyMCE user interface.
* The variable {$editor_id} will be replaced with the current editor instance id and {$themeurl} will be replaced
* with the URL of the theme. Language variables such as {$lang_somekey} will also be replaced with contents from
* the language packs.
*
* @param {string} cn Editor control/button name to get HTML for.
* @return HTML code for a specific control or empty string.
* @type string
*/
getControlHTML : function(cn) {
switch (cn) {
case "<span class="marked">SomeControl</span>":
return tinyMCE.getButtonHTML(cn, 'lang_<span class="marked">sometheme</span>_<span class="marked">button</span>_desc', '{$themeurl}/images/<span class="marked">someimage</span>.gif', '<span class="marked">mceSomeCommand</span>');
}
template['file'] = 'link.htm';
template['width'] = 320;
template['height'] = 130;
return "";
},
return template;
}
/**
* Returns the HTML code that should be inserted for a specific editor instance.
* This function should return a name/value array with three items html, delta_width, delta_height.
* The html item should contain the HTML code to insert as a editor instance.
* The variable {$editor_id} will be replaced with the current editor instance id and {$themeurl} will be replaced
* with the URL of the theme. Language variables such as {$lang_somekey} will also be replaced with contents from
* the language packs. Any element with the id {$editor_id} will be replaced with the editor iframe element.
* The {$width} and {$height} variables will be replaced with the editors outside dimension values.
* The delta_width/height is the relative width/height in pixels to add or remove from the iframe dimensions.
*
* @param {Array} settings Name/Value array instance settings.
* @param {string} editor_id TinMYCE editor control instance id.
* @return Name/Value array of editor template data.
* @type Array
*/
getEditorTemplate : function(settings, editor_id) {
var html = "";
function TinyMCE_<span class="marked">default</span>_getInsertImageTemplate(settings) {
var template = new Array();
// Build toolbar and editor instance
html += "..";
template['file'] = 'image.htm';
template['width'] = 320;
template['height'] = 130;
return {
html : html,
delta_width : 0,
delta_height : 0
};
},
return template;
}
/**
* Executes a specific command, this function handles theme commands.
*
* @param {string} editor_id TinyMCE editor instance id that issued the command.
* @param {HTMLElement} element Body or root element for the editor instance.
* @param {string} command Command name to be executed.
* @param {string} user_interface True/false if a user interface should be presented.
* @param {mixed} value Custom value argument, can be anything.
* @return true/false if the command was executed by this theme or not.
* @type
*/
execCommand : function(editor_id, element, command, user_interface, value) {
// Handle commands
switch (command) {
// Remember to have the "mce" prefix for commands so they don't intersect with built in ones in the browser.
case "mce<span class="marked">SomeCommand</span>":
// Do your custom command logic here.
function TinyMCE_<span class="marked">default</span>_handleNodeChange(editor_id, node) {
// Check what happend
}
return true;
}
function TinyMCE_<span class="marked">default</span>_execCommand(editor_id, element, command, user_interface, value) {
// Your custom command logic
return false;
}
// Pass to next handler in chain
return false;
},
/**
* Gets called ones the cursor/selection in a TinyMCE instance changes. This is useful to enable/disable
* button controls depending on where the user are and what they have selected. This method gets executed
* alot and should be as performance tuned as possible.
*
* @param {string} editor_id TinyMCE editor instance id that was changed.
* @param {HTMLNode} node Current node location, where the cursor is in the DOM tree.
* @param {int} undo_index The current undo index, if this is -1 custom undo/redo is disabled.
* @param {int} undo_levels The current undo levels, if this is -1 custom undo/redo is disabled.
* @param {boolean} visual_aid Is visual aids enabled/disabled ex: dotted lines on tables.
* @param {boolean} any_selection Is there any selection at all or is there only a cursor.
*/
handleNodeChange : function(editor_id, node, undo_index, undo_levels, visual_aid, any_selection) {
},
/**
* Gets called when a TinyMCE editor instance gets filled with content on startup.
*
* @param {string} editor_id TinyMCE editor instance id that was filled with content.
* @param {HTMLElement} body HTML body element of editor instance.
* @param {HTMLDocument} doc HTML document instance.
*/
setupContent : function(editor_id, body, doc) {
},
/**
* Gets called when the contents of a TinyMCE area is modified, in other words when a undo level is
* added.
*
* @param {TinyMCE_Control} inst TinyMCE editor area control instance that got modified.
*/
onChange : function(inst) {
},
/**
* Gets called when TinyMCE handles events such as keydown, mousedown etc. TinyMCE
* doesn't listen on all types of events so custom event handling may be required for
* some purposes.
*
* @param {Event} e HTML editor event reference.
* @return true - pass to next handler in chain, false - stop chain execution
* @type boolean
*/
handleEvent : function(e) {
return true;
},
/**
* Gets called when HTML contents is inserted or retrived from a TinyMCE editor instance.
* The type parameter contains what type of event that was performed and what format the content is in.
* Possible valuses for type is get_from_editor, insert_to_editor, get_from_editor_dom, insert_to_editor_dom.
*
* @param {string} type Cleanup event type.
* @param {mixed} content Editor contents that gets inserted/extracted can be a string or DOM element.
* @param {TinyMCE_Control} inst TinyMCE editor instance control that performes the cleanup.
* @return New content or the input content depending on action.
* @type string
*/
cleanup : function(type, content, inst) {
return content;
},
// Private theme internal methods
/**
* This is just a internal theme method, prefix all internal methods with a _ character.
* The prefix is needed so they doesn't collide with future TinyMCE callback functions.
*
* @param {string} a Some arg1.
* @param {string} b Some arg2.
* @return Some return.
* @type string
*/
_someInternalFunction : function(a, b) {
return 1;
}
};
// Adds the theme class to the list of available TinyMCE themes
tinyMCE.addTheme("<span class="marked">sometheme</span>", TinyMCE_<span class="marked">SomeTheme</span>Theme);
</pre>
</div>
</p>
@ -74,348 +240,21 @@ When creating a popup you need to include the &quot;tiny_mce_popup.js&quot; this
<pre>
&lt;html&gt;
&lt;head&gt;
&lt;title&gt;{$lang_plugin_sample_title}&lt;/title&gt;
&lt;title&gt;{$lang_theme_sample_title}&lt;/title&gt;
&lt;script language=&quot;javascript&quot; src=&quot;../../tiny_mce_popup.js&quot;&gt;&lt;/script&gt;
&lt;script language=&quot;javascript&quot;&gt;
// getWindowArg returns any arguments passed to the window
alert(tinyMCE.getWindowArg('some_arg'));
&lt;/script&gt;
&lt;body&gt;
&lt;strong&gt;{$lang_plugin_sample_desc}&lt;/strong&gt;
&lt;strong&gt;{$lang_theme_sample_desc}&lt;/strong&gt;
&lt;/body&gt;
</pre>
</div>
<div class="separator"></div>
<h3>The TinyMCE_&lt;theme&gt;_getEditorTemplate(settings) function</h3>
<p>
This function is responsible for the layout of the editor instance within the page it should return a name/value based array with some specific names. These are explained below, notice names included in [] characters are optional. The settings parameter to this function is a name/value array containing tinyMCE:s settings/options.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Template data</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>html</strong></td>
<td>HTML template data, this value should contain all the HTML code needed to render the editor. Notice: {$&lt;variable&gt;} are replaces with values when used. More about these specific values later on.</td>
</tr>
<tr>
<td><strong>[delta_width]</strong></td>
<td>Delta width, this value should contain the relative width needed by the UI. For example if a toolbar takes 20 pixels this value should be -20. This is so the editor gets the same size as the element that are replaced.</td>
</tr>
<tr>
<td><strong>[delta_height]</strong></td>
<td>Delta height, this value should contain the relative width needed by the UI. For example if a toolbar takes 40 pixels this value should be -40. This is so the editor gets the same size as the element that are replaced.</td>
</tr>
</tbody>
</table>
</p>
<p>
Variables within the &quot;html&quot; value above are replaced with internal TinyMCE values. There are two types of variables one is the ones starting with the &quot;lang_&quot; prefix, these are replaced with the matching names in the language packs. So for example &lt;b&gt;{$lang_test}&lt;/b&gt; gets replaces with the &quot;tinyMCELang['lang_test']&quot; variable and the output is then &lt;b&gt;Test&lt;/b&gt;. The other variables are passed expicilty for the template used and these are listed below. Notice: Variables within [] characters are optional.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Variables</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>editor_id</strong></td>
<td>This is the editor instance id and it should be placed in ID attribute of the IFRAME element that must be included in the template.</td>
</tr>
<tr>
<td><strong>[default_document]</strong></td>
<td>This will be replaced with a blank html page, this is added for MSIE security issues and should be placed in the SRC attribute of the IFRAME within the template.</td>
</tr>
<tr>
<td><strong>[area_width]</strong></td>
<td>Width of IFRAME area in pixels.</td>
</tr>
<tr>
<td><strong>[area_height]</strong></td>
<td>Height of IFRAME area in pixels.</td>
</tr>
<tr>
<td><strong>[width]</strong></td>
<td>Width of the whole editor area in pixels.</td>
</tr>
<tr>
<td><strong>[height]</strong></td>
<td>Height of the whole editor area in pixels.</td>
</tr>
<tr>
<td><strong>[themeurl]</strong></td>
<td>URL to theme location.</td>
</tr>
</tbody>
</table>
</p>
<p>
Notice: There are two javascript function that can be called from this template these are tinyMCE.execCommand that executes commans on the currenly selected editor area and the tinyMCE.switchClass that switches the CSS class of the element specified. For more details of commands available by execCommand check the Mozilla midas specification and the TinyMCE specific commands.
</p>
<div class="separator"></div>
<h3>The TinyMCE_&lt;theme&gt;_getInsertLinkTemplate(settings) function</h3>
<p>
This function is responsible for the layout of the insert link popup window and it should return a name/value based array with some specific names. These are explained below, notice names included in [] characters are optional. The settings parameter to this function is a name/value array containing tinyMCE:s settings/options.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Template data</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>html</strong></td>
<td>HTML template data, this value should contain all the HTML code needed to render the link dialog. Notice: {$&lt;variable&gt;} are replaces with values when used. More about these specific values later on. This parameter is not needed if the &quot;file&quot; param is assigned.</td>
</tr>
<tr>
<td><strong>file</strong></td>
<td>Name of external template file to use, this may even be logic pages like .php,.asp,.jsp etc.</td>
</tr>
<tr>
<td><strong>[width]</strong></td>
<td>Width of popup window in pixels. Default is 320.</td>
</tr>
<tr>
<td><strong>[height]</strong></td>
<td>Height of popup window in pixels. Default is 200.</td>
</tr>
</tbody>
</table>
</p>
<p>
Variables within the &quot;html&quot; value above are replaced with internal TinyMCE values. There are two types of variables one is the ones starting with the &quot;lang_&quot; prefix, these are replaced with the matching names in the language packs. So for example &lt;b&gt;{$lang_test}&lt;/b&gt; gets replaces with the &quot;tinyMCELang['lang_test']&quot; variable and the output is then &lt;b&gt;Test&lt;/b&gt;. The other variables are passed expicilty for the template used and these are listed below. Notice: Variables within [] characters are optional.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Variables/Window arguments:</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>[href]</strong></td>
<td>This variable gets replaced with the &quot;href&quot; attribute value of the selected link if one is selected.</td>
</tr>
<tr>
<td><strong>[target]</strong></td>
<td>This variable gets replaced with the &quot;target&quot; attribute value of the selected link if one is selected.</td>
</tr>
<tr>
<td><strong>[css]</strong></td>
<td>Theme popup css location.</td>
</tr>
</tbody>
</table>
</p>
<p>
Notice: There are a javascript function that can be called from this template &quot;window.opener.tinyMCE.insertLink(href, target)&quot; this inserts the link into the currently selected editor and should be called when for example a insert button is pressed.
</p>
<div class="separator"></div>
<h3>The TinyMCE_&lt;theme&gt;_getInsertImageTemplate(settings) function</h3>
<p>
This function is responsible for the layout of the insert image dialog, it should return a name/value based array with some specific names. These are explained below, notice names included in [] characters are optional. The settings parameter to this function is a name/value array containing tinyMCE:s settings/options.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Template data</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>html</strong></td>
<td>HTML template data, this value should contain all the HTML code needed to render the image dialog. Notice: {$&lt;variable&gt;} are replaces with values when used. More about these specific values later on. This parameter is not needed if the &quot;file&quot; param is assigned.</td>
</tr>
<tr>
<td><strong>[width]</strong></td>
<td>Width of popup window in pixels. Default is 320.</td>
</tr>
<tr>
<td><strong>[height]</strong></td>
<td>Height of popup window in pixels. Default is 200.</td>
</tr>
</tbody>
</table>
</p>
<p>
Variables within the &quot;html&quot; value above are replaced with internal TinyMCE values. There are two types of variables one is the ones starting with the &quot;lang_&quot; prefix, these are replaced with the matchin names in the language packs. So for example &lt;b&gt;{$lang_test}&lt;/b&gt; gets replaces with the &quot;tinyMCELang['lang_test']&quot; variable and the output is then &lt;b&gt;Test&lt;/b&gt;. The other variables are passed expicilty for the template used and these are listed below. Notice: Variables within [] characters are optional.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Variables/Window arguments</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>[src]</strong></td>
<td>This variable gets replaced with the &quot;src&quot; attribute value of the selected link if one is selected.</td>
</tr>
<tr>
<td><strong>[alt]</strong></td>
<td>This variable gets replaced with the &quot;alt&quot; attribute value of the selected link if one is selected.</td>
</tr>
<tr>
<td><strong>[border]</strong></td>
<td>This variable gets replaced with the &quot;border&quot; attribute value of the selected link if one is selected.</td>
</tr>
<tr>
<td><strong>[hspace]</strong></td>
<td>This variable gets replaced with the &quot;hspace&quot; attribute value of the selected link if one is selected.</td>
</tr>
<tr>
<td><strong>[vspace]</strong></td>
<td>This variable gets replaced with the &quot;vspace&quot; attribute value of the selected link if one is selected.</td>
</tr>
<tr>
<td><strong>[width]</strong></td>
<td>This variable gets replaced with the &quot;width&quot; attribute value of the selected link if one is selected.</td>
</tr>
<tr>
<td><strong>[height]</strong></td>
<td>This variable gets replaced with the &quot;height&quot; attribute value of the selected link if one is selected.</td>
</tr>
<tr>
<td><strong>[align]</strong></td>
<td>This variable gets replaced with the &quot;align&quot; attribute value of the selected link if one is selected.</td>
</tr>
<tr>
<td><strong>[css]</strong></td>
<td>Theme popup css location.</td>
</tr>
</tbody>
</table>
</p>
<p>
Notice: There are a javascript function that can be called from this template &quot;window.opener.tinyMCE.insertImage(src, alt, border, hspace, vspace, width, height, align)&quot; this inserts the image into the currently selected editor and should be called when for example a insert button is pressed.
</p>
<div class="separator"></div>
<h3>The TinyMCE_&lt;theme&gt;_handleNodeChange function (Optional)</h3>
<p>
This function is called when the cursor/selection of a editor instance changes. Then the currenly selected/focused node is passed to this function. This can be useful when you want to change the UI depending on what the user has selected.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Parameters</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>editor_id</strong></td>
<td>Unique editor id, this is the same as the $editor_id variable in getEditorTemplate.</td>
</tr>
<tr>
<td><strong>node</strong></td>
<td>Reference to the Node element where the cursor is currenly located.</td>
</tr>
<tr>
<td><strong>undo_index</strong></td>
<td>Current undo index, this value is -1 if the custom undo/redo support is disabled.</td>
</tr>
<tr>
<td><strong>undo_levels</strong></td>
<td>Current number of undo levels, this value is -1 if the custom undo/redo support is disabled.</td>
</tr>
<tr>
<td><strong>visual_aid</strong></td>
<td>True/false state of visual aid/guidelines mode.</td>
</tr>
<tr>
<td><strong>any_selection</strong></td>
<td>Is any text or image selected.</td>
</tr>
</tbody>
</table>
</p>
<div class="separator"></div>
<h3>The TinyMCE_&lt;theme&gt;_execCommand function (Optional)</h3>
<p>
This function is called when a command is executed for example &quot;bold&quot; or &quot;createlink&quot; this callback/theme function may then intercept theme specific commands and do custom logic. If this command returns true the command handling is terminated and the default tinyMCE command handeling never gets executed.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Parameters</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>editor_id</strong></td>
<td>Unique editor id, this is the same as the $editor_id variable in getEditorTemplate.</td>
</tr>
<tr>
<td><strong>element</strong></td>
<td>Reference to the document DOM root element of the editor instance.</td>
</tr>
<tr>
<td><strong>command</strong></td>
<td>Command that is to be executed for example &quot;myCommand&quot;.</td>
</tr>
<tr>
<td><strong>user_interface</strong></td>
<td>true/false option if a user insterace is to be used or not.</td>
</tr>
<tr>
<td><strong>value</strong></td>
<td>Custom data value passed with command, may be any data type.</td>
</tr>
</tbody>
</table>
</p>
<p>
Returns: <br />
true - Command intercepted and handled do not continue with command handling.<br />
false - Continue with execCommand handling, bubble.<br />
</p>
<div class="separator"></div>
<h3>The TinyMCE_&lt;theme&gt;_getControlHTML(control_name) function (Optional)</h3>
<p>
This function is called when a editor needs to render a specific control/button. This function should return the HTML template of that control or a empty string if the control_name wasn't recognized. Notice the variable {$pluginurl} gets replaced with the URL prefix for the current plugin directory.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead>
<tr>
<td colspan="2">Parameters</td>
</tr>
</thead>
<tbody>
<tr>
<td><strong>control_name</strong></td>
<td>Control name to match against.</td>
</tr>
</tbody>
</table>
</p>
<p>
Returns: return the HTML template of that control or a empty string if the control_name wasn't recognized.
</p>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -12,9 +12,27 @@
<div class="content">
<p>Here are some common answers to common questions. If you need more help you can always visit the <a href="http://tinymce.moxiecode.com/">TinyMCE Forum</a> on the TinyMCE web site.</p>
<p>
<ul class="plist">
<li><a href="#broken">TinyMCE is broken, what should I do?</a></li>
<li><a href="#paths">Why is my paths incorrect, I want absolute/relative URLs?</a></li>
<li><a href="#strip">Why does TinyMCE strip aways attributes or tags from my source?</a></li>
<li><a href="#font">How do I change the default font size/face color of the editor?</a></li>
<li><a href="#remove">How do I remove/add buttons/controls to TinyMCE?</a></li>
<li><a href="#quotes">Why does my HTML output include lots of \&quot; like &lt;a href=\&quot;mylink.htm\&quot;&gt;link&lt;/a&gt;?</a></li>
<li><a href="#load">TinyMCE takes ages to load, is there a way to make it load quicker?</a></li>
<li><a href="#hidden">TinyMCE stops working when placed in tabs or hidden divs?</a></li>
<li><a href="#commercial">Can I use TinyMCE in my commercial application?</a></li>
<li><a href="#commercial2">Are there any restrictions to using TinyMCE in my commercial application?</a></li>
<li><a href="#lgpl">I don't like LGPL, is there a commercial license available for me?</a></li>
<li><a href="#support">Do you provide support?</a></li>
<li><a href="#who">Who made this software?</a></li>
</ul>
</p>
<div class="separator"></div>
<a name="broken"></a>
<h2>TinyMCE is broken, what should I do?</h2>
<div class="section">
<p>There are a few things you should check before posting questions about your problem at the forum or sourceforge.</p>
@ -32,6 +50,63 @@
<div class="separator"></div>
<a name="paths"></a>
<h2>Why is my paths incorrect, I want absolute/relative URLs?</h2>
<div class="section">
<p>
These are the diffrent configuration scenarios for URLs within TinyMCE:
<table class="btable">
<thead>
<th>Output</th>
<th>Config</th>
<th>Description</th>
</thead>
<tbody>
<tr>
<td><strong>http://www.site.com/path1/path2/file.htm</strong> will be converted to <strong>path2/file.htm</strong></td>
<td nowrap="nowrap">
<a href="option_relative_urls.html">relative_urls</a> : true,<br />
<a href="option_document_base_url.html">document_base_url</a> : &quot;http://www.site.com/path1/&quot;<br />
</td>
<td>This will convert all URLs within the same domain to relative URLs.<br /> <strong>The URLs will be relative from the <a href="option_document_base_url.html">document_base_url</a></strong>.</td>
</tr>
<tr>
<td><strong>path2/file.htm</strong> will be converted to <strong>/path1/path2/file.htm</strong></td>
<td nowrap="nowrap">
<a href="option_relative_urls.html">relative_urls</a> : false,<br />
<a href="option_remove_script_host.html">remove_script_host</a> : true,<br />
<a href="option_document_base_url.html">document_base_url</a> : &quot;http://www.site.com/path1/&quot;<br />
</td>
<td>This will convert all relative URLs to absolute URLs.<br /> <strong>The URLs will be absolute based on the <a href="option_document_base_url.html">document_base_url</a></strong>.</td>
</tr>
<tr>
<td><strong>path2/file.htm</strong> will be converted to <strong>http://www.site.com/path1/path2/file.htm</strong></td>
<td nowrap="nowrap">
<a href="option_relative_urls.html">relative_urls</a> : false,<br />
<a href="option_remove_script_host.html">remove_script_host</a> : false,<br />
<a href="option_document_base_url.html">document_base_url</a> : &quot;http://www.site.com/path1/&quot;<br />
</td>
<td>This will convert all relative URLs to absolute URLs.<br /> <strong>The URLs will be absolute based on the <a href="option_document_base_url.html">document_base_url</a></strong>.</td>
</tr>
<tr>
<td><strong>path2/file.htm</strong> or <strong>http://www.site.com/path1/path2/file.htm</strong> will not be converted at all.</td>
<td nowrap="nowrap">
<a href="option_convert_urls.html">convert_urls</a> : false<br />
</td>
<td>This option will preserve the URLs as they are in a separate attribute while editing, <strong>since browsers tend to auto convert URLs</strong>.</td>
</tr>
</tbody>
</table>
</p>
</div>
<div class="separator"></div>
<a name="strip"></a>
<h2>Why does TinyMCE strip aways attributes or tags from my source?</h2>
<div class="section">
<p>You need to check out the &quot;<a href="option_valid_elements.html">valid_elements</a>&quot; and &quot;<a href="option_extended_valid_elements.html">extended_valid_elements</a>&quot; option in the configuration. By default, TinyMCE only allows certain tags and attributes. TinyMCE also tries to follow the XHTML specification as much as possible (and so should you), this can cause some unexpected source changes, there are however configuration options to battle this issue, study the configuration options in details.</p>
@ -39,6 +114,7 @@
<div class="separator"></div>
<a name="font"></a>
<h2>How do I change the default font size/face color of the editor?</h2>
<div class="section">
<p>
@ -48,6 +124,7 @@
<div class="separator"></div>
<a name="remove"></a>
<h2>How do I remove/add buttons/controls to TinyMCE?</h2>
<div class="section">
<p>
@ -57,15 +134,7 @@
<div class="separator"></div>
<h2>TinyMCE changes the path of my images, why?</h2>
<div class="section">
<p>
Different browsers handles images differently, TinyMCE tries to compensate for this and has its own convert URL functions. You can control the behavior through the configuration, check out the URL section in the <a href="reference_configuration.html">configuration</a> options.
</p>
</div>
<div class="separator"></div>
<a name="quotes"></a>
<h2>Why does my HTML output include lots of \&quot; like &lt;a href=\&quot;mylink.htm\&quot;&gt;link&lt;/a&gt;?</h2>
<div class="section">
<p>This is probably because you are using PHP and it has a feature that's called magic quotes that is enabled by default. You can read more about this at the <a href="http://se2.php.net/magic_quotes/">PHP website</a> or use the <a href="http://www.php.net/manual/en/function.stripslashes.php">stripslashes</a> function.</p>
@ -73,6 +142,7 @@
<div class="separator"></div>
<a name="load"></a>
<h2>TinyMCE takes ages to load, is there a way to make it load quicker?</h2>
<div class="section">
<p>
@ -82,13 +152,7 @@
<div class="separator"></div>
<h2>Can I use TinyMCE in my commercial application?</h2>
<div class="section">
<p>Yes you can, the LGPL license is a Free Software License. You can read the whole license <a href="license.html">here</a> or visit Free Software Foundation web site <a href="http://www.fsf.org/" target="_blank">here</a></p>
</div>
<div class="separator"></div>
<a name="hidden"></a>
<h2>TinyMCE stops working when placed in tabs or hidden divs?</h2>
<div class="section">
<p>Since Gecko based browsers Mozilla/Firefox has a bug where it looses designMode on iframes that are hidden a special option is needed that re-enables the design mode when reappearing after being hidden. Enable this option to resolve the issue: &quot;<a href="option_auto_reset_designmode.html">auto_reset_designmode</a>&quot;.</p>
@ -96,18 +160,28 @@
<div class="separator"></div>
<a name="commercial"></a>
<h2>Can I use TinyMCE in my commercial application?</h2>
<div class="section">
<p>Yes you can, the LGPL license is a Free Software License. You can read the whole license <a href="license.html">here</a> or visit Free Software Foundation web site <a href="http://www.fsf.org/" target="_blank">here</a></p>
</div>
<div class="separator"></div>
<a name="commercial2"></a>
<h2>Are there any restrictions to using TinyMCE in my commercial application?</h2>
<div class="section">
<p>
Yes, all copyright notices must be intact. Moxiecode Systems are still the copyright holders of the source code, so you can not use the code for other applications. Any modifications or add-ons you make to the source has to be contributes back to the TinyMCE community.
</p>
<p>
If you start to make a lot of revenue from using TinyMCE, please remember the time and dedication that has been put into this by other developers, respect this and give credit to those who deserve it. We also accept donations.
If you start to make a lot of revenue from using TinyMCE, please remember the time and dedication that has been put into this by other developers, respect this and give credit to those who deserve it.
</p>
</div>
<div class="separator"></div>
<a name="lgpl"></a>
<h2>I don't like LGPL, is there a commercial license available for me?</h2>
<div class="section">
<p>
@ -117,6 +191,7 @@
<div class="separator"></div>
<a name="support"></a>
<h2>Do you provide support?</h2>
<div class="section">
<p>
@ -126,6 +201,7 @@
<div class="separator"></div>
<a name="who"></a>
<h2>Who made this software?</h2>
<div class="section">
<p>
@ -136,7 +212,7 @@
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -36,7 +36,7 @@
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -27,7 +27,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -28,7 +28,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -44,7 +44,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -35,7 +35,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -113,7 +113,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -457,7 +457,7 @@ DAMAGES.
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -12,7 +12,7 @@
<div class="content">
<p>
This option enables you to turn on/off the build in cleanup functionality. TinyMCE is equipped with powerful cleanup functionality that enables you to specify what elements and attributes are allowed and how HTML contents should be generated. This option is set to true by default, but if you want to disable it you may set it to false. <strong>Notice: It's not recommended to disable this feature.</strong>
This option enables you to turn on/off the built in cleanup functionality. TinyMCE is equipped with powerful cleanup functionality that enables you to specify what elements and attributes are allowed and how HTML contents should be generated. This option is set to true by default, but if you want to disable it you may set it to false. <strong>Notice: It's not recommended to disable this feature.</strong>
</p>
<div class="separator"></div>
@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -64,7 +64,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -12,7 +12,7 @@
<div class="content">
<p>
This option enables you to specify a custom CSS file that extends the theme content CSS. This CSS file is the one used within the editor (the editable area). The default location of this CSS file is within the current theme.
This option enables you to specify a custom CSS file that extends the theme content CSS. This CSS file is the one used within the editor (the editable area). The default location of this CSS file is within the current theme. This option can also be a comma separated list of URLs.
</p>
<div class="separator"></div>
@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -11,7 +11,7 @@
</div>
<div class="content">
<p>This option enables you to control if TinyMCE is to be clever and restore urls to their original values. URLs are auto converted/messed up by default since the build in browser logic works this way, there is no way to get the real URL unless you store it away. If you set this option to false it will try to keep these URLs intact. This option is set to true by default that means URLs will be forced absolute or relative depending on the state of <a href="option_relative_urls.html">relative_urls</a>.</p>
<p>This option enables you to control if TinyMCE is to be clever and restore urls to their original values. URLs are auto converted/messed up by default since the built in browser logic works this way, there is no way to get the real URL unless you store it away. If you set this option to false it will try to keep these URLs intact. This option is set to true by default that means URLs will be forced absolute or relative depending on the state of <a href="option_relative_urls.html">relative_urls</a>.</p>
<div class="separator"></div>
@ -28,7 +28,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -27,7 +27,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -28,7 +28,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -41,7 +41,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -41,7 +41,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -43,7 +43,7 @@ var tinyMCEImageList = new Array(
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -44,7 +44,7 @@ var tinyMCELinkList = new Array(
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -35,7 +35,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -27,7 +27,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -27,7 +27,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -12,7 +12,7 @@
<div class="content">
<p>
If you set this option to true, TinyMCE will force BR elements on newlines instead of inserting paragraphs. This option is set to false by default since paragraphs is a much better concept. You can style P elements to be one row by adding p { margin: 0px; padding: 0px; } to your CSS, P tags where invented for a reason and should be used. <strong>BR elements should only be used when you really have to (mostly never)</strong>.
If you set this option to true, TinyMCE will force BR elements on newlines instead of inserting paragraphs. This option is set to false by default since paragraphs is a much better concept. You can style P elements to be one row by adding p { margin: 0; padding: 0; } to your CSS, P tags where invented for a reason and should be used. <strong>BR elements should only be used when you really have to (mostly never)</strong>.
</p>
<div class="separator"></div>
@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -27,7 +27,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -34,7 +34,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -7,12 +7,15 @@
<body>
<div class="header">
<h1>Option: insertimage_callback</h1>
<h1><span class="marked">(deprecated)</span> Option: insertimage_callback</h1>
</div>
<div class="content">
<p>
This option enables you to override the build in functionality for inserting images. This option should contain a function name to be executed when a new image is inserted into TinyMCE. The format of this callback function is: insertImage(src, alt, border, hspace, vspace, width, height, align, title, onmouseover, onmouseout, action). Where most of these options are self explained the action can be &quot;update&quot; or &quot;insert&quot; depending on what operation type. This function should return an array with the same values as the incomming parameters, the example below describes how this is done. This option is set to a internal TinyMCE function by default.
This callback was removed in 2.0.3, use <a href="option_execcommand_callback.html">execcommand_callback</a> instead this also enables you to override other things than the image and link dialogs.
</p>
<p>
This option enables you to override the built in functionality for inserting images. This option should contain a function name to be executed when a new image is inserted into TinyMCE. The format of this callback function is: insertImage(src, alt, border, hspace, vspace, width, height, align, title, onmouseover, onmouseout, action). Where most of these options are self explained the action can be &quot;update&quot; or &quot;insert&quot; depending on what operation type. This function should return an array with the same values as the incomming parameters, the example below describes how this is done. This option is set to a internal TinyMCE function by default.
</p>
<div class="separator"></div>
@ -49,7 +52,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -7,12 +7,15 @@
<body>
<div class="header">
<h1>Option: insertlink_callback</h1>
<h1><span class="marked">(deprecated)</span> Option: insertlink_callback</h1>
</div>
<div class="content">
<p>
This option enables you to override the build in functionality for inserting links. This option should contain a function name to be executed when a new link is inserted into TinyMCE. The format of this callback function is: insertLink(href, target, title, onclick, action). Where most of these options are self explained the action can be &quot;update&quot; or &quot;insert&quot; depending on what operation type. This function should return an array with the same values as the incomming parameters, the example below describes how this is done. This option is set to a internal TinyMCE function by default.
This callback was removed in 2.0.3, use <a href="option_execcommand_callback.html">execcommand_callback</a> instead this also enables you to override other things than the image and link dialogs.
</p>
<p>
This option enables you to override the built in functionality for inserting links. This option should contain a function name to be executed when a new link is inserted into TinyMCE. The format of this callback function is: insertLink(href, target, title, onclick, action). Where most of these options are self explained the action can be &quot;update&quot; or &quot;insert&quot; depending on what operation type. This function should return an array with the same values as the incomming parameters, the example below describes how this is done. This option is set to a internal TinyMCE function by default.
</p>
<div class="separator"></div>
@ -42,7 +45,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -34,7 +34,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -29,7 +29,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -46,7 +46,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -35,7 +35,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -34,7 +34,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -14,6 +14,9 @@
<p>
This option should contain a comma separated list of plugins. Plugins are loaded from the &quot;tinymce/jscripts/tiny_mce/plugins&quot; directory and the plugin name matches the name of the directory. TinyMCE is shipped with some core plugins these are described in greater detail in the <a href="reference_plugins.html">Plugins reference</a>.
</p>
<p>
TinyMCE also supports the ability to have plugins added from a external resource, these plugins needs to be self registrering and loaded after the tinyMCE.init call. You should also prefix these plugins with a &quot;-&quot; character so that TinyMCE doesn't try to load it from the TinyMCE plugins directory.
</p>
<p>
There are many third party plugins for TinyMCE some of these may be found under &quot;Plugins&quot; at <a href="http://sourceforge.net/projects/tinymce/">SourceForge</a> and if you have developed one of your own please contribute it to this project by uploading it to SourceForge.
@ -26,7 +29,7 @@
<pre>
tinyMCE.init({
...
<strong>plugins : "table,contextmenu,paste"</strong>
<strong>plugins : &quot;table,contextmenu,paste,-externalplugin&quot;</strong>
});
</pre>
</div>
@ -34,7 +37,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -28,7 +28,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -29,7 +29,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -12,7 +12,7 @@
<div class="content">
<p>
This option enables you to add custom logic to be executed when the contents is extracted/saved. This custom logic can then modify the contents before it's submited to a serverside page. This can be useful if you want to do your own regexp cleanups and so forth. The format of this function is: saveContent(element_id, html, body). Where element id is the form element/div id of the editor and HTML is the HTML contents after the build in cleanup process has executed. This function should return the new HTML contents.
This option enables you to add custom logic to be executed when the contents is extracted/saved. This custom logic can then modify the contents before it's submited to a serverside page. This can be useful if you want to do your own regexp cleanups and so forth. The format of this function is: saveContent(element_id, html, body). Where element id is the form element/div id of the editor and HTML is the HTML contents after the built in cleanup process has executed. This function should return the new HTML contents.
</p>
<div class="separator"></div>
@ -37,7 +37,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -35,7 +35,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -39,7 +39,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -12,7 +12,7 @@
<div class="content">
<p>
This option enables you to specify what theme to use when rendering the TinyMCE WYSIWYG editor instances. This name matches the directories located in &quot;tinymce/jscripts/tiny_mce/themes&quot;. The default value of this option is &quot;advanced&quot;. TinyMCE has three build in themes and these are described in greater detail below.
This option enables you to specify what theme to use when rendering the TinyMCE WYSIWYG editor instances. This name matches the directories located in &quot;tinymce/jscripts/tiny_mce/themes&quot;. The default value of this option is &quot;advanced&quot;. TinyMCE has three built in themes and these are described in greater detail below.
</p>
<p>
@ -41,7 +41,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -12,7 +12,7 @@
<div class="content">
<p>
This option should contain a comma separated list of block formats the default value of this option is &quot;p,address,pre,h1,h2,h3,h4,h5,h6&quot;. This option is only available if the advanced theme is used.
This option should contain a comma separated list of block formats the default value of this option is &quot;p,div,address,pre,h1,h2,h3,h4,h5,h6&quot;. This option is only available if the advanced theme is used.
</p>
<div class="separator"></div>
@ -22,7 +22,7 @@
<pre>
tinyMCE.init({
...
<strong>theme_advanced_blockformats : "p,h1,h2,h3,h4,h5,h6"</strong>
<strong>theme_advanced_blockformats : "p,div,h1,h2,h3,h4,h5,h6"</strong>
});
</pre>
</div>
@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -12,7 +12,7 @@
<div class="content">
<p>
This option should contain a comma separated list of button/control names to insert into the toolbar. The number 1-n is the row number to insert the buttons/controls to. Below is a list of build in controls, plugins may include other controls names that can be inserted but these are documented in the individual plugins.
This option should contain a comma separated list of button/control names to insert into the toolbar. The number 1-n is the row number to insert the buttons/controls to. Below is a list of built in controls, plugins may include other controls names that can be inserted but these are documented in the individual plugins.
This option can only be used when <a href="option_theme.html">theme</a> is set to advanced and when the <a href="option_theme_advanced_layout_manager.html">theme_advanced_layout_manager</a> option is set to the default value of &quot;SimpleLayout&quot;.
</p>
<p>
@ -36,7 +36,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -12,7 +12,7 @@
<div class="content">
<p>
This option should contain a comma separated list of button/control names to add to the end of the specified toolbar row. The number 1-n is the row number to add the buttons/controls to. Below is a list of build in controls, plugins may include other controls names that can be inserted but these are documented in the individual plugins.
This option should contain a comma separated list of button/control names to add to the end of the specified toolbar row. The number 1-n is the row number to add the buttons/controls to. Below is a list of built in controls, plugins may include other controls names that can be inserted but these are documented in the individual plugins.
This option can only be used when <a href="option_theme.html">theme</a> is set to advanced and when the <a href="option_theme_advanced_layout_manager.html">theme_advanced_layout_manager</a> option is set to the default value of &quot;SimpleLayout&quot;.
</p>
<p>
@ -36,7 +36,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -12,7 +12,7 @@
<div class="content">
<p>
This option should contain a comma separated list of button/control names to add to the beginning of the specified toolbar row. The number 1-n is the row number to add the buttons/controls to. Below is a list of build in controls, plugins may include other controls names that can be inserted but these are documented in the individual plugins.
This option should contain a comma separated list of button/control names to add to the beginning of the specified toolbar row. The number 1-n is the row number to add the buttons/controls to. Below is a list of built in controls, plugins may include other controls names that can be inserted but these are documented in the individual plugins.
This option can only be used when <a href="option_theme.html">theme</a> is set to advanced and when the <a href="option_theme_advanced_layout_manager.html">theme_advanced_layout_manager</a> option is set to the default value of &quot;SimpleLayout&quot;.
</p>
<p>
@ -36,7 +36,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -31,7 +31,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -31,7 +31,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -31,7 +31,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -41,7 +41,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -30,7 +30,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

View file

@ -31,7 +31,7 @@ tinyMCE.init({
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>

Some files were not shown because too many files have changed in this diff Show more