Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • osian/sucs-site
  • kais58/sucs-site
  • imranh/sucs-site
  • foshjedi2004/sucs-site
  • gigosaurus/sucs-site
  • matstn/sucs-site
  • ripp_/sucs-site
  • eggnog/sucs-site
  • sucssite/sucs-site
  • elbows/sucs-site
  • realitykiller/sucs-site
  • crox/sucs-site
  • vectre/sucs-site
  • welshbyte/sucs-site
  • paperclipman/sucs-site
15 results
Show changes
Expand all Hide whitespace changes
Inline Side-by-side
Showing
with 0 additions and 1302 deletions
htdocs/js/tinymce/docs/installing.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/license.html deleted 100644 → 0
View file @ 67c8f9e0
This diff is collapsed.
htdocs/js/tinymce/docs/option_accessibility_focus.html deleted 100644 → 0
View file @ 67c8f9e0
<!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_focus</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: accessibility_focus</h1>
</div>
<div class="content">
<p>
If this option is set to true some accessibility focus will available to all buttons, you will be able to tab through them all. If you set this option to false, focus will be placed inside the text area when you tab through the interface.
</p>
<div class="separator"></div>
<h3>Example of usage of the accessibility_focus option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>accessibility_focus : false</strong>
});
</pre>
</div>
</div>
<div class="footer">
<div class="helpindexlink"><a href="index.html">Index</a></div>
<div class="copyright">Copyright &copy; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_accessibility_warnings.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_add_form_submit_trigger.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_add_unload_trigger.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_apply_source_formatting.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_ask.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_auto_focus.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_auto_reset_designmode.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_auto_resize.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_browsers.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_button_tile_map.html deleted 100644 → 0
View file @ 67c8f9e0
<!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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_cleanup.html deleted 100644 → 0
View file @ 67c8f9e0
<!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 built in cleanup functionality. TinyMCE is equipped with powerful cleanup functionality that enables you to specify what elements and attributes are allowed and how HTML contents should be generated. This option is set to true by default, but if you want to disable it you may set it to false. <strong>Notice: It's not recommended to disable this feature.</strong>
</p>
<div class="separator"></div>
<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; 2003-2006 <a href="http://www.moxiecode.com">Moxiecode Systems AB</a></div>
<br style="clear: both" />
</div>
</body>
</html>
htdocs/js/tinymce/docs/option_cleanup_callback.html deleted 100644 → 0
View file @ 67c8f9e0
This diff is collapsed.
htdocs/js/tinymce/docs/option_content_css.html deleted 100644 → 0
View file @ 67c8f9e0
This diff is collapsed.
htdocs/js/tinymce/docs/option_convert_urls.html deleted 100644 → 0
View file @ 67c8f9e0
This diff is collapsed.