oqapi/webgui
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

upgraded to tinymce 2.0.1

Browse source
This commit is contained in:
JT Smith 2005-12-05 05:28:30 +00:00
parent 586e1a00fa
commit 75acc465b0
891 changed files with 16251 additions and 18835 deletions
Download patch file Download diff file Expand all files Collapse all files

41
www/extras/tinymce2/docs/about.html Normal file
View file

@ -0,0 +1,41 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>About</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>About</h1>
</div>
<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 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>
<h2>Features</h2>
<p>
<ul>
<li>Easy to integrate, takes only a couple lines of code.</li>
<li>Theme and template support.</li>
<li>Easy to extend with custom code. (Plugins and callbacks)</li>
<li>Customizable HTML output. Block elements and force attributes.</li>
<li>International language support (Language packs).</li>
<li>Multiple browser support, currently Mozilla (PC, Mac and Linux), MSIE (PC) and FireFox (PC, Mac and Linux) and some limited Safari support.</li>
</ul>
</p>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

84
www/extras/tinymce2/docs/compatiblity_chart.html Normal file
View file

@ -0,0 +1,84 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Compatiblity Chart</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Compatiblity Chart</h1>
</div>
<div class="content">
<h2>Browser support</h2>
<div class="section">
<p>TinyMCE uses advanced JavaScript and tries to be as smart as possible when it comes to different browsers, the main focus is on Microsoft Internet Explorer and Mozilla/Firefox. The table was reset to only show the browsers we ourselves can test on. It works with many older versions of Mozilla and Firefox. <strong>Just cause a browser is not listed on this page doesn't mean it does not work, try out the examples on our website.</strong></p>
<p>Since MacOS X 10.4 is more or less Linux we are not testing much on Linux any more, use the Sourceforge bug report system to submit bugs on the very latest browsers only.</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<tr>
<td>&nbsp;</td>
<td>Windows XP</td>
<td>MacOS X 10.4</td>
</tr>
<tr>
<td>MSIE 6</td>
<td>OK</td>
<td>&nbsp;</td>
</tr>
<tr>
<td>MSIE 5.5 SP2</td>
<td>OK</td>
<td>&nbsp;</td>
</tr>
<tr>
<td>MSIE 5.0</td>
<td>OK</td>
<td>&nbsp;</td>
</tr>
<tr>
<td>Mozilla 1.7.x</td>
<td>OK</td>
<td>OK</td>
</tr>
<tr>
<td>Firefox 1.0.x</td>
<td>OK</td>
<td>OK</td>
</tr>
<tr>
<td>Firefox 1.5b2</td>
<td>OK</td>
<td>OK</td>
</tr>
<tr>
<td>Safari 2.0 (412)</td>
<td>&nbsp;</td>
<td>OK(1)</td>
</tr>
<tr>
<td>Opera 9 Preview 1</td>
<td>OK(1)</td>
<td>OK(1)</td>
</tr>
</table>
</p>
<p>
<ul>
<li>(1) - Partialy working</li>
<li>(2) - Buggy browser version</li>
</ul>
</p>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

81
www/extras/tinymce2/docs/credits.html Normal file
View file

@ -0,0 +1,81 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Credits</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Credits</h1>
</div>
<div class="content">
<h2>Contributors</h2>
<div class="section">
<p>These are the people, companies or organizations that have contributed in some way to the TinyMCE project. If you feel we are missing someone please inform us right away and we will correct this in future versions of TinyMCE.</p>
<p>
Please note that some of these have contributed with complete language packs and some have updated parts of language packs or similar.
</p>
</div>
<div class="separator"></div>
<div class="section">
<p>
<ul>
<li class="list_subtitle">Code / Solutions / Features</li>
<ul>
<li>Michael Keck</li>
<li>Victor Nilsson</li>
<li>Jürgen Baute</li>
<li>"Neirda"</li>
<li>"speednet"</li>
<li>Virtuelcom</li>
<li>"SlyD"</li>
<li>Ernst de Moor</li>
<li>"jamesw"</li>
<li>Vincent FIACK</li>
<li>Aptest</li>
</ul>
<li class="list_subtitle">Language packs</li>
<ul>
<li>Marcin Szymon Sznyra</li>
<li>"revyag"</li>
<li>Jim Kou</li>
<li>"Krokogras"</li>
<li>Hani Suleiman</li>
<li>Jan Moelgaard</li>
<li>Christopher Müller</li>
<li>Virtuelcom</li>
<li>Pavel Novák</li>
<li>Simon Rupf</li>
<li>"Fabrix Xm"</li>
<li>Mats Löfström, York Consulting AB</li>
<li>Morteza Zafari</li>
<li>Laurent Dran</li>
<li>Tobias Heer</li>
<li>"Innozent"</li>
<li>"cube316"</li>
<li>José Pedro Pereira</li>
<li>"Martin"</li>
<li>Sten Aksel Heien</li>
<li>Setzer Gabbiani</li>
<li>Jacaranda Bill</li>
<li>Pat Boens</li>
<li>Roman Filippov</li>
<li>Arnoud van Delden</li>
</ul>
</ul>
</p>
<p>There are also a few corporations that have contributed in various ways to have features developed by payed support.
</p>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

145
www/extras/tinymce2/docs/css/screen.css Normal file
View file

@ -0,0 +1,145 @@
body {
background-color: #FFFFFF;
font-family: Verdana, Arial, helvetica, sans-serif;
font-size: 12px;
}
.header {
border: #E0E0E0 solid 1px;
}
.footer {
border: #E0E0E0 solid 1px;
height: 20px;
}
h1 {
font-size: 18px;
font-weight: bold;
padding: 0px;
margin: 4px;
}
h2 {
font-size: 14px;
font-weight: bold;
padding: 0px;
margin: 0px;
margin-top: 4px;
margin-bottom: 4px;
}
h3 {
font-size: 11px;
font-weight: bold;
padding: 0px;
margin: 0px;
margin-bottom: 3px;
}
.section {
margin-left: 15px;
}
.column {
margin-right: 20px;
float: left
}
.separator {
border-bottom: 1px solid #E6EBF1;
margin-top: 10px;
margin-bottom: 10px;
}
p {
}
.helpindex {
margin-left: 20px;
padding-left: 0px;
}
.optionlist {
margin: 0px;
padding: 0px;
margin-bottom: 10px;
}
.optionlist li {
padding: 0px;
margin: 0px;
margin-top: 3px;
margin-bottom: 3px;
margin-left: 10px;
list-style-type: none;
}
.helpindex li {
margin-top: 3px;
}
.content {
margin: 10px;
}
.example {
background-color: #E6EBF1;
margin-left: 10px;
}
code, pre {
margin: 0px;
padding: 0px;
background-color: #E6EBF1;
}
.copyright {
margin: 3px;
float: left;
}
.helpindexlink {
margin: 3px;
float: right;
}
a:visited {
color: #666666;
text-decoration: underline;
}
a:active {
color: #666666;
text-decoration: underline;
}
a:hover {
color: #666666;
text-decoration: underline;
}
a {
color: #666666;
text-decoration: underline;
}
.list_subtitle {
padding-top: 5px;
}
.note {
margin-top: 5px;
margin-left: 10px;
font-size: 10px;
}
.marked {
color: red;
font-weight: bold;
}
thead {
background-color: #E6EBF1;
}

51
www/extras/tinymce2/docs/customization_language_packs.html Normal file
View file

@ -0,0 +1,51 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Customization - Creating a language pack</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Customization - Creating a language pack</h1>
</div>
<div class="content">
<h2>Making language packs</h2>
<p>Language packs are simply JavaScript name/value arrays placed in the &quot;<ISO-639-2 code>.js&quot; files in the &quot;lang&quot; directory. Remember to allways use the &quot;lang_&quot; prefix for these value names so that they don't override other variables in the templates. The example below shows how the cut, copy and paste texts are lang packed. Notice there are three kinds of language packs the first one is the general one shared by all themes these are located in the &quot;jscripts/tiny_mce/langs&quot; directory the secound ones are theme specific language packs these are contained in &quot;jscripts/tiny_mce/themes/&lt;some theme&gt;/langs&quot; and the last one is plugin specific language packs located in each plugin.
</p>
<p>
<div class="example">
<pre>
tinyMCE.addToLang('',{
cut_desc : 'Cut (Ctrl+X)',
copy_desc : 'Copy (Ctrl+C)',
paste_desc : 'Paste (Ctrl+P)'
);
</pre>
</div>
</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>
When translating TinyMCE, these are the files that currently needs to be translated:
</p>
<p>
/tinymce/jscripts/tiny_mce/langs/en.js<br />
/tinymce/jscripts/tiny_mce/plugins/&lt;plugin&gt;/langs/en.js<br />
/tinymce/jscripts/tiny_mce/themes/advanced/langs/en.js<br />
</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>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

254
www/extras/tinymce2/docs/customization_plugins.html Normal file
View file

@ -0,0 +1,254 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Customization - Creating a plugin</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Customization - Creating a plugin</h1>
</div>
<div class="content">
<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;.
</p>
<p>
The example below has three functions, these are explained in greater detail below.
</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'
};
};
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;
}
</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>
<br style="clear: both" />
</div>
</body>
</html>

423
www/extras/tinymce2/docs/customization_themes.html Normal file
View file

@ -0,0 +1,423 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Customization - Creating a theme</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Customization - Creating a theme</h1>
</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;.
</p>
<p>
The example below has three functions, these are explained in greater detail below.
</p>
<p>
<div class="example">
<pre>
function TinyMCE_<span class="marked">default</span>_getEditorTemplate(settings) {
var template = new Array();
template['html'] = '&lt;Some HTML&gt;';
template['delta_width'] = 0;
template['delta_height'] = -40;
return template;
}
function TinyMCE_<span class="marked">default</span>_getInsertLinkTemplate(settings) {
var template = new Array();
template['file'] = 'link.htm';
template['width'] = 320;
template['height'] = 130;
return template;
}
function TinyMCE_<span class="marked">default</span>_getInsertImageTemplate(settings) {
var template = new Array();
template['file'] = 'image.htm';
template['width'] = 320;
template['height'] = 130;
return template;
}
function TinyMCE_<span class="marked">default</span>_handleNodeChange(editor_id, node) {
// Check what happend
}
function TinyMCE_<span class="marked">default</span>_execCommand(editor_id, element, command, user_interface, value) {
// Your custom command logic
return false;
}
</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;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>
<br style="clear: both" />
</div>
</body>
</html>

144
www/extras/tinymce2/docs/faq.html Normal file
View file

@ -0,0 +1,144 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Frequently Asked Questions</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Frequently Asked Questions</h1>
</div>
<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>
<div class="separator"></div>
<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>
<p>
<ul>
<li>Does TinyMCE work on the <a href="http://tinymce.moxiecode.com/example_full.php?example=true">TinyMCE website</a>. Then you know that TinyMCE works with your browser.</li>
<li>Try to disable any other JavaScripts on the page, some scripts interfere with internal functions that TinyMCE uses. Those scripts are probably poorly written.</li>
<li>Check that you havn't missed removing the last , character in your initialization code and that all the other rows have a trailing , character.</li>
<li>Verify that the path/URL to TinyMCE is correct, you can use the excellent tool <a href="http://www.fiddlertool.com/fiddler/">Fiddler</a> for this and other HTTP debugging.</li>
<li>Do not cross domain load TinyMCE or any other script unless you really really must, since this will invoke various browser security features. In other words, try placing everything on the same server.</li>
<li>Don't place textareas within paragraph elements since this is not valid HTML and it will break MSIE and TinyMCE.</li>
</ul>
</p>
</div>
<div class="separator"></div>
<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>
</div>
<div class="separator"></div>
<h2>How do I change the default font size/face color of the editor?</h2>
<div class="section">
<p>
We recommend that you have a look at the <a href="option_content_css.html">content_css</a> option, this enables you to switch the CSS file TinyMCE uses for it's editing area with a file with your CSS rules for font size and so forth.
</p>
</div>
<div class="separator"></div>
<h2>How do I remove/add buttons/controls to TinyMCE?</h2>
<div class="section">
<p>
There are quite a few options for this but a reference of all available buttons/control names can be found in the <a href="reference_buttons.html">button/control reference</a>.
</p>
</div>
<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>
<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>
</div>
<div class="separator"></div>
<h2>TinyMCE takes ages to load, is there a way to make it load quicker?</h2>
<div class="section">
<p>
If you use PHP on your server you can use tiny_mce_gzip.php instead of tiny_mce.js in page script call. This PHP file bundles all .js files together into two HTTP requests instead of one for each plugin, language file and theme and it also GZip compresses these files.
</p>
</div>
<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>
<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>
</div>
<div class="separator"></div>
<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.
</p>
</div>
<div class="separator"></div>
<h2>I don't like LGPL, is there a commercial license available for me?</h2>
<div class="section">
<p>
Yes, we can draw up a license for you that enables you to remove copyright restrictions or anything else you would like to have in this license agreement. Contact us through email, sales (at) moxiecode (dot) com.
</p>
</div>
<div class="separator"></div>
<h2>Do you provide support?</h2>
<div class="section">
<p>
We do not provide any non-commercial support outside the forum on the <a href="http://tinymce.moxiecode.com/">TinyMCE</a> web site. If you require commercial support, contact us by email, sales (at) moxiecode (dot) com.
</p>
</div>
<div class="separator"></div>
<h2>Who made this software?</h2>
<div class="section">
<p>
The author of TinyMCE is <a href="http://www.moxiecode.com/" target="_blank">Moxiecode Systems</a>, parts of code has also been contributed by others, <a href="credits.html">here</a> are the credits list.
</p>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

BIN
www/extras/tinymce2/docs/images/moxiecode.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 2.7 KiB

44
www/extras/tinymce2/docs/index.html Normal file
View file

@ -0,0 +1,44 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>TinyMCE Documentation - Index</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>TinyMCE Documentation</h1>
</div>
<div class="content">
<ul class="helpindex">
<li><a href="about.html">About TinyMCE</a></li>
<li><a href="installing.html">Installation instructions</a></li>
<li class="list_subtitle"><strong>Reference</strong></li>
<ul>
<li><a href="reference_configuration.html">Configuration</a></li>
<li><a href="reference_buttons.html">Button/control reference</a></li>
<li><a href="reference_javascript_functions.html">JavaScript functions</a></li>
<li><a href="reference_plugins.html">Plugins</a></li>
</ul>
<li class="list_subtitle"><strong>Customization</strong></li>
<ul style="padding-bottom: 5px;">
<li><a href="customization_plugins.html">Creating a plugin</a></li>
<li><a href="customization_language_packs.html">Creating a language pack</a></li>
<li><a href="customization_themes.html">Creating a theme</a></li>
</ul>
<li><a href="compatiblity_chart.html">Compatiblity chart</a></li>
<li><a href="faq.html">Frequently asked questions</a></li>
<li><a href="credits.html">Credits</a></li>
<li><a href="license.html">License (LGPL)</a></li>
</ul>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

35
www/extras/tinymce2/docs/installation_example_00.html Normal file
View file

@ -0,0 +1,35 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Installation Example 00</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
<script language="javascript" type="text/javascript" src="../jscripts/tiny_mce/tiny_mce.js"></script>
<script language="javascript" type="text/javascript">
tinyMCE.init({
mode : "textareas",
theme : "simple"
});
</script>
</head>
<body>
<div class="header">
<h1>Installation example 00</h1>
</div>
<div class="content">
<h3>Example</h3>
<form method="post">
<textarea name="content" cols="50" rows="15">This is some content that will be editable with TinyMCE.</textarea>
</form>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

36
www/extras/tinymce2/docs/installation_example_01.html Normal file
View file

@ -0,0 +1,36 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Installation Example 01</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
<script language="javascript" type="text/javascript" src="../jscripts/tiny_mce/tiny_mce_src.js"></script>
<script language="javascript" type="text/javascript">
tinyMCE.init({
mode : "textareas",
theme : "advanced"
});
</script>
</head>
<body>
<div class="header">
<h1>Installation example 01</h1>
</div>
<div class="content">
<h3>Example</h3>
<p>Open this page with "View source" or similar to see how the configuration is made.</p>
<form method="post">
<textarea name="content" cols="50" rows="15">This is some content that will be editable with TinyMCE.</textarea>
</form>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

52
www/extras/tinymce2/docs/installation_example_02.html Normal file
View file

@ -0,0 +1,52 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Installation Example 02</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
<script language="javascript" type="text/javascript" src="../jscripts/tiny_mce/tiny_mce.js"></script>
<script language="javascript" type="text/javascript">
tinyMCE.init({
mode : "textareas",
theme : "advanced",
plugins : "table,save,advhr,advimage,advlink,emotions,iespell,insertdatetime,preview,zoom,flash,searchreplace,print,contextmenu",
theme_advanced_buttons1_add_before : "save,separator",
theme_advanced_buttons1_add : "fontselect,fontsizeselect",
theme_advanced_buttons2_add : "separator,insertdate,inserttime,preview,zoom,separator,forecolor,backcolor",
theme_advanced_buttons2_add_before: "cut,copy,paste,separator,search,replace,separator",
theme_advanced_buttons3_add_before : "tablecontrols,separator",
theme_advanced_buttons3_add : "emotions,iespell,flash,advhr,separator,print",
theme_advanced_toolbar_location : "top",
theme_advanced_toolbar_align : "left",
theme_advanced_path_location : "bottom",
plugin_insertdate_dateFormat : "%Y-%m-%d",
plugin_insertdate_timeFormat : "%H:%M:%S",
extended_valid_elements : "a[name|href|target|title|onclick],img[class|src|border=0|alt|title|hspace|vspace|width|height|align|onmouseover|onmouseout|name],hr[class|width|size|noshade],font[face|size|color|style],span[class|align|style]",
external_link_list_url : "example_data/example_link_list.js",
external_image_list_url : "example_data/example_image_list.js",
flash_external_list_url : "example_data/example_flash_list.js"
});
</script>
</head>
<body>
<div class="header">
<h1>Installation example 02</h1>
</div>
<div class="content">
<h3>Example</h3>
<p>Open this page with "View source" or similar to see how the configuration is made.</p>
<form method="post">
<textarea name="content" cols="85" rows="15">This is some content that will be editable with TinyMCE.</textarea>
</form>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

43
www/extras/tinymce2/docs/installation_example_03.html Normal file
View file

@ -0,0 +1,43 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Installation Example 02</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
<script language="javascript" type="text/javascript" src="../jscripts/tiny_mce/tiny_mce.js"></script>
<script language="javascript" type="text/javascript">
tinyMCE.init({
mode : "textareas",
theme : "advanced",
theme_advanced_buttons1 : "bold,italic,underline,separator,strikethrough,justifyleft,justifycenter,justifyright, justifyfull,bullist,numlist,undo,redo,link,unlink",
theme_advanced_buttons2 : "",
theme_advanced_buttons3 : "",
theme_advanced_toolbar_location : "top",
theme_advanced_toolbar_align : "left",
theme_advanced_path_location : "bottom",
extended_valid_elements : "a[name|href|target|title|onclick],img[class|src|border=0|alt|title|hspace|vspace|width|height|align|onmouseover|onmouseout|name],hr[class|width|size|noshade],font[face|size|color|style],span[class|align|style]"
});
</script>
</head>
<body>
<div class="header">
<h1>Installation example 02</h1>
</div>
<div class="content">
<h3>Example</h3>
<p>Open this page with "View source" or similar to see how the configuration is made.</p>
<form method="post">
<textarea name="content" cols="85" rows="15">This is some content that will be editable with TinyMCE.</textarea>
</form>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

121
www/extras/tinymce2/docs/installing.html Normal file
View file

@ -0,0 +1,121 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Installation instructions</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Installation instructions</h1>
</div>
<div class="content">
<p>Installing TinyMCE is very simple, follow the instructions here. We give a few examples of to integrate TinyMCE, also look at the extensive <a href="reference_configuration.html">options</a> for configuration.</p>
<div class="separator"></div>
<h2>Requirements</h2>
<div class="section">
<p>TinyMCE has no direct requirements except for <a href="compatiblity_chart.html">browser compatibility</a> and of course JavaScript needs to be turned on. There is NO backend code distributed with TinyMCE.
</p>
</div>
<div class="separator"></div>
<h2>Downloading</h2>
<div class="section">
<p>For download instructions check our <a href="http://tinymce.moxiecode.com">web site.</a></p>
</div>
<div class="separator"></div>
<h2>Extracting the archives</h2>
<div class="section">
<p>On windows you could use <a href="http://www.winzip.com">WinZip</a> or something similar. And on other operating systems such as Linux you simply extract the archive with the tar command. You can find a example on how to extract the archived file on Linux below.</p>
<p>
You should extract TinyMCE in your wwwroot or site domain root folder
</p>
<h3>Extract example using a shell:</h3>
<div class="example">
<pre>
$ cd wwwroot
$ gzip -d tinymce_1_44.tar.gz
$ tar xvf tinymce_1_44.tar
</pre>
</div>
<p>
<h3>A folder structure looking like this is created:</h3>
<div class="example">
<pre>
/tinymce/
/tinymce/docs/
/tinymce/docs/zh_cn/
/tinymce/examples/
/tinymce/examples/zh_cn/
/tinymce/jscripts/
/tinymce/jscripts/tiny_mce/
/tinymce/jscripts/tiny_mce/langs/
/tinymce/jscripts/tiny_mce/plugins/
/tinymce/jscripts/tiny_mce/plugins/&lt;plugin folders&gt;
/tinymce/jscripts/tiny_mce/themes/
/tinymce/jscripts/tiny_mce/themes/advanced/
/tinymce/jscripts/tiny_mce/themes/default/
/tinymce/jscripts/tiny_mce/themes/simple/
</pre>
</div>
</p>
</div>
<div class="separator"></div>
<h2>Making changes on your web site</h2>
<div class="section">
<p>Once you have extracted the archive you will need to edit the pages to include the configuration and javascript for TinyMCE. Please note that you should probably only include the TinyMCE javascript on the pages that need it, not all the pages of the web site. Remember to change the URL to the .js below to match your installation path.</p>
<p>
<h3>The most basic page integration (converts all textarea elements into editors):</h3>
<div class="example">
<pre>
&lt;html&gt;
&lt;head&gt;
&lt;title&gt;TinyMCE Test&lt;/title&gt;
<strong>&lt;script language=&quot;javascript&quot; type=&quot;text/javascript&quot; src=&quot;../jscripts/tiny_mce/tiny_mce.js&quot;&gt;&lt;/script&gt;
&lt;script language=&quot;javascript&quot; type=&quot;text/javascript&quot;&gt;
tinyMCE.init({
mode : &quot;textareas&quot;
});
&lt;/script&gt;</strong>
&lt;/head&gt;
&lt;body&gt;
&lt;form method=&quot;post&quot;&gt;
&lt;textarea name=&quot;content&quot; cols=&quot;50&quot; rows=&quot;15&quot;&gt;This is some content that will be editable with TinyMCE.&lt;/textarea&gt;
&lt;/form&gt;
&lt;/body&gt;
&lt;/html&gt;
</pre>
</div>
</p>
<p>
Here are a few different example of how you could integrate TinyMCE.
</p>
<p>
<ul>
<li><a href="installation_example_00.html">Example 00</a> - Simple Theme</li>
<li><a href="installation_example_01.html">Example 01</a> - Advanced Theme</li>
<li><a href="installation_example_02.html">Example 02</a> - Advanced Theme Full</li>
<li><a href="installation_example_03.html">Example 03</a> - Advanced Theme Simplified</li>
</ul>
</p>
<p>
If you have any problems, you should check the forum on the <a href="http://tinymce.moxiecode.com/" target="_blank">TinyMCE web site.</a></p>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

465
www/extras/tinymce2/docs/license.html Normal file
View file

@ -0,0 +1,465 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>TinyMCE License (LGPL)</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>TinyMCE License (LGPL)</h1>
</div>
<div class="content">
<p>
Visit the <a href="faq.html">FAQ</a> for general answers surrounding TinyMCE. Or visit <a href="http://www.fsf.org" target="_blank">http://www.fsf.org</a> for more information about Open-Source licenses.
</p>
<pre>
GNU LIBRARY GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the library GPL. It is
numbered 2 because it goes with version 2 of the ordinary GPL.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Library General Public License, applies to some
specially designated Free Software Foundation software, and to any
other libraries whose authors decide to use it. You can use it for
your libraries, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if
you distribute copies of the library, or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link a program with the library, you must provide
complete object files to the recipients so that they can relink them
with the library, after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
Our method of protecting your rights has two steps: (1) copyright
the library, and (2) offer you this license which gives you legal
permission to copy, distribute and/or modify the library.
Also, for each distributor's protection, we want to make certain
that everyone understands that there is no warranty for this free
library. If the library is modified by someone else and passed on, we
want its recipients to know that what they have is not the original
version, so that any problems introduced by others will not reflect on
the original authors' reputations.
.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that companies distributing free
software will individually obtain patent licenses, thus in effect
transforming the program into proprietary software. To prevent this,
we have made it clear that any patent must be licensed for everyone's
free use or not licensed at all.
Most GNU software, including some libraries, is covered by the ordinary
GNU General Public License, which was designed for utility programs. This
license, the GNU Library General Public License, applies to certain
designated libraries. This license is quite different from the ordinary
one; be sure to read it in full, and don't assume that anything in it is
the same as in the ordinary license.
The reason we have a separate public license for some libraries is that
they blur the distinction we usually make between modifying or adding to a
program and simply using it. Linking a program with a library, without
changing the library, is in some sense simply using the library, and is
analogous to running a utility program or application program. However, in
a textual and legal sense, the linked executable is a combined work, a
derivative of the original library, and the ordinary General Public License
treats it as such.
Because of this blurred distinction, using the ordinary General
Public License for libraries did not effectively promote software
sharing, because most developers did not use the libraries. We
concluded that weaker conditions might promote sharing better.
However, unrestricted linking of non-free programs would deprive the
users of those programs of all benefit from the free status of the
libraries themselves. This Library General Public License is intended to
permit developers of non-free programs to use free libraries, while
preserving your freedom as a user of such programs to change the free
libraries that are incorporated in them. (We have not seen how to achieve
this as regards changes in header files, but we have achieved it as regards
changes in the actual functions of the Library.) The hope is that this
will lead to faster development of free libraries.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, while the latter only
works together with the library.
Note that it is possible for a library to be covered by the ordinary
General Public License rather than by this special one.
.
GNU LIBRARY GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library which
contains a notice placed by the copyright holder or other authorized
party saying it may be distributed under the terms of this Library
General Public License (also called "this License"). Each licensee is
addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
.
6. As an exception to the Sections above, you may also compile or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
c) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
d) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the source code distributed need not include anything that is normally
distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
.
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Library General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
</pre>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_accessibility_warnings.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: accessibility_warnings</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: accessibility_warnings</h1>
</div>
<div class="content">
<p>
If this option is set to true some accessibility warnings will be presented to the user if they miss specifying that information. This option is set to true default, since we should all try to make this world a better place for disabled people. But if you are annoyed with the warnings, set this option to false.
</p>
<div class="separator"></div>
<h3>Example of usage of the accessibility_warnings option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>accessibility_warnings : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_add_form_submit_trigger.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: add_form_submit_trigger</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: add_form_submit_trigger</h1>
</div>
<div class="content">
<p>
This option enables you to turn on/off the onsubmit event listener. This feature adds a onsubmit event listener on all forms on the page, if a form is submitted a tinyMCE.triggerSave() JavaScript calls gets executed, this function moves HTML content from the editor iframe and to the hidden form element. This option is set to true by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the add_form_submit_trigger option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>add_form_submit_trigger : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_add_unload_trigger.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: add_unload_trigger</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: add_unload_trigger</h1>
</div>
<div class="content">
<p>
If you set this option to true, page contents will be stored away is the page is unloaded for example is the user navigates away from the page and then navigated back to it by pressing the back button. This option is set to true by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the add_unload_trigger option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>add_unload_trigger : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_apply_source_formatting.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: apply_source_formatting</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: apply_source_formatting</h1>
</div>
<div class="content">
<p>
This option enables you to tell TinyMCE to apply some source formatting to the output HTML code. This function is disabled by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the apply_source_formatting option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>apply_source_formatting : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_ask.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: ask</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: ask</h1>
</div>
<div class="content">
<p>
This option enables you to add a confirmation dialog when focusing textareas. This dialog asks if the focused textarea should be converted into a editor instance or not. It will only ask once since it would get annoying otherwice. The default value of this option is &quot;false&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the ask option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>ask : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_auto_focus.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: auto_focus</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: auto_focus</h1>
</div>
<div class="content">
<p>
This option enables you to auto focus a editor instance. The value of this option should be a editor instance id. Editor instance ids are specified as &quot;mce_editor_&lt;index&gt;&quot; where index is a value starting from 0. So if there are 3 editor instances on a page these would have the following ids mce_editor_0, mce_editor_1 and mce_editor_2.
</p>
<div class="separator"></div>
<h3>Example of usage of the auto_focus option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>auto_focus : "mce_editor_2"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_auto_reset_designmode.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: auto_reset_designmode</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: auto_reset_designmode</h1>
</div>
<div class="content">
<p>
This option is very useful if TinyMCE is used in a DHTML tab system or other divs that are hidden and displayed by some JavaScript. Since Mozilla has a bug when using display:none, the designMode state gets lost. To prevent this from happening you should enable this option. The default value of this option is &quot;true&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the auto_reset_designmode option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>auto_reset_designmode : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_auto_resize.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: auto_resize</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: auto_resize</h1>
</div>
<div class="content">
<p>
This option enables you to get the TinyMCE editor area to resize to the bounderies of the contents. This option is very experimental and is set to false by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the auto_resize option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>auto_resize : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_browsers.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: browsers</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: browsers</h1>
</div>
<div class="content">
<p>
This option should contain a comma separated list of supported browsers. This enables you to for example disable the editor while running on Safari. The default value of this option is: msie,gecko,safari,opera and since the support for Safari is very limited a warning message will appear until a better version is released. The possible values of this option is msie, gecko and safari.
</p>
<div class="separator"></div>
<h3>Example of usage of the browsers option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>browsers : "msie,gecko,opera"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_button_tile_map.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: button_tile_map</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: button_tile_map</h1>
</div>
<div class="content">
<p>
If this option is set to true TinyMCE will use tiled images instead of individual images for most of the editor controls. This produces faster loading time since only one GIF image needs to be loaded instead of a GIF for each individual button. This option is set to false by default since it doesn't work with some DOCTYPE declarations.
</p>
<div class="separator"></div>
<h3>Example of usage of the button_tile_map option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>button_tile_map : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_cleanup.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: cleanup</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: cleanup</h1>
</div>
<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>
</p>
<div class="separator"></div>
<h3>Example of usage of the cleanup option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>cleanup : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

72
www/extras/tinymce2/docs/option_cleanup_callback.html Normal file
View file

@ -0,0 +1,72 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: cleanup_callback</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: cleanup_callback</h1>
</div>
<div class="content">
<p>
This option enables you to add custom cleanup logic to TinyMCE. This function is called when the cleanup process is executed this process occures when the editor saves/submits content, user hits the cleanup button and when the HTML editor dialog is presented. The format of this function is: customCleanup(type, value). Where type can be &quot;get_from_editor&quot; when the contents is extracted from TinyMCE for example when the user submits the form. The &quot;insert_to_editor&quot; type value gets passed when new contents is inserted into the editor on initialization or when the HTML editor dialog commits new content. The &quot;get_from_editor_dom&quot; value is executed when cleanup process has a valid DOM tree and is extracted from the editor. The &quot;insert_to_editor_dom&quot; gets passed when the editor has a valid DOM tree and contents has been inserted into the editor. The example below illustrated all these types.
</p>
<div class="separator"></div>
<h3>Example of usage of the cleanup_callback option:</h3>
<div class="example">
<pre>
function <strong>myCustomCleanup</strong>(type, value) {
switch (type) {
case "get_from_editor":
alert("Value HTML string: " + value);
// Do custom cleanup code here
break;
case "insert_to_editor":
alert("Value HTML string: " + value);
// Do custom cleanup code here
break;
case "get_from_editor_dom":
alert("Value DOM Element " + value);
// Do custom cleanup code here
break;
case "insert_to_editor_dom":
alert("Value DOM Element: " + value);
// Do custom cleanup code here
break;
}
return value;
}
tinyMCE.init({
...
<strong>cleanup_callback : "myCustomCleanup"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_cleanup_on_startup.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: cleanup_on_startup</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: cleanup_on_startup</h1>
</div>
<div class="content">
<p>
If you set this option to true, TinyMCE will perform a HTML cleanup call when the editor loads. This option is set to false by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the cleanup_on_startup option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>cleanup_on_startup : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_content_css.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: content_css</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: content_css</h1>
</div>
<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.
</p>
<div class="separator"></div>
<h3>Example of usage of the content_css option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>content_css : "/mycontent.css"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_convert_fonts_to_spans.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: convert_fonts_to_spans</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: convert_fonts_to_spans</h1>
</div>
<div class="content">
<p>If you set this option to true, all TinyMCE will convert all font elements to span elements and generate span elements instead of font elements. This option should be used inorder to get more W3C compatible code, since font elements are deprecated. How sizes gets converted can be controlled by the <a href="option_font_size_classes.html">font_size_classes</a> and <a href="option_font_size_style_values.html">font_size_style_values</a> options.</p>
<p>
More information about this subject can be found in this article: <a href="http://www.microsoft.com/typography/web/designer/face7.htm">What's wrong with FONT FACE</a>
</p>
<div class="separator"></div>
<h3>Example of usage of the convert_fonts_to_spans option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>convert_fonts_to_spans : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_convert_newlines_to_brs.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: convert_newlines_to_brs</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: convert_newlines_to_brs</h1>
</div>
<div class="content">
<p>
If you set this option to true newline characters codes gets converted in to br elements. This option is set to false by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the convert_newlines_to_brs option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>convert_newlines_to_brs : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

36
www/extras/tinymce2/docs/option_convert_urls.html Normal file
View file

@ -0,0 +1,36 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: convert_urls</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: convert_urls</h1>
</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>
<div class="separator"></div>
<h3>Example of usage of the convert_urls option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>convert_urls : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_custom_undo_redo.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: custom_undo_redo</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: custom_undo_redo</h1>
</div>
<div class="content">
<p>
This option is a true/false option that enables you to disable/enable the custom undo/redo logic within TinyMCE. This option is enabled by default, if you disable it some operations may not be undoable.
</p>
<div class="separator"></div>
<h3>Example of usage of the custom_undo_redo option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>custom_undo_redo : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_custom_undo_redo_keyboard_shortcuts.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: custom_undo_redo_keyboard_shortcuts</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: custom_undo_redo_keyboard_shortcuts</h1>
</div>
<div class="content">
<p>
This option enables you to disable/enable the usage of keyboard shortcuts for undo/redo. This feature is enabled by default. Keyboard shortcurs are Ctrl+Z for undo, Ctrl+Y for redo.
</p>
<div class="separator"></div>
<h3>Example of usage of the custom_undo_redo_keyboard_shortcuts option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>custom_undo_redo_keyboard_shortcuts : "false"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_custom_undo_redo_levels.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: custom_undo_redo_levels</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: custom_undo_redo_levels</h1>
</div>
<div class="content">
<p>
This option should contain the number of undo levels to keep in memory. This is set to -1 by default and such a value tells TinyMCE to use a unlimited number of undo levels. But this steals lots of memory so for low end systems a value of 10 may be better.
</p>
<div class="separator"></div>
<h3>Example of usage of the custom_undo_redo_levels option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>custom_undo_redo_levels : 10</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_debug.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: debug</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: debug</h1>
</div>
<div class="content">
<p>
If the value of this option is set to &quot;true&quot; some debugging information will appear such as a list of what CSS files are used. The default value of this option is false.
</p>
<div class="separator"></div>
<h3>Example of usage of the debug option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>debug : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_dialog_type.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: dialog_type</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: dialog_type</h1>
</div>
<div class="content">
<p>
This option enables you to specify how dialogs/popups should be opened, possible values are &quot;window&quot; and &quot;modal&quot;, where the window option opens a normal window and the dialog option opens a modal dialog. This option is set to &quot;window&quot; by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the dialog_type option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>dialog_type : "modal"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_directionality.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: directionality</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: directionality</h1>
</div>
<div class="content">
<p>
This option specifies the default writing direction, some languages writes from right to left instead of left to right. The default value of this option is &quot:ltr&quot; but if you want to use from right to left mode specify &quot;rtl&quot; instead.
</p>
<div class="separator"></div>
<h3>Example of usage of the directionality option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>directionality : "rtl"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_docs_language.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: docs_language</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: docs_language</h1>
</div>
<div class="content">
<p>
This option should contain a language code of the editor documentation to use with TinyMCE. These codes are in <a href="http://www.loc.gov/standards/iso639-2/englangn.html">ISO-639-2</a> format to see if your language is available check the contents of &quot;tinymce/jscripts/tiny_mce/theme/&lt;theme used&gt;/docs&quot;. The default value of this option is the value specified in the &quot;language&quot; option or &quot;en&quot; for English.
</p>
<div class="separator"></div>
<h3>Example of usage of the docs_language option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>docs_language : "sv"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

35
www/extras/tinymce2/docs/option_doctype.html Normal file
View file

@ -0,0 +1,35 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: doctype</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: doctype</h1>
</div>
<div class="content">
<p>This option enables you to specify the doctype that is used while editing content within TinyMCE, this defaults to <!DOCTYPE html PUBLIC &quot;-//W3C//DTD HTML 4.0 Transitional//EN&quot;>.</p>
<div class="separator"></div>
<h3>Example of usage of the doctype option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>doctype : &quot;&lt;!DOCTYPE html PUBLIC &quot;-//W3C//DTD XHTML 1.0 Transitional//EN&quot; &quot;http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd&quot;&gt;&quot;</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

36
www/extras/tinymce2/docs/option_document_base_url.html Normal file
View file

@ -0,0 +1,36 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: document_base_url</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: document_base_url</h1>
</div>
<div class="content">
<p>This option enables you to specify the URL from where all URLs will be relative to this option is only used when the <a href="option_relative_urls.html">relative_urls</a> option is set to true. The value of this option is set to the current document by default.</p>
<div class="separator"></div>
<h3>Example of usage of the document_base_url option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>document_base_url : "/somedir/somfile.html"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_editor_css.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: editor_css</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: editor_css</h1>
</div>
<div class="content">
<p>
This option enables you to specify the CSS to be used for the editor toolbars/user interface of TinyMCE this option is set to a CSS file found in the currently used theme by default. This CSS contains layout information about panels and buttons used by TinyMCE.
</p>
<div class="separator"></div>
<h3>Example of usage of the editor_css option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>editor_css : "/myeditor.css"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

49
www/extras/tinymce2/docs/option_editor_deselector.html Normal file
View file

@ -0,0 +1,49 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: editor_deselector</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: editor_deselector</h1>
</div>
<div class="content">
<p>
This option enables you to specify a CSS class name that will be deselect textareas from being converted into editor instances. If this option isn't set to a value this option will not have any effect and the <a href="option_mode.html">mode</a> option will choose textareas instead. The default value of this option is &quot;mceNoEditor&quot; so if mceNoEditor is added to the class attribute of a textarea it will be excluded for convertion.
</p>
<div class="separator"></div>
<h3>Example of usage of the editor_deselector option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>editor_deselector : "mceNoEditor"</strong>
});
</pre>
</div>
<div class="separator"></div>
<h3>Example of usage in the HTML:</h3>
<div class="example">
<pre>
&lt;textarea id=&quot;myarea1&quot; class=&quot;<strong>mceNoEditor</strong>&quot;&gt;This will be a NOT be a editor.&lt;/textarea&gt;
&lt;textarea id=&quot;myarea2&quot;&gt;This will be a editor.&lt;/textarea&gt;
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

49
www/extras/tinymce2/docs/option_editor_selector.html Normal file
View file

@ -0,0 +1,49 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: editor_selector</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: editor_selector</h1>
</div>
<div class="content">
<p>
This option enables you to specify a CSS class name that will be required on the text areas that is to be converted. This enables you to select specific text areas for convertion by adding this CSS class name to the class attribute of the text area. If this option isn't set to a value this option will not have any effect and the <a href="option_mode.html">mode</a> option will choose textareas instead. If you want all editors to be converted and just specific editors to be excluded check the <a href="option_editor_deselector.html">editor_deselector</a> option.
</p>
<div class="separator"></div>
<h3>Example of usage of the editor_selector option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>editor_selector : "mceEditor"</strong>
});
</pre>
</div>
<div class="separator"></div>
<h3>Example of usage in the HTML:</h3>
<div class="example">
<pre>
&lt;textarea id=&quot;myarea1&quot; class=&quot;<strong>mceEditor</strong>&quot;&gt;This will be a editor.&lt;/textarea&gt;
&lt;textarea id=&quot;myarea2&quot;&gt;This will NOT be a editor.&lt;/textarea&gt;
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_elements.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: elements</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: elements</h1>
</div>
<div class="content">
<p>
This option should contain a comma separated list of element id's to convert into editor instances. This option is only used if <a href="option_mode.html">mode</a> is set to &quot;exact&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the elements option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>elements : "elm1,elm2"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_encoding.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: encoding</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: encoding</h1>
</div>
<div class="content">
<p>
This option enables you to get XML escaped contents out of TinyMCE. Posted content will be converted to a XML string escaping characters such as &lt; &gt; &quot; &amp; to &amp;lt; &amp;gt; &amp;quot; &amp;amp;. This option is set nothing by default and is there for disabled.
</p>
<div class="separator"></div>
<h3>Example of usage of the encoding option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>encoding : "xml"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_entities.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: entities</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: entities</h1>
</div>
<div class="content">
<p>
This option contains a comma separated list of entity names that is used instead of characters. Odd items are the character code and even items are the name of the character code. The default value of this option is placed in the example below.
</p>
<div class="separator"></div>
<h3>Example of usage of the entities option / default value:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>entities : "160,nbsp,38,amp,34,quot,162,cent,8364,euro,163,pound,165,yen,169,copy,174,reg,8482,trade,8240,permil,181,micro,183,middot,8226,bull,8230,hellip,8242,prime,8243,Prime,167,sect,182,para,223,szlig,8249,lsaquo,8250,rsaquo,171,laquo,187,raquo,8216,lsquo,8217,rsquo,8220,ldquo,8221,rdquo,8218,sbquo,8222,bdquo,60,lt,62,gt,8804,le,8805,ge,8211,ndash,8212,mdash,175,macr,8254,oline,164,curren,166,brvbar,168,uml,161,iexcl,191,iquest,710,circ,732,tilde,176,deg,8722,minus,177,plusmn,247,divide,8260,frasl,215,times,185,sup1,178,sup2,179,sup3,188,frac14,189,frac12,190,frac34,402,fnof,8747,int,8721,sum,8734,infin,8730,radic,8764,sim,8773,cong,8776,asymp,8800,ne,8801,equiv,8712,isin,8713,notin,8715,ni,8719,prod,8743,and,8744,or,172,not,8745,cap,8746,cup,8706,part,8704,forall,8707,exist,8709,empty,8711,nabla,8727,lowast,8733,prop,8736,ang,180,acute,184,cedil,170,ordf,186,ordm,8224,dagger,8225,Dagger,192,Agrave,194,Acirc,195,Atilde,196,Auml,197,Aring,198,AElig,199,Ccedil,200,Egrave,202,Ecirc,203,Euml,204,Igrave,206,Icirc,207,Iuml,208,ETH,209,Ntilde,210,Ograve,212,Ocirc,213,Otilde,214,Ouml,216,Oslash,338,OElig,217,Ugrave,219,Ucirc,220,Uuml,376,Yuml,222,THORN,224,agrave,226,acirc,227,atilde,228,auml,229,aring,230,aelig,231,ccedil,232,egrave,234,ecirc,235,euml,236,igrave,238,icirc,239,iuml,240,eth,241,ntilde,242,ograve,244,ocirc,245,otilde,246,ouml,248,oslash,339,oelig,249,ugrave,251,ucirc,252,uuml,254,thorn,255,yuml,914,Beta,915,Gamma,916,Delta,917,Epsilon,918,Zeta,919,Eta,920,Theta,921,Iota,922,Kappa,923,Lambda,924,Mu,925,Nu,926,Xi,927,Omicron,928,Pi,929,Rho,931,Sigma,932,Tau,933,Upsilon,934,Phi,935,Chi,936,Psi,937,Omega,945,alpha,946,beta,947,gamma,948,delta,949,epsilon,950,zeta,951,eta,952,theta,953,iota,954,kappa,955,lambda,956,mu,957,nu,958,xi,959,omicron,960,pi,961,rho,962,sigmaf,963,sigma,964,tau,965,upsilon,966,phi,967,chi,968,psi,969,omega,8501,alefsym,982,piv,8476,real,977,thetasym,978,upsih,8472,weierp,8465,image,8592,larr,8593,uarr,8594,rarr,8595,darr,8596,harr,8629,crarr,8656,lArr,8657,uArr,8658,rArr,8659,dArr,8660,hArr,8756,there4,8834,sub,8835,sup,8836,nsub,8838,sube,8839,supe,8853,oplus,8855,otimes,8869,perp,8901,sdot,8968,lceil,8969,rceil,8970,lfloor,8971,rfloor,9001,lang,9002,rang,9674,loz,9824,spades,9827,clubs,9829,hearts,9830,diams,8194,ensp,8195,emsp,8201,thinsp,8204,zwnj,8205,zwj,8206,lrm,8207,rlm,173,shy,233,eacute,237,iacute,243,oacute,250,uacute,193,Aacute,225,aacute,201,Eacute,205,Iacute,211,Oacute,218,Uacute,221,Yacute,253,yacute"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_entity_encoding.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: entity_encoding</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: entity_encoding</h1>
</div>
<div class="content">
<p>
This option controls how entities/characters gets processed by TinyMCE. The value can be set to numeric, named or raw. Where numeric is numeric representation such as &quot;&amp;#160;&quot; named is entity names such as &quot;&amp;nbsp;&quot; and raw is &quot;&nbsp;&quot;. The default value of this option is named, if named is used the <a href="option_entities.html">entities</a> option will be used to convert the codes into names.
</p>
<div class="separator"></div>
<h3>Example of usage of the entity_encoding option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>entity_encoding : "raw"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_event_elements.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: event_elements</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: event_elements</h1>
</div>
<div class="content">
<p>
This option should contain a comma separated list of elements thay may have event attributes such as onclick and simmilar. This option is needed since some browsers execute these events while editing content. This option is set to &quot;a,img&quot; default.
</p>
<div class="separator"></div>
<h3>Example of usage of the event_elements option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>event_elements : "a,img,span"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_extended_valid_elements.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: extended_valid_elements</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: extended_valid_elements</h1>
</div>
<div class="content">
<p>
This option is very similar to <a href="option_valid_elements.html">valid_elements</a> the only diffrance between this option and valid_elements is that this one gets added to the existing rule set. This can be very useful if the existing rule set is fine but you want to add some specific elements that also should be valid.
</p>
<div class="separator"></div>
<h3>Example of usage of the extended_valid_elements option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>extended_valid_elements : "img[class|src|border=0|alt|title|hspace|vspace|width|height|align|onmouseover|onmouseout|name]"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

51
www/extras/tinymce2/docs/option_external_image_list_url.html Normal file
View file

@ -0,0 +1,51 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: external_image_list_url</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: external_image_list_url</h1>
</div>
<div class="content">
<p>
This option enables you to have a external list of images this list of images can be generated by a server side page and then inserted into the image dialog windows of TinyMCE. The images can be to internal site images or external URLs.
</p>
<div class="separator"></div>
<h3>Example of usage of the external_image_list_url option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>external_image_list_url : "myexternallist.js"</strong>
});
</pre>
</div>
<div class="separator"></div>
<h3>Example of a external link list file: (myexternallist.js)</h3>
<div class="example">
<pre>
var tinyMCEImageList = new Array(
// Name, URL
["Logo 1", "logo.jpg"],
["Logo 2 Over", "logo_over.jpg"]
);
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

52
www/extras/tinymce2/docs/option_external_link_list_url.html Normal file
View file

@ -0,0 +1,52 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: external_link_list_url</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: external_link_list_url</h1>
</div>
<div class="content">
<p>
This option enables you to have a external list of links this list of links can be generated by a server side page and then inserted into the link dialog windows of TinyMCE. The links can be to internal site documents or external URLs.
</p>
<div class="separator"></div>
<h3>Example of usage of the external_link_list_url option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>external_link_list_url : "myexternallist.js"</strong>
});
</pre>
</div>
<div class="separator"></div>
<h3>Example of a external link list file: (myexternallist.js)</h3>
<div class="example">
<pre>
var tinyMCELinkList = new Array(
// Name, URL
["Moxiecode", "http://www.moxiecode.com"],
["Freshmeat", "http://www.freshmeat.com"],
["Sourceforge", "http://www.sourceforge.com"]
);
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

43
www/extras/tinymce2/docs/option_file_browser_callback.html Normal file
View file

@ -0,0 +1,43 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: file_browser_callback</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: file_browser_callback</h1>
</div>
<div class="content">
<p>
This option enables you to add your own file browser/image browser to TinyMCE. This function is executed each time a user clicks on the &quot;browse&quot; buttons in various dialogs. The format of this callback function is: fileBrowser(field_name, url, type, win) where field_name is the id/name of the form element that the browser should insert it's URL into. The url parameter contains the URL value that is currently inside the field. The type parameter contains what type of browser to present this value can be file, image or flash depending on what dialog is calling the function. The win parameter contains a reference to the dialog/window that executes the function.
</p>
<div class="separator"></div>
<h3>Example of usage of the file_browser_callback option:</h3>
<div class="example">
<pre>
function <strong>myCustomFileBrowser</strong>(field_name, url, type, win) {
// Do custom browser logic
win.document.forms[0].elements[field_name].value = 'my browser value';
}
tinyMCE.init({
...
<strong>file_browser_callback : "myCustomFileBrowser"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_fix_content_duplication.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: fix_content_duplication</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: fix_content_duplication</h1>
</div>
<div class="content">
<p>
This option is available since MSIE has a serious bug where the DOM tree sometimes can include the same node twice. This produces duplication of content when the cleanup process runs. This option is enabled by default and removes any duplicated nodes.
</p>
<div class="separator"></div>
<h3>Example of usage of the fix_content_duplication option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>fix_content_duplication : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_focus_alert.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: focus_alert</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: focus_alert</h1>
</div>
<div class="content">
<p>
This option enables you to specify if a &quot;Editor is not focused&quot; alert message should appear if the user calls tinyMCE.execCommand and havn't selected a editor instance before. This message will normaly not appear unless some integration has been made. Using tinyMCE.execInstanceCommand prevents this from happening since it auto focuses the editor specified. The default value of this option is &quot;true&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the focus_alert option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>focus_alert : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

35
www/extras/tinymce2/docs/option_font_size_classes.html Normal file
View file

@ -0,0 +1,35 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: font_size_classes</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: font_size_classes</h1>
</div>
<div class="content">
<p>Comma separated list of class names that is to be used when the user selects font sizes, this option is only used when the <a href="option_convert_fonts_to_spans.html">convert_fonts_to_spans</a> option is enabled. This list of classes should be 7 items. This option is not used by default, but can be useful if you want to have custom classes for each font size for browser compatiblity.</p>
<div class="separator"></div>
<h3>Example of usage of the font_size_classes option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>font_size_classes : "fontSize1,fontSize2,fontSize3,fontSize4,fontSize5,fontSize6,fontSize7"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

35
www/extras/tinymce2/docs/option_font_size_style_values.html Normal file
View file

@ -0,0 +1,35 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: font_size_style_values</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: font_size_style_values</h1>
</div>
<div class="content">
<p>Comma separated list of style values that is to be used when the user selects font sizes, this option is only used when the <a href="option_convert_fonts_to_spans.html">convert_fonts_to_spans</a> option is enabled. This list of style values should be 7 items. This option is not used by default, but can be useful if you want to have custom CSS values for each font size for browser compatiblity. Defaults to: xx-small,x-small,small,medium,large,x-large,xx-large.</p>
<div class="separator"></div>
<h3>Example of usage of the font_size_style_values option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>font_size_style_values : "xx-small,x-small,small,medium,large,x-large,xx-large"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_force_br_newlines.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: force_br_newlines</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: force_br_newlines</h1>
</div>
<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>.
</p>
<div class="separator"></div>
<h3>Example of usage of the force_br_newlines option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>force_br_newlines : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

35
www/extras/tinymce2/docs/option_force_hex_style_colors.html Normal file
View file

@ -0,0 +1,35 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: force_hex_style_colors</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: force_hex_style_colors</h1>
</div>
<div class="content">
<p>This option enables you to control TinyMCE to force the color format to use hexa decimal instead of rgb strings. It converts for example &quot;color: rgb(255, 255, 0)&quot; to &quot;#FFFF00&quot;. This option is set to true by default since otherwice MSIE and Firefox would differ in this behavior.</p>
<div class="separator"></div>
<h3>Example of usage of the force_hex_style_colors option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>force_hex_style_colors : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_force_p_newlines.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: force_p_newlines</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: force_p_newlines</h1>
</div>
<div class="content">
<p>
This option enables you to disable/enable the creation of paragraphs on return/enter in Mozilla/Firefox. The default value of this option is true.
</p>
<div class="separator"></div>
<h3>Example of usage of the force_p_newlines option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>force_p_newlines : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_force_p_newliness.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: force_p_newliness</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: force_p_newliness</h1>
</div>
<div class="content">
<p>
...
</p>
<div class="separator"></div>
<h3>Example of usage of the force_p_newliness option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>force_p_newliness : ""</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_height.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: height</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: height</h1>
</div>
<div class="content">
<p>
This option gives you the ability to specify the height of the editor in pixels or percent. This height can be very userful to specify if the editor is used in hidden tabs or if the editor area should be bigger than the replaced element. The default value of this option is set to the height of the HTML element TinyMCE replaces for example the pixel height of a textarea.
</p>
<div class="separator"></div>
<h3>Example of usage of the height option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>height : "480"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

42
www/extras/tinymce2/docs/option_init_instance_callback.html Normal file
View file

@ -0,0 +1,42 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: init_instance_callback</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: init_instance_callback</h1>
</div>
<div class="content">
<p>
This option should contain a function name to be executed each time a editor instance is initialized. The format of this function is: initInstance(inst) where inst is the editor instance object reference.
</p>
<div class="separator"></div>
<h3>Example of usage of the init_instance_callback option:</h3>
<div class="example">
<pre>
function <strong>myCustomInitInstance</strong>(inst) {
alert("Editor: " + inst.editorId + " is now initialized.");
}
tinyMCE.init({
...
<strong>init_instance_callback : "myCustomInitInstance"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_inline_styles.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: inline_styles</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: inline_styles</h1>
</div>
<div class="content">
<p>
If you enable the inline styles feature by setting this option to true. Most of the attributes gets converted into CSS style attributes instead. This will make the editor output more XHTML strict compatible.
</p>
<div class="separator"></div>
<h3>Example of usage of the inline_styles option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>inline_styles : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

57
www/extras/tinymce2/docs/option_insertimage_callback.html Normal file
View file

@ -0,0 +1,57 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: insertimage_callback</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>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.
</p>
<div class="separator"></div>
<h3>Example of usage of the insertimage_callback option:</h3>
<div class="example">
<pre>
function <strong>myCustomInsertImage</strong>(src, alt, border, hspace, vspace, width, height, align, title, onmouseover, onmouseout, action) {
var result = new Array();
// Do some custom logic
result['src'] = "logo.jpg";
result['alt'] = "test description";
result['border'] = "2";
result['hspace'] = "5";
result['vspace'] = "5";
result['width'] = width;
result['height'] = height;
result['align'] = "right";
result['title'] = "Some title";
result['onmouseover'] = "";
result['onmouseout'] = "";
return data;
}
tinyMCE.init({
...
<strong>insertimage_callback : "myCustomInsertImage"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

50
www/extras/tinymce2/docs/option_insertlink_callback.html Normal file
View file

@ -0,0 +1,50 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: insertlink_callback</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>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.
</p>
<div class="separator"></div>
<h3>Example of usage of the insertlink_callback option:</h3>
<div class="example">
<pre>
function <strong>myCustomInsertLink</strong>(href, target, title, onclick, action) {
var result = new Array();
// Do some custom logic
result['href'] = "some_page.htm";
result['target'] = "_self";
result['title'] = "Some link title";
result['onclick'] = "";
return data;
}
tinyMCE.init({
...
<strong>insertlink_callback : "myCustomInsertLink"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_invalid_elements.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: invalid_elements</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: invalid_elements</h1>
</div>
<div class="content">
<p>
This option should contain a comma separated list of element names to exclude from the content. Elements in this list will removed when TinyMCE executes a cleanup.
</p>
<div class="separator"></div>
<h3>Example of usage of the invalid_elements option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>invalid_elements : "strong,em"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

42
www/extras/tinymce2/docs/option_language.html Normal file
View file

@ -0,0 +1,42 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: language</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: language</h1>
</div>
<div class="content">
<p>
This option should contain a language code of the language pack to use with TinyMCE. These codes are in <a href="http://www.loc.gov/standards/iso639-2/englangn.html">ISO-639-2</a> format to see if your language is available check the contents of &quot;tinymce/jscripts/tiny_mce/langs&quot;. The default value of this option is &quot;en&quot; for English.
</p>
<p>
If TinyMCE doesn't have a language pack for your language you could always write your own and contribute this back to this project by uploading it as a Patch at <a href="http://sourceforge.net/projects/tinymce/">SourceForge</a>. A description on how to create language packs can be found in <a href="customization_language_packs.html">Language packs</a> section.
</p>
<div class="separator"></div>
<h3>Example of usage of the language option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>language : "en"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

37
www/extras/tinymce2/docs/option_merge_styles_invalid_parents.html Normal file
View file

@ -0,0 +1,37 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: merge_styles_invalid_parents</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: merge_styles_invalid_parents</h1>
</div>
<div class="content">
<p>This option enables you to specify a regexp with elements you want to exclude from parent mergeing. By default style information are attached to the parent element of a selection if all childrent/the whole element contents is selected. For example if you select a whole strong element and select a font size, the font-size style will be applied to the strong element and not with a wrapping style element. But sometimes you want to force a span element, this is where this option comes in to place. This option is set to nothing by default and applies to the font size/face/color and class drop drown lists.</p>
<div class="separator"></div>
<h3>Example of usage of the merge_styles_invalid_parents option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
// Excludes table cells and strong elements from any parent merge operation
<strong>merge_styles_invalid_parents : "^TD|STRONG$"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

54
www/extras/tinymce2/docs/option_mode.html Normal file
View file

@ -0,0 +1,54 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: mode</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: mode</h1>
</div>
<div class="content">
<p>
This option specifies how elements is to be converted into TinyMCE WYSIWYG editor instances. This option can be set to any of the values below.
</p>
<p>
<h3>textareas</h3>
Converts all textarea elements to editors when the page loads.
</p>
<p>
<h3>specific_textareas</h3>
Converts all textarea elements with the a <a href="option_textarea_trigger.html">textarea_trigger</a> attribute set to &quot;true&quot;.
</p>
<p>
<h3>exact</h3>
exact - Converts only explicit elements, these are listed in the <a href="option_elements.html">elements</a> option. These elements can be any kind for example textareas or divs.
</p>
<div class="separator"></div>
<h3>Example of usage of the mode option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>mode : "exact",</strong>
elements : "elm1,elm2"
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_nowrap.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: nowrap</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: nowrap</h1>
</div>
<div class="content">
<p>
This nowrap option enables you to control how whitespace is to be wordwrapped within the editor. This option is set to false by default, but if you enable it by setting it to true editor contents will never wrap.
</p>
<div class="separator"></div>
<h3>Example of usage of the nowrap option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>nowrap : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_object_resizing.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: object_resizing</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: object_resizing</h1>
</div>
<div class="content">
<p>
This true/false option gives you the ability to turn on/off the inline resizing controls of tables and images in Firefox/Mozilla. These are enabled by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the object_resizing option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>object_resizing : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

43
www/extras/tinymce2/docs/option_onchange_callback.html Normal file
View file

@ -0,0 +1,43 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: onchange_callback</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: onchange_callback</h1>
</div>
<div class="content">
<p>
This option should contain a function name to be executed each time contents is modified by TinyMCE. This function is called each time a undo level is added to TinyMCE. The format of this function is: onchange(inst), where inst is the editor instance object reference.
</p>
<div class="separator"></div>
<h3>Example of usage of the onchange_callback option:</h3>
<div class="example">
<pre>
function <strong>myCustomOnChangeHandler</strong>(inst) {
alert("Some one modified something");
alert("The HTML is now:" + inst.getBody().innerHTML);
}
tinyMCE.init({
...
<strong>onchange_callback : "myCustomOnChangeHandler"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

42
www/extras/tinymce2/docs/option_oninit.html Normal file
View file

@ -0,0 +1,42 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: oninit</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: oninit</h1>
</div>
<div class="content">
<p>
This option enables you to specify a function name to be executed when all editor instances has finished it's initialization. This is much like the onload event of a HTML page.
</p>
<div class="separator"></div>
<h3>Example of usage of the oninit option:</h3>
<div class="example">
<pre>
function <strong>myCustomOnInit</strong>() {
alert("We are ready to rumble!!");
}
tinyMCE.init({
...
<strong>oninit : "myCustomOnInit"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

42
www/extras/tinymce2/docs/option_plugins.html Normal file
View file

@ -0,0 +1,42 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: plugins</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: plugins</h1>
</div>
<div class="content">
<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>
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.
</p>
<div class="separator"></div>
<h3>Example of usage of the plugins option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>plugins : "table,contextmenu,paste"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_popups_css.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: popups_css</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: popups_css</h1>
</div>
<div class="content">
<p>
This option enables you to specify the CSS to be used in all popup/dialog windows within TinyMCE this option is set to a CSS file found in the currently used theme by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the popups_css option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>popups_css : "/mypopup.css"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_preformatted.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: preformatted</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: preformatted</h1>
</div>
<div class="content">
<p>
If you enable this feature, whitespace such as tabs and spaces will be preserved. Much like the bahavior of a PRE element. This can be handy when integrating TinyMCE with webmail clients. This option is disabled by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the preformatted option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>preformatted : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

36
www/extras/tinymce2/docs/option_relative_urls.html Normal file
View file

@ -0,0 +1,36 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: relative_urls</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: relative_urls</h1>
</div>
<div class="content">
<p>If this option is set to true, all URLs returned from the MCFileManager will be relative from the specified <a href="option_document_base_url.html">document_base_url</a> if it's set to false all URLs will be converted to absolute URLs. This feature can not be disabled since MSIE and FF modifies the URLs of DOM objects by them self so TinyMCE tries to solve this problem by reconverting them. This option is set to true by default.</p>
<div class="separator"></div>
<h3>Example of usage of the relative_urls option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>relative_urls : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_remove_linebreaks.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: remove_linebreaks</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: remove_linebreaks</h1>
</div>
<div class="content">
<p>
This option controls if linebreak characters should be removed from output HTML or not. This option is enabled by default since many backend systems use newline to &lt;br /&gt; convertion since they used to be plain old textarea based. With this option enables all HTML content will be placed on one line.
</p>
<div class="separator"></div>
<h3>Example of usage of the remove_linebreaks option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>remove_linebreaks : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

37
www/extras/tinymce2/docs/option_remove_script_host.html Normal file
View file

@ -0,0 +1,37 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: remove_script_host</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: remove_script_host</h1>
</div>
<div class="content">
<p>If this option is enabled the protocol and host part of the URLs returned from the MCFileManager will be removed. This option is only used if the <a href="option_relative_urls.html">relative_urls</a> option is set to false. This option is set to true by default.</p>
<p>URL:s will be returned in this format: &quot;/somedir/somefile.htm&quot; instead of the default mode: &quot;http://www.somesite.com/somedir/somefile.htm&quot;.</p>
<div class="separator"></div>
<h3>Example of usage of the remove_script_host option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>remove_script_host : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

45
www/extras/tinymce2/docs/option_save_callback.html Normal file
View file

@ -0,0 +1,45 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: save_callback</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: save_callback</h1>
</div>
<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.
</p>
<div class="separator"></div>
<h3>Example of usage of the save_callback option:</h3>
<div class="example">
<pre>
function <strong>myCustomSaveContent</strong>(element_id, html, body) {
// Do some custom HTML cleanup
html = html.replace(/a/g,'b');
return html;
}
tinyMCE.init({
...
<strong>save_callback : "myCustomSaveContent"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

43
www/extras/tinymce2/docs/option_setupcontent_callback.html Normal file
View file

@ -0,0 +1,43 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: setupcontent_callback</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: setupcontent_callback</h1>
</div>
<div class="content">
<p>
This option enables you to execute custom setup content logic when the editor initializes. The format of this callback is:
setupContent(editor_id, body, doc). Where editor_id is the TinyMCE editor instance id the editor instance object reference can be retrived by using tinyMCE.getInstanceById(editor_id). The body parameter is a reference to the iframes body element and doc is the iframes document element. This option is not used if it's not specified.
</p>
<div class="separator"></div>
<h3>Example of usage of the setupcontent_callback option:</h3>
<div class="example">
<pre>
function myCustomSetupContent(editor_id, body, doc) {
body.innerHTML = "my new content" + body.innerHTML;
}
tinyMCE.init({
...
<strong>setupcontent_callback : "myCustomSetupContent"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_submit_patch.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: submit_patch</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: submit_patch</h1>
</div>
<div class="content">
<p>
This toggle option enables you to turn on/off the auto patching of the submit function in forms. TinyMCE will auto move contents from the iframe to the hidden textarea field if for example a JavaScript uses a form[0].submit() call. This is the same as using the tinyMCE.triggerSave() call. This option is set to true by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the submit_patch option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>submit_patch : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_table_inline_editing.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: table_inline_editing</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: table_inline_editing</h1>
</div>
<div class="content">
<p>
This true/false option gives you the ability to turn on/off the inline table editing controls in Firefox/Mozilla. These controls are somewhat buggy and not redesignable so they are disabled by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the table_inline_editing option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>table_inline_editing : true</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

47
www/extras/tinymce2/docs/option_textarea_trigger.html Normal file
View file

@ -0,0 +1,47 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: textarea_trigger</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: textarea_trigger</h1>
</div>
<div class="content">
<p>
This option enables you to specify the name of the attribute to check if it's value is true/false. If the <a href="option_mode.html">mode</a> option is set to &quot;specific_textareas&quot;, only specific textareas with a attribute by the name of the value of this option gets converted and only if it's set to true. This option defaults to &quot;mce_editable&quot;.
</p>
<p>
If the mode is set to textareas and the textarea trigger attribute value is set to false, these textareas will not be converted.
</p>
<p>
<strong>Notice: This option is deprecated.</strong>
We strongly recommend you to use the <a href="option_editor_selector.html">editor_selector</a>/<a href="option_editor_deselector.html">editor_deselector</a> options instead since they validate with W3C specifications.<strong>
</p>
<div class="separator"></div>
<h3>Example of usage of the textarea_trigger option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>textarea_trigger : "convert_this"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

49
www/extras/tinymce2/docs/option_theme.html Normal file
View file

@ -0,0 +1,49 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme</h1>
</div>
<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.
</p>
<p>
<h3>advanced</h3>
This is the advanced theme of TinyMCE, this theme enables users to add/remove buttons and panels and is a lot more flexible than the simple or default theme. For more information about this themes specific options check the &quot;Advanced theme&quot; configuration section.
</p>
<p>
<h3>simple</h3>
This is the most simple theme for TinyMCE it contains only the basic functions.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme : "advanced",</strong>
theme_advanced_buttons3_add_before : "tablecontrols,separator"
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_theme_advanced_blockformats.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_blockformats</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_blockformats</h1>
</div>
<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.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_blockformats option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_blockformats : "p,h1,h2,h3,h4,h5,h6"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

44
www/extras/tinymce2/docs/option_theme_advanced_buttons_n.html Normal file
View file

@ -0,0 +1,44 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_buttons&lt;1-n&gt;</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_buttons&lt;1-n&gt;</h1>
</div>
<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 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>
A complete reference of all built in buttons and controls can be found in the <a href="reference_buttons.html">button/control reference</a> page.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_buttons&lt;1-n&gt; option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_buttons1 : "separator,insertdate,inserttime,preview,zoom,separator,forecolor,backcolor"</strong>
<strong>theme_advanced_buttons2 : "bullist,numlist,separator,outdent,indent,separator,undo,redo,separator,link,unlink,anchor,image,cleanup,help,code"</strong>
<strong>theme_advanced_buttons3 : "hr,removeformat,visualaid,separator,sub,sup,separator,charmap"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

44
www/extras/tinymce2/docs/option_theme_advanced_buttons_n_add.html Normal file
View file

@ -0,0 +1,44 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_buttons&lt;1-n_add&gt;</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_buttons&lt;1-n_add&gt;</h1>
</div>
<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 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>
A complete reference of all built in buttons and controls can be found in the <a href="reference_buttons.html">button/control reference</a> page.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_buttons&lt;1-n&gt;_add option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_buttons1_add : "separator,insertdate,inserttime,preview,zoom,separator,forecolor,backcolor"</strong>
<strong>theme_advanced_buttons2_add : "bullist,numlist,separator,outdent,indent,separator,undo,redo,separator,link,unlink,anchor,image,cleanup,help,code"</strong>
<strong>theme_advanced_buttons3_add : "hr,removeformat,visualaid,separator,sub,sup,separator,charmap"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

44
www/extras/tinymce2/docs/option_theme_advanced_buttons_n_add_before.html Normal file
View file

@ -0,0 +1,44 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_buttons&lt;1-n_add_before&gt;</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_buttons&lt;1-n_add_before&gt;</h1>
</div>
<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 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>
A complete reference of all built in buttons and controls can be found in the <a href="reference_buttons.html">button/control reference</a> page.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_buttons&lt;1-n&gt;_add_before option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_buttons1_add_before : "separator,insertdate,inserttime,preview,zoom,separator,forecolor,backcolor"</strong>
<strong>theme_advanced_buttons2_add_before : "bullist,numlist,separator,outdent,indent,separator,undo,redo,separator,link,unlink,anchor,image,cleanup,help,code"</strong>
<strong>theme_advanced_buttons3_add_before : "hr,removeformat,visualaid,separator,sub,sup,separator,charmap"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

39
www/extras/tinymce2/docs/option_theme_advanced_container.html Normal file
View file

@ -0,0 +1,39 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_container_&lt;container&gt;</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_container_&lt;container&gt;</h1>
</div>
<div class="content">
<p>
This option should contain buttons/control that you wich to insert into the container, the button names available is the same as in the <a href="option_theme_advanced_buttons_n.html">theme_advanced_buttons_&lt;1-3&gt;</a> option but two extra controls available when this layout option is used these are &quot;mceEditor&quot; and &quot;mceElementpath&quot;. The &lt;container&gt; part of this option should be replaced with a name within the <a href="option_theme_advanced_containers.html">theme_advanced_containers</a> list. 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 value of &quot;RowLayout&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_container_&lt;container&gt; option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_container_somecontainer1 : "bold,italic",</strong>
<strong>theme_advanced_container_somecontainer2 : "strikethrough,cut"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

39
www/extras/tinymce2/docs/option_theme_advanced_container_align.html Normal file
View file

@ -0,0 +1,39 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_container_align</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_container_&lt;container&gt;_align</h1>
</div>
<div class="content">
<p>
This option is used to set the alignment of a specific containerer. The &lt;container&gt; part of this option should be replaced with a name within the <a href="option_theme_advanced_containers.html">theme_advanced_containers</a> list. 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 value of &quot;RowLayout&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_container_&lt;container&gt;_align option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_container_somecontainer1_align : "left"</strong>
<strong>theme_advanced_container_somecontainer2_align : "right"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

39
www/extras/tinymce2/docs/option_theme_advanced_container_class.html Normal file
View file

@ -0,0 +1,39 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_container_&lt;container&gt;_class</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_container_&lt;container&gt;_class</h1>
</div>
<div class="content">
<p>
This option is used to set the class of a specific container. The &lt;container&gt; part of this option should be replaced with a name within the <a href="option_theme_advanced_containers.html">theme_advanced_containers</a> list. 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 value of &quot;RowLayout&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_container_&lt;container&gt;_class option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_container_somecontainer1_class : "someclass",</strong>
<strong>theme_advanced_container_somecontainer2_class : "someotherclass"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_theme_advanced_containers.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_containers</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_containers</h1>
</div>
<div class="content">
<p>
This option should contain a comma separated list of container/panel names. These names are then matched agains the other container options. 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 value of &quot;RowLayout&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_containers option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_containers : "mycontainer1,mycontainer2"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_theme_advanced_containers_default_align.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_containers_default_align</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_containers_default_align</h1>
</div>
<div class="content">
<p>
This option should contain the default container/panel alignment this can be a value of &quot;left&quot;, &quot;center&quot; or &quot;right&quot;. 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 value of &quot;RowLayout&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_containers_default_align option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_containers_default_align : "left"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_theme_advanced_containers_default_class.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_containers_default_class</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_containers_default_class</h1>
</div>
<div class="content">
<p>
This option should contain the default container/panel class name. 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 value of &quot;RowLayout&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_containers_default_class option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_containers_default_class : "myPanelClass"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

49
www/extras/tinymce2/docs/option_theme_advanced_custom_layout.html Normal file
View file

@ -0,0 +1,49 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_custom_layout</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_custom_layout</h1>
</div>
<div class="content">
<p>
This option is used to specify a custom layout manager function. The format of this function is: customLayout(template) where template is the template array within the advanced theme, this function should return a new template array containing the editor HTML in a key called html. 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 value of &quot;RowLayout&quot;.
CustomLayout
template
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_custom_layout option:</h3>
<div class="example">
<pre>
function <strong>myCustomLayout</strong>(template) {
// Make custom layout
template['html'] = "make new layout";
return template;
}
tinyMCE.init({
...
<strong>theme_advanced_custom_layout : "myCustomLayout"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_theme_advanced_disable.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_disable</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_disable</h1>
</div>
<div class="content">
<p>
This option should contain a comma separated list of controls to disable from any toolbar row/panel in TinyMCE.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_disable option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_disable : "bold,italic"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

38
www/extras/tinymce2/docs/option_theme_advanced_fonts.html Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Option: theme_advanced_fonts</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_fonts</h1>
</div>
<div class="content">
<p>
This option should contain a semicolon separated list of font titles and font families separated by =. The titles are the ones that get presented to the user in the fonts drop down list and and the font family names is the string that gets inserted into the font face or fontFamily CSS style.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_fonts option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_fonts : "Arial=arial,helvetica,sans-serif;Courier New=courier new,courier,monospace"</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2005 Moxiecode Systems AB</div>
<br style="clear: both" />
</div>
</body>
</html>

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