remove old tinymce version

This commit is contained in:
Cornelius Weiß 2006-08-21 19:24:18 +00:00
parent ae53106726
commit 9e80148276
896 changed files with 0 additions and 40234 deletions

View File

@ -1,563 +0,0 @@
Version 1.45 RC1 (2005-05-27)
Fixed bug where character map inserted &amp; and &lt;/&gt; when using & < >.
Fixed so paragraphs containing &nbsp; is converted to numeric or raw if entity_encoding is set.
Fixed bug in searchreplace plugin when user tried to search on a empty string or the editor contents was empty.
Fixed repaint/trail graphics issues with images and tables in FF/Mozilla.
Fixed some memory leaks in TinyMCE core and context menu plugin, only MSIE was inflicted by this.
Fixed stange issue where elements sometimes disappeared in MSIE.
Fixed URL convertion problems with onmouseover, onmouseout image urls in advimage plugin.
Fixed URL convertion problems with Flash plugin.
Fixed the experimental Safari support, some features work some doesn't.
Fixed bug where multiple a elements where created when updating links on images in FF/Mozilla.
Fixed bug in importCSS function, was having a meaning less if statement.
Fixed so the contextmenu plugin uses images from the configurated theme instead of the advanced theme.
Fixed so the external_link_list_url/external_image_list_url options can use relative or absolute path.
Fixed so the external_link_list_url/external_image_list_url has a random query parameter to prevent it from cache.
Added new mceInsertRawHTML command, this inserts raw as it is HTML code in the the selected position.
Added paste plain text plugin contributed by Ryan Demmer, converted it into a paste plugin.
Added updated paste plugin contributed by speednet, includes paste directly feature for MSIE.
Added split/merge table cells support, to table plugin and context menus.
Added cut/copy/paste table rows functionality to context menu and table plugin.
Added new mceSetContent command, this does the same as the setContent function.
Added new clear all/new document icon to advanced theme.
Added new remove formatting and select text color icons.
Added new directionality plugin to better support languages that write from right to left.
Added new fullscreen plugin, enables users to toggle fullscreen editing mode.
Added a new template/tutorial plugin to aid people in the development of own plugins.
Removed visual_table_style and replaced it with visual_table_class. [BREAKS COMPATIBLITY].
Renamed urlconvertor_callback option to urlconverter_callback.
Version 1.44 (2005-05-03)
Fixed bug with contextmenu not showing at the correct location in MSIE.
Fixed bug where a error was produced by the Flash plugin if the user reloaded the page in MSIE.
Fixed issue where mceAddControl and mceRemoveControl commands produced a error in MSIE.
Fixed bug when images and flash movies where mixed in the editor produced strange results.
Fixed so trailing / characters isn't removed from URLs.
Fixed so the contextmenu uses a diffrent method of loading it's custom CSS file.
Fixed getAttributes problem, it should read getAttribute.
Fixed so "Edit HTML source" window may be maximized.
Added French eacute entitiy to default entities option.
Added a height CSS value for the element path in advanced themes editor_ui.css since it keept bobbing up and down.
Added updated Polish language pack contributed by Marcin Szymon Sznyra.
Added better window auto resize method for most dialogs.
Added new feature to set what tags are to be left open in valid_elements. Add a + before the element names to enable.
Added nowrap for the editor table cells, sometimes the editors controls wrapped.
Updated German language pack contributed by Krokogras.
Version 1.44 RC2 (2005-04-25)
Fixed bug with host prefixes and port numbers when having relative_urls set to false and remove_script_host set to true.
Fixed bug when site absolute URLs for example /something was converted incorrectly in Firefox/Mozilla.
Fixed bug where the link wasn't auto selected in the drop list in the advanced themes default link dialog.
Fixed bug issue with the flash plugin and croping out characters before and after the movie.
Fixed bug where the editor jumped to top of editor area on enter/return when doctype was set to XML Transitional.
Fixed bug where context menu was appearing in the wrong location if the window was resized.
Fixed bug in the context menu where table properties wasn't working.
Fixed bug where a selectorText exception was trown if the CSS file contained @import or @charset.
Fixed bug where bold/italic/strikethough/underline wasn't selected/unselected in toolbar some times.
Fixed issue with hspace and vspace when having the inline_styles option enabled. Contributed by speednet.
Fixed bug where access denied error was thrown sometimes in MSIE.
Fixed so images without src won't be inserted.
Fixed some issues with width/height fields in the advimage plugin.
Fixed so the contextmenu plugin doesn't appear in MSIE 5.0, now functions with 5.5+.
Added filebrowser icon to mouse over and mouse out fields in the advimage plugin.
Added filebrowser icon to popup field in the advlink plugin.
Added so the triggerSave function gets auto executed when a user calls submit on a form, this can be disabled with the submit_patch option.
Added missing readme.txt file for the context menu plugin.
Added new border and background color fields to table dialog, based on contribution by Neirda. Enable them by the table_color_fields option.
Removed some old outdated items from FAQ.
Version 1.44 RC1 (2005-04-20)
Fixed bug where width/height attributes of a image wasn't stored some times in Firefox/Mozilla.
Fixed bug where P elements where created if a user pressed return/enter within a h1-h6 in Firefox/Mozilla.
Fixed bug where the remove format fuction didn't work some times in MSIE.
Fixed so backspace/delete gets added in one undo level in MSIE (improves performance).
Fixed so the "Could not find element by id or name" alert only shows when the debug option is set to true.
Fixed bug where bold/italic didn't work in Mozilla 1.3.
Fixed bug where width/height of a hidden TinyMCE instance where incorrect.
Fixed so the function layout of classes in tiny_mce_src.js uses prototype keyword instead of TinyMCE_ prefix (reduces size).
Fixed bug where triggerNodeChange produced javascript error some times in MSIE.
Fixed some issues in the Swedish and Spanish language packs.
Fixed bug where first undo level wasn't working correctly.
Fixed so flash plugin loads it's needed CSS data from within the plugin.
Fixed button images and CSS in the simple theme.
Fixed so the simple example shows how to use the simple theme instead of the default theme.
Fixed so cleanup default values can be set to empty. For example alt= generated alt="" on img elements.
Fixed memory leaks in MSIE (circular closure problem) events are now removed in a better way.
Fixed bug where URLs where converted incorrectly if the editor page URL contained / characters.
Fixed bug where table guidlines didn't work correctly when using the build in Mozilla table buttons.
Fixed bug where the Flash plugin was breaking other elements.
Added new contextmenu plugin, this plugin adds a menu if the user right clicks/uses the contextmenu on elements.
Added new multiple configuration support, the init method may now be called multiple times.
Added new remove_linebreaks option, this option is enabled by default and removes all HTML code linebreaks.
Added new behavior to the textarea_trigger option, if mode is textareas and trigger is false those elements will not be converted into editors.
Added new entity_encoding option, enabled user to better control the behavior of how character are converted into entities.
Added new isDirty command to TinyMCEControl, this method returns true if the user has done any modifications to the content.
Added new onchange_callback option, this callback is executed when contents within the editor instance is changed.
Added new init function for themes/plugins this gets called when a editor instance has finished it's setup.
Added new init_instance_callback option this callback is executed when instances are added to the editor.
Added new cleanup option this option enables users to totaly disable the whole cleanup process.
Added new importCSS method to TinyMCE. This method allows plugins and themes to load custom CSS files on initialization.
Added new getSelectedHTML method to TinyMCEControl class, this method returns the currently selected HTML contents.
Added new getSelectedText method to TinyMCEControl class, this method returns the currently selected contents as text.
Added new removeclass behavior to the removeformat button. The current class will be removed if no contents is selected.
Added new queryInstanceCommandValue and queryInstanceCommandState methods.
Added new option button_tile_map, this option contols the usage of button tile maps and is disabled by default.
Version 1.43 (2005-03-06)
Fixed bug with ask option not working at all.
Fixed bug where a "instance is not defined bug" error was produced.
Fixed bug with empty image src produced a error.
Fixed so the simple and default theme used the same CSS style as the advanced theme.
Fixed bug with the relative to absolute URL convertion logic if a empty string was passed used.
Fixed parse error bug with the source editor some servers can't handle XML PI declarations.
Fixed bug issue with HR elements in MSIE, if a specific work pattern where used a runtime error was produced by MSIE.
Fixed bug in the URL convertor logic, port numbers was not correctly handled.
Fixed issue where the cursor was placed before a insert of custom charater or date/time.
Fixed bug where the editor height option didn't work on MSIE.
Fixed bug where a linefeed within a table cell broke the table in Firefox/Mozilla.
Fixed bug where return/enter key after a image removed all content.
Fixed bug where return/enter key sometimes produced nestled P elements.
Fixed bug where the editor was stealing focus on load in MSIE.
Fixed bug where the visual aid logic forces width/height attributes on tables.
Fixed bug where getCSSClasses some times returned null value.
Fixed issue where the lang_insert/lang_update language variables wasn't entity decoded.
Fixed so the image/link/flash drop list gets auto selected thanks goes to Randy Simons and salzbermat.
Fixed so remove formatting button in MSIE removes all classes aswell.
Fixed issue where output contained single br element when the editor area was empty.
Added new %A/%a/%B/%b format chunks to insertdatetime, these insert localized date names such as January.
Added new oninit callback option for TinyMCE this callback is executed when all editor instances been initialized.
Added new preview panel to dialog in the advimage plugin, contributed by Virtuelcom.
Added element class name to element path in the advanced theme.
Updated Canadian French table language pack contributed by Virtuelcom.
Updated the swedish language pack, contributed by Mats Löfström, York Consulting AB.
Version 1.42 (2005-02-14)
Fixed bug with the element path beeing resized if width/height of editor was 100%.
Fixed bug with reloading/flicker of all button images in MSIE if browser cache is disabled.
Fixed backspace/delete bug in Firefox, some times the cursor got stuck.
Fixed bug issues with enter/return key in Firefox/Mozilla.
Fixed bug where copy/paste and drag drop of images/links failed in Firefox/Mozilla if a document_base_url is provided.
Fixed so when relative_urls is set to false it forces absolute URLs for images/links.
Fixed so the _src.js suffix versions of the themes and plugins gets loaded with the tiny_mce_src.js script is used.
Fixed so verify_css_classes option is disabled by default.
Fixed bug where tables where resized when toggling visual aid in Firefox/Mozilla.
Fixed bugs with advhr plugin running in a hidden div element.
Added new auto_focus option that enabled a specific editor area to be focused on startup.
Added a extra argument to the filebrowser callback inorder to get the calling window reference.
Added a new persian (farsi) language pack contributed by Morteza Zafari.
Added new more nice looking icons contributed by Morteza Zafari and Michael Keck. The old icons are available in a separate icon pack.
Added updated Canadian French language pack contributed by Virtuelcom.
Added updated French languahe pack contributed by Laurent Dran.
Added updated German language pack contributed by Tobias Heer.
Added some documentation regarding the layout manager options made by SlyD.
Version 1.41 (2005-01-31)
Added new table plugin, all table code is moved into this plugin [BREAKS COMPATIBLITY].
Added new external_link_list_url/external_image_list_url options for better backend integration.
Added new file_browser_callback option for better backend integration.
Added new layout manager code into the advanced theme, contributed by SlyD.
Added new nowrap option, enables so users may change the word wraping behavior.
Added new Thai language pack contributed by Innozent.
Added obfuscated version of all plugins and themes to reduce over all startup/download time.
Added Simplified Chinese language pack contributed by cube316.
Added a updated Czech language pack thanks to Josef Klimosz.
Fixed issue where anchor elements where closed. This results in browser problems with the outputed HTML.
Fixed bug where the first return key press didn't produce a paragraph in Firefox/Mozilla.
Fixed bug in the searchreplace plugin where replace content sometimes fails in Firefox/Mozilla.
Fixed so all language packs now uses the ISO-639-2 code instead of ISO 3166-1 [BREAKS COMPATIBLITY].
Fixed some issues with the force_br_newlines option in MSIE.
Fixed bug where the backspace or delete key produced BR elements in Firefox/Mozilla.
Fixed bug issue with link and image dialogs of the default theme/simple example.
Fixed some bugs when having the editor hidden in a tab/div, contributed by Ernst de Moor.
Fixed some character issues with the Danish language packs, contributed by someone unknown.
Version 1.40 (2005-01-09)
Added a new default value for the font size drop down, if no font size where found this gets selected.
Added a auto resize window feature, this is enabled by default but can be disabled with a window argument.
Added a new print plugin, prints the current editor contents to a printer.
Added a new searchreplace plugin, adds a search, searchnext and replace button.
Fixed bug issue where buttons didn't display correctly on some Firefox installations.
Fixed issue with value and type attributes of input elements getting lost in cleanup on MSIE.
Fixed so that the getEditorInstance command is public, returns a TinyMCEControl by id.
Fixed issue where "true" and "false" string wasn't treated as booleans in TinyMCE init options.
Fixed so cursor/mousepointer allways remains a arrow in all themes when rolling over buttons.
Fixed the popup windows so they are mode "modal" in Mozilla/Firefox.
Fixed so the ask question is displayed when elements are focused with the tab key.
Fixed so the ask option works when mode option is set to exact.
Fixed issue with visualaids on tables not working correctly when the user uses the tab key in Firefox/Mozilla.
Fixed some bugs with the mceSetCSSClass class command and the element path.
Fixed a new version of the mceInsertContent command.
Fixed so the auto_cleanup_word option is disabled by default.
Removed the langs of the zoom plugin, it now uses + instead of the "zoom" word.
Version 1.391 (2005-01-04)
Fixed major spacebar bug in MSIE, spacebar was disabled.
Version 1.39 (2005-01-04)
Updated the Flash plugin with a new version, contributed by jamesw.
Added new setWindowArg function, useful if plugins are to call other plugins.
Added new save plugin, this plugin adds a save/submit form button to tinyMCE, contributed by SlyD.
Added new hilite color support, sets a background-color style on the selected text.
Added new variable replacement popup URLs, check the openWindow function documentation for details.
Added new force_p_newlines option, forces P elements on return/enter key in Mozilla/Firefox.
Added new theme_advanced_path_location, adds a element path list.
Added new theme_advanced_toolbar_align option, defaults to center.
Added new Portuguese translation contributed by José Pedro Pereira.
Added new mceSelectNode and mceSelectNodeDepth commands.
Added new add_unload_trigger option, this adds a unload triggerSave call. Enabled by default.
Added am/pm time format to the insertdatetime plugin.
Fixed font color and size attribute bug, contributed by Vincent FIACK.
Fixed className undefined bug, Firefox/Mozilla produced a console error sometimes.
Fixed so mceSetCSSClass command may be applied to all sorts of elements.
Fixed so anchor elements can be removed by setting the anchor name to nothing.
Fixed typing performance some in Firefox/Mozilla, removed some nodechange triggers.
Fixed so the zoom plugin is invisible in MSIE 5.0, since zoom isn't available in that browser.
Fixed bug with the emotions plugin in MSIE 5.0, it was opening a new window.
Fixed so contents stay within the editor if the user hits the back/forward buttons.
Fixed bug where the window.name property was set to the image name.
Fixed so anchors links within the same page are made relative when relative_urls are set to false.
Updated the advanced theme so most of the images are loaded from a tiled image, improves loading time.
Updated the Swedish language pack, contributed by Martin.
Updated the readme.txt in the advlink plugin, was some problems with the valid_elements.
Updated the default CSS for the advanced theme some, added button backgrounds to look like office2k.
Version 1.38 (2004-11-28)
Added new textarea field for form elements when debug mode is enabled, contributed by Michael Keck.
Added new spacer item support for the theme_advanced_buttons<n> options, contributed by Michael Keck.
Added new selection borders for images and hr elements, contributed by Michael Keck.
Added new advhr plugin, this plugin handles advanced settings on HR elements, contributed by Michael Keck.
Added new german language pack for the preview plugin, contributed by Michael Keck.
Added new word wrap and source formatting to the source editor, contributed by Michael Keck.
Added new updated charmap, contributed by Michael Keck.
Added new flash plugin that enabled flash movied to be handled, contributed by Michael Keck.
Added the old cut/copy/paste commands to the advanced theme, these are not visible by default.
Added new theme_advanced_buttons<N>_add_before option to advanced theme.
Added new "update" button title for a popup windows.
Added new zoom prefix language variable to the zoom plugin.
Added new entities option, that enables you to config entity code to name convertion.
Added new custom cleanup possibility to plugins.
Added new cleanup_callback option, adds the possibilty to add custom cleanup logic.
Added new Norwegian language pack, contributed by Sten Aksel Heien.
Added new Korean language pack, contributed by Setzer Gabbiani.
Fixed the layout of the color picker, contributed by Michael Keck.
Fixed so the preview plugin doesn't include the any toolsbars in preview popup window, contributed by Michael Keck.
Fixed bug where anchors elements was treated as links.
Fixed so all popup windows are modal dialogs in MSIE.
Fixed bug where the word "null" sometimes appares in HTML after cleanup in Firefox/Mozilla.
Fixed bug where form elements with missing name attributes produced errors.
Fixed some default value bugs and issues with the new advlink plugin.
Fixed the link/image dialog sizes in the SE language pack.
Fixed the content duplication bug, it seems to be fixed anyway, if not please let me know.
Fixed bug where plugin handleNodeChange extentions broke the theme function.
Version 1.37 (2004-11-12)
Added new mceResetDesignMode command that can be used when the editor is placed in tabs.
Added new updated Italian language pack thanks goes to "Fabrix Xm" for the contribtion.
Added new greek language pack thanks goes to "Jacaranda Bill" for the contribution.
Added new french language pack thanks goes to "Pat Boens" for the contribution.
Added new russian language pack thanks goes to "Roman Filippov" for the contribution.
Added new updated Dutch language pack thanks goes to Arnoud van Delden and Ernst de Moor for the contribution.
Added new convert_newlines_to_brs option, that enables newlines to be converted to br elements.
Added new custom_undo_redo_keyboard_shortcuts option, enables keyboard shortcuts to be enabled/disabled.
Added new auto_reset_designmode option, thats resets the design mode when a editor instance is focused.
Added new form reset handler, resets the contents of TinyMCE areas when the onreset event is trigged.
Added new skip_cleanup parameter to triggerSave, this parameter is optional and defaults to false.
Added new lang_underline_img language variable to all themes.
Added new title attribute to all images, enables tooltips in Mozilla and Firefox.
Added new insert and cancel CSS id's for all submit and cancel buttons.
Added new full featured example that includes all available plugins and buttons.
Added new advlink and advimage plugins to TinyMCE, these are more advanced link and image tools. Contributed by Michael Keck.
Added new parameters to insertImage and insertLink commands. Contributed by Michael Keck.
Added updated compatiblity chart, includes a matrix table thanks goes to Ernst de Moor.
Added new insert image icon contributed by Arnoud van Delden and Ernst de Moor.
Added window focus on all popup windows, contributed by Arnoud van Delden and Ernst de Moor.
Fixed some issues with the char map added some characters and removed duplicate ones, contributed by Arnoud van Delden and Ernst de Moor.
Fixed the insert row icon, rotated it 180 degrees, contributed by Arnoud van Delden and Ernst de Moor.
Fixed the visual aid icon, made it a bit darker. Contributed by Arnoud van Delden and Ernst de Moor.
Fixed some issues with entity encoding in source editor aswell as in core cleanup code.
Fixed bug where the auto import CSS feature imported invalid CSS rules with : or spaces.
Fixed bug where unnecessary entity encoding of characters was done.
Fixed the window sizes some to better function on MSIE with SP2.
Fixed some issued with the auto word cleanup feature, fixes some issued with content duplication.
Fixed bug that made the editor to throw weird error when HTML code includes <!a or <!/a> content.
Fixed bug where the style attribute was returned on images in source output even if it was disabled.
Fixed issue where the UI form elements of TinyMCE was submitted with the form submit.
Version 1.36 (2004-10-19)
Added a newly modified version of the German language pack from "krokogras".
Added auto resizing to popup windows with the same name.
Added example page for the plugin_preview_pageurl option in the preview plugin.
Fixed issue with link button auto enable/disable feature when content selection was made with the keyboard.
Fixed bug where events wasn't handled correctly in MSIE 5.5 and some 6.0 versions.
Fixed so align on images gets set as float style when the inline_styles option is enabled.
Fixed so solid border style isn't applied on elements with a border when the inline_styles option is enabled.
Fixed some issues with tables and the inline_styles option.
Fixed back button issue with MSIE, iframes was placed in browser history.
Version 1.35 (2004-10-13)
Added so that whitespace gets stripped in plugin and theme_advanced_buttons options.
Added custom plugin_preview_pageurl option to preview plugin.
Added Canadian French language packs for the new plugins, contributed by Virtuelcom.
Added new theme_advanced_blockformats option.
Added new title support to advanced theme link dialog.
Added new Ctrl+B/I/U keyboard shortcuts for Firefox.
Added Polish language pack contributed by "revyag".
Added Taiwanese language pack contributed by "Jim Kou".
Added updated German language pack contributed by "Krokogras".
Fixed some issues with ieSpell including better language support.
Fixed bug with default value in valid_elements not working in Firefox some times.
Fixed bug when focusing links without selecting any characters.
Fixed some typos in Swedish language pack.
Fixed bug with content selection and link button auto enable/disable feature.
Fixed bug issue when "theme_advanced_buttons<N>" options where left empty.
Fixed various bugs with absolute URLs.
Version 1.34 (2004-10-03)
Added new insertdatetime plugin, inserts date/time in various formats.
Added new preview plugin, previews the HTML page in a new window.
Added new zoom plugin, adds the possibility zoom the editor in MSIE.
Added new emotions plugin, adds the possibility to add smileys.
Fixed so that TinyMCE functions on MSIE 5.0 again.
Fixed so that TinyMCE functions better on Mozilla 1.3.
Fixed so that the cursor doesn't jump to the top when setting styles.
Fixed bug with STRONG and EM elements wasn't handled correctly in Firefox.
Optimized the key handling some, gives better typing performance.
Removed key down statusbar debug info.
Version 1.33 (2004-09-29)
Removed the need of loading blank.html, iframes are now created dynamicly.
Fixed bug when selecting tables, MSIE was casting errors.
Fixed bug with pluginurl variable.
Fixed bug when tinyMCE.selectedElement error was cast in Mozilla.
Added new Arabic language pack contributed by Hani Suleiman.
Added "lang_dir" support to language packs like Arabic.
Version 1.32 (2004-09-25)
Added new ieSpell plugin, only works in MSIE.
Added new "theme_advanced_buttons<N>_add" option.
Added new importPluginLanguagePack function.
Added new Danish language pack contributed by Jan Moelgaard.
Added updated German language pack contributed by Christopher Müller.
Added new any_selection to handleNodeChange callback.
Modified so link/unlink is dimmed if nothing is selected.
Fixed bug when deleting images in Firefox.
Changed the plugin location to a new plugin directory.
Renamed the "theme_plugins" option to "plugins".
Version 1.31 (2004-09-18)
Added Canadian French language pack, contributed by Virtuelcom.
Added so link/unlink buttons gets selected when user enters a link element.
Fixed URL bug when drag dropping/copy pasting images in Mozilla.
Fixed so mso style attribs don't get trimmed if auto_cleanup_word option is set to false.
Fixed bug with text alignment buttons.
Fixed bug with CSS auto import function in MSIE.
Fixed initialization bugs and issues.
Version 1.30 (2004-09-10)
Fixed bug issue where the editor was stealing focus from location bar.
Fixed bug issue with absolute aligned images lost focus when using tools.
Fixed bug #1025483, Url converting broken.
Added ability to send command values in advanced theme button list, contributed by someone helpfull.
Added new cleanup_on_startup option, to increase startup speed.
Added new inline_styles partly based on a contribution by Victor Nilsson.
Added new named anchor support.
Added custom_undo_redo_levels option.
Version 1.29 (2004-09-08)
Added new getEditorId function, to retrive the editor id of a form element.
Readded so cleanup is automaticly executed on editor startup in MSIE.
Added some various cleanup fixes for MS Word HTML.
Added new auto_cleanup_word option, enabled auto MS Word HTML cleanup on paste events.
Fixed parameter issue with insertImage function. Bug #1022863.
Fixed bug #1022874, Where the small theme had underline command on strikethrough button.
Fixed some bugs with table commands.
Fixed bug #1023204, mceRemoveControl brings back the old HTML.
Fixed bug issue with tinyMCE.selectedInstance in Mozilla.
Fixed bug issue with Mozilla not saving content.
Version 1.28 (2004-09-04)
Added new Finnish language pack thanks to Urho Konttori.
Added new rowseparator as a possible value of the theme_advanced_buttons<n> options.
Added new theme_advanced_toolbar_location option.
Added new uid variable option to valid_elements. (Generates unique IDs)
Added new "directionality" option to support languages like Arabic.
Added new character map button/window.
Added new guidelines/visual aid toggle button.
Reduced the source of the advanced theme some, and added some better comments.
Separated the default theme in to files aswell.
Removed source area size options and made source editor resizable instead.
Increased the default width and height of the source editor.
Fixed bug where image width/height default to 0x0 if these attributes wasn't defined.
Fixed some bug issues with MSIE 5.5.
Version 1.27 (2004-08-29)
Added new cleanup logic, with new options and smarter behavior.
Added new "trim_span_elements" option (removed unneeded span elements).
Added new "verify_css_classes" option (verifies so class attributes contain a valid class).
Added new "verify_html" option (enables/disabled verification of elements and attributes).
Added new value verification type to "valid_elements" option.
Added new simple wildcard support in "valid_elements" option.
Added class as a valid attribute to table elements by default.
Added so non existent classes gets removed HTML output.
Added fix for &nbsp; entities, so they get converted correctly.
Added new class select box in table dialog.
Added hr as a default valid element.
Fixed some issues with the language packs.
Fixed some weird bugs and issues with hr elements.
Fixed bug where Mozilla was casting exceptions on keypress.
Version 1.26 (2004-08-25)
Added a better way to create theme popup windows (External files).
Added new getWindowArg function, returns window arguments in theme popups.
Modified the advanced theme to adopt the new theme popup idea.
Fixed critical Mozilla bug, where the editor didn't work at all some times.
Fixed bug with auto CSS class import feature running on Firefox.
Version 1.25 (2004-08-22)
Added new format select box in advanced theme (Can be disabled).
Added new "theme_advanced_disable" option to advanced theme.
Added some new elements to default list of valid elements (Format select box elements).
Added new font face, forecolor and font size support, these are not enabled by default.
Added new "mceAddControl" command, enables users to dynamicly add editors.
Added new execInstanceCommand function, check the documentation for details.
Added new "mceSetAttribute" command.
Modified the themes so that the focus alert doesn't popup as often as before.
Modified the "mceRemoveControl" command so it can handle element id aswell as editor ids.
Fixed some bugs and issues with the new custom undo/redo logic.
Fixed weird Mozilla bug #997860.
Version 1.24 (2004-08-17)
Modified so that span with CSS classes that don't exists get removed.
Added new "custom_undo_redo" option, this option is enabled by default.
Added new "fix_content_duplication" option, that fixes some MSIE content duplication issues.
Added new "mceFocus" command, that changes focus to the specified editor instance.
Added new "mceReplaceContent" command, that enables users to replace the current selection.
Fixed so styles including spaces doesn't get listed in style selection box.
Fixed bug with form element names and exact mode in Mozilla.
Fixed so tiny_mce_src.js can be used aswell as tiny_mce.js.
Converted some of the language packs to better support unicode.
Version 1.23 (2004-07-31)
Modified the mceSetCSSClass command to address bug #997071.
Added new Hungarian language pack thanks to 2XP.
Added new callback "setupcontent_callback" check the manual for details.
Fixed bug #994506, where empty theme_plugins option generated a 404 error.
Fixed bug #999332, where image properties wasn't removed if the user deleted the image.
Version 1.22 (2004-07-19)
Fixed bug #989846, Image resize bug.
Changed so that style attribute values get converted to lowercase in MSIE.
Changed so the alignment called "middle" is "center" in table properties.
Fixed so visual aids work correctly after using the source editor.
Fixed some issues with anchor links.
Fixed so that javascript: links can be used.
Added width/height options for the advanced source editor.
Fixed bug issue with URL:s containing quotes or single quotes.
Fixed so that document_base_url can point to another domain.
Version 1.21 (2004-07-12)
Added new "theme_plugins" option, check the manuals for details.
Added new "execCommand" plugin extention possibility.
Added new "buttons<n>" config options to the advanced theme.
Added new "mceRemoveControl" command.
Added Spanish language pack thanks to "Alvaro Velasco".
Fixed first click bug.
Fixed so CSS url:s can be absolute.
Updated the FAQ regarding the Cut/Copy/Paste issue.
Version 1.20 (2004-07-05)
Fixed bug issue #983257, JS runtime error when template contains no controls.
Removed cut/copy/paste commands and icons due to security reasons in Mozilla.
Added Czech language pack, thanks goes to "Pavel Novák" for the contribution.
Fixed minor bug regarding empty attributes.
Fixed so the "extended_valid_elements" overrides previous declarations.
Version 1.19 (2004-06-28)
Fixed focus bug that appared on Linux version of Mozilla.
Fixed major bug issues with some Firefox/Firebird versions on Linux.
Fixed minor visual aid bugs on tables.
Fixed minor bugs with table commands.
Fixed scroll issue in HTML source windows on Mozilla/Linux.
Added a compatiblity chart to the manuals.
Version 1.18 (2004-06-20)
Added new option "remove_script_host".
Some minor fixes to the mceInsertContent command.
Fixed some issues with visual aids for tables.
Fixed strange focus bug in MSIE.
Updated some of the documentation.
Version 1.17 (2004-06-16)
Fixed bug, #972666 - Doesn't save edits when id != name.
Added more Italian, user manuals. Thanks goes to "Fabrix Xm".
Added Dutch language pack thanks to "Meint Post".
Modified the MSIE version of mceInsertContent command.
Version 1.16 (2004-06-14)
Added new table dialog and TinyMCE_<theme>_getInsertTableTemplate template function.
Added auto class import feature and Italian language pack thanks goes to "Lorenzo Pavani".
Added border, alignment, vspace, hspace, width, height fields to the image properties dialog in advanced theme.
Updates advanced theme help pages for Swedish and English.
Fixed some minor issues with the mceSetCSSClass command.
Fixed minor MSIE bug in built in default URL convertor.
Fixed some image alignment issues.
Fixed support for site root script paths like src="/jscripts/tiny_mce.js".
Removed the use of "TinyMCE_advanced_cssClasses" from "advanced" theme.
Modified the default value of "valid_elements" to include table align and class as valid attributes.
Modified the default value of "valid_elements" to set img border attribute to 0 by default instead of by force.
Modified so that popup windows gets centered on screen.
Version 1.15 (2004-06-09)
Added new "advanced" theme, that adds some new functions.
Added new public js functions "getContent, setContent, applyTemplate, openWindow".
Added new custom command "mceSetCSSClass", that sets css class of the selection.
Added new custom command "mceInsertContent", that inserts HTML content.
Added class attributes to some of the elements in the default value of "valid_elements".
Added ability to have theme specific language packs by the js function "importThemeLanguagePack".
Added more documentation to the usage and themes sections.
Added table support, with custom commands and in advanced theme.
Modified the advanced example to include the new advanced theme.
Fixed tooltips for buttons in Mozilla.
Version 1.14 (2004-06-07)
Added new conversion possibility to save callback.
Added some more usage documentation.
Fixed some issues will updateContent function in Mozilla.
Fixed some issues with relative paths.
Fixed small Mozilla issue with visual aids.
Fixed so that the default theme sets image border to 0.
Fixed bug #968079, Removing editor buttons in template can cause errors.
Version 1.13 (2004-06-04)
Fixed critical bug where the editor didn't work at all in MSIE.
Fixed bug where table visual aids didn't work in Mozilla.
Version 1.12 (2004-06-03)
Added updateContent function thanks to "Jürgen Baute" contribution.
Added documentation of the diffrent public javascript functions of tinyMCE.
Fixed bug #965615, Empty editor content returns "<br />" as value after cleanup.
Fixed bug where Bold and Italic didn't work correctly in Mozilla.
Version 1.11 (2004-06-01)
Added new option "document_base_url", it's used when converting absolute URLs to relative ones.
Added so that align button sets the align attribute of selected images.
Fixed bug when / was passed within query string to the editors page.
Fixed bug #961041, Image attributes are not removed.
Version 1.1 (2004-05-26)
Fixed bug #960112 JavaScript error when opening image window.
Fixed bug #926644 Multiple forms with elements having the same name failed.
Added function so that "specific_textareas" mode handles the "ask" option.
Added new option "focus_alert", to remove annoying focus alert message.
Version 1.09 (2004-05-24)
Added new option "extended_valid_elements", this option adds extra elements to the "valid_elements" list.
Fixed bug #958637, Resized images are displayed in original size
Fixed bug #958942, Bug on realitive_urls (Bug with absolute URLs to insertlink_callback, insertimage_callback callbacks)
Fixed bug #958498, Unable to change Bold and italic text in Mozilla.
Version 1.08 (2004-05-21)
Added new attributes "border, hspace, vspace, width, height, align" to the getInsertImageTemplate theme function.
Added new relative_urls option, this new feature converts all absolute URLs to relative URLs and it's on by default.
Fixed bug #956007, the CSS theme URL:s was allways pointing to the default theme.
Fixed bug where enter/return key produced a error in the insert link popup window form. (This was done in the default template)
Fixed bug #957681, Could not delete text without first adding character bug in Mozilla.
Version 1.07 (2004-05-10)
Added experimental support for option "force_br_newlines" to address bug #922416 and feature request #936270.
Fixed bug with mailto: links.
Version 1.06 (2004-04-15)
Added new German language pack. Thanks goes to "Simon Rupf" for the contribution.
Added new German/Swedish bold/italic language specific icons to both default and simple theme.
Added new Swedish documentation.
Version 1.05 (2004-04-02)
Added new Italian language pack and documentation. Thanks goes to "Fabrix Xm" for the contribution.
Fixed missing "lang_help_desc" definition in UK and SE langpacks.
Added better documentation for the "valid_elements" option and it's format.
Added new "preformatted" option to address feature request #927948.
Added browser checker so that the script don't break on non compatible browsers.
Fixed bug #926639, now the editor instance gets resized if a width/height is specified in %.
Added new simple theme, this theme has only basic functions.
Version 1.04 (2004-03-30)
Fixed bug when insertLink and insertImage function didn't use the url_convertor callback.
Fixed MSIE bug when images was 32x32 on initialization on slow connections.
Fixed bug that made request on images with wrong path, produced some 404 error in webserver logs.
Fixed MSIE bug where users could add images outside of the editor scope.
Version 1.03 (2004-03-26)
Added new "add_form_submit_trigger" this option is default and is added on all document forms within the page. To address bug #923362
Moved javascript sourcecode file to "jscripts/tiny_mce/tiny_mce_src.js".
Added new obfuscated version of tinymce to reduce size of script.
Added some performance boosting code to the switchClassSticky function.
Removed the "autosave" option, this is no longer needed and is replaced with "add_form_submit_trigger" or triggerSave call.
Fixed undo bug in MSIE.
Removed some unused eventhandlers results in better performance.
Version 1.02 (2004-03-26)
Added new handleNodeChange callback to themes.
Fixed some bugs regarding events and themes function checks.
Fixed bug issue when user focused nodes with keyboard.
Version 1.01 (2004-03-12)
Added some more documentation.
Added new "visual" option to editor.
Fixed bug on empty P elements.
Fixed bug on table width/height.
Version 1.0 (2004-03-11)
Added new "debug" option and fixed some path issues.

View File

@ -1,41 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,84 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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 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.8</td>
<td>OK</td>
<td>OK</td>
</tr>
<tr>
<td>Mozilla 1.7.7</td>
<td>OK</td>
<td>OK</td>
</tr>
<tr>
<td>Firefox 1.0.4</td>
<td>OK</td>
<td>OK</td>
</tr>
<tr>
<td>Firefox 1.0.3</td>
<td>OK</td>
<td>OK</td>
</tr>
<tr>
<td>Safari 2.0 (412)</td>
<td>&nbsp;</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>

View File

@ -1,81 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,145 +0,0 @@
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;
}

View File

@ -1,47 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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 two kinds of language packs one is the general one shared by all themes these are located in the &quot;jscripts/tiny_mce/langs&quot; directory the other optional one is theme specific language packs these are contained in &quot;jscripts/tiny_mce/themes/&lt;some theme&gt;/langs&quot;.
</p>
<p>
<div class="example">
<pre>
tinyMCELang['lang_cut_desc'] = 'Cut (Ctrl+X)';
tinyMCELang['lang_copy_desc'] = 'Copy (Ctrl+C)';
tinyMCELang['lang_paste_desc'] = 'Paste (Ctrl+P)';
</pre>
</div>
</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.
</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>

View File

@ -1,243 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>_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>

View File

@ -1,423 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,86 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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 website.</p>
<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 "<a href="option_valid_elements.html">valid_elements</a>" and "<a href="option_extended_valid_elements.html">extended_valid_elements</a>" 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 configururation options to battle this issue, study the configuration options in details.</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 behaviour 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>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 website <a href="http://www.fsf.org/" target="_blank">here</a></p>
</div>
<div class="separator"></div>
<h2>Are there any restrictions to useing 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 addons 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 avalible 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 aggreement. 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> webbsite. 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.moxiedcode.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>

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.7 KiB

View File

@ -1,43 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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_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>

View File

@ -1,37 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>
<p>
<form method="post">
<textarea name="content" cols="50" rows="15">This is some content that will be editable with TinyMCE.</textarea>
</form>
</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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.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>
<p>
<form method="post">
<textarea name="content" cols="50" rows="15">This is some content that will be editable with TinyMCE.</textarea>
</form>
</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>

View File

@ -1,54 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>
<p>
<form method="post">
<textarea name="content" cols="85" rows="15">This is some content that will be editable with TinyMCE.</textarea>
</form>
</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>

View File

@ -1,45 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>
<p>
<form method="post">
<textarea name="content" cols="85" rows="15">This is some content that will be editable with TinyMCE.</textarea>
</form>
</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>

View File

@ -1,122 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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 compatiblity</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">website.</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 website</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 website.</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 website</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>

View File

@ -1,465 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: auto_cleanup_word</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: auto_cleanup_word</h1>
</div>
<div class="content">
<p>
If you set this option to true, TinyMCE will try to auto remove some weird Word HTML when a user pastes content. This feature is disabled by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the auto_cleanup_word option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>auto_cleanup_word : 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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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;false&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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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.
</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>

View File

@ -1,72 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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 to use instead of the build in content CSS. This CSS file is the one used within the editor. 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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,36 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,58 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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"</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,51 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,52 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,43 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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.
</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,42 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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 option is set to false by default since I think using classes is a better approach.
</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>

View File

@ -1,57 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,50 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,42 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,54 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,43 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,42 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,42 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,36 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,37 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,45 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,43 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,41 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>
<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>

View File

@ -1,54 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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;default&quot;. TinyMCE has three build in themes and these are described in greater detail below.
</p>
<p>
<h3>default</h3>
This is the default theme of TinyMCE if no theme option is specified this one will be used for rendering TinyMCE editor instances. This theme contains some of the most common functions.
</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,47 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: theme_advanced_buttons&lt;1-3&gt;</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_buttons&lt;1-3&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-3 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>
<h3>These are the build in buttons/controls that the advanced theme has.</h3>
bold,italic,underline,strikethrough,justifyleft,justifycenter,justifyright,justifyfull,styleselect,formatselect
bullist,numlist,outdent,indent,undo,redo,link,unlink,anchor,image,cleanup,help,code
hr,removeformat,visualaid,sub,sup,charmap,separator
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_buttons&lt;1-3&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>

View File

@ -1,47 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: theme_advanced_buttons&lt;1-3_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-3_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-3 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>
<h3>These are the build in buttons/controls that the advanced theme has.</h3>
bold,italic,underline,strikethrough,justifyleft,justifycenter,justifyright,justifyfull,styleselect,formatselect
bullist,numlist,outdent,indent,undo,redo,link,unlink,anchor,image,cleanup,help,code
hr,removeformat,visualaid,sub,sup,charmap,separator
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_buttons&lt;1-3&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>

View File

@ -1,47 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: theme_advanced_buttons&lt;1-3_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-3_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-3 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>
<h3>These are the build in buttons/controls that the advanced theme has.</h3>
bold,italic,underline,strikethrough,justifyleft,justifycenter,justifyright,justifyfull,styleselect,formatselect
bullist,numlist,outdent,indent,undo,redo,link,unlink,anchor,image,cleanup,help,code
hr,removeformat,visualaid,sub,sup,charmap,separator
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_buttons&lt;1-3&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>

View File

@ -1,39 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,39 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,39 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,49 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<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>

View File

@ -1,39 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: theme_advanced_layout_manager</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_layout_manager</h1>
</div>
<div class="content">
<p>
This option enables you to switch button and panel layout functionality. There are three diffrent layout manager options
SimpleLayout that is the default layout manager, RowLayout that is the more advanced manager and finaly CustomLayout that executes a custom layout manager function. Each of these layout managers have diffrent options and can be configurated in diffrent ways. This option is only available if the advanced theme is used.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_layout_manager option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_layout_manager : "RowLayout"</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: theme_advanced_path_location</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_path_location</h1>
</div>
<div class="content">
<p>
This option enables you to specify where the element path should be located. This option can be set to &quot;top&quot;, &quot;bottom&quot; or &quot;none&quot;. The default value is set to &quot;none&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 default value of &quot;SimpleLayout&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_path_location option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_path_location : "bottom"</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: theme_advanced_source_editor_height</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_source_editor_height</h1>
</div>
<div class="content">
<p>
This option is used to define the height of the source editor dialog. This option is set to 400 by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_source_editor_height option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_source_editor_height : "600"</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: theme_advanced_source_editor_width</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_source_editor_width</h1>
</div>
<div class="content">
<p>
This option is used to define the width of the source editor dialog. This option is set to 500 by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_source_editor_width option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_source_editor_width : "700"</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: theme_advanced_styles</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_styles</h1>
</div>
<div class="content">
<p>
This option should contain a semicolon separated list of class titles and class names separated by =. The titles are the ones that get presented to the user in the styles drop down list and and the class names is the classes that gets inserted. If this option isn't defined TinyMCE auto imports the classes from the content CSS.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_styles option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_styles : "Header 1=header1;Header 2=header2;Header 3=header3;Table Row=tableRow1"</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: theme_advanced_toolbar_align</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_toolbar_align</h1>
</div>
<div class="content">
<p>
This option enables you to specify the alignment of the toolbar, this value can be left, right or center the default value is center. 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>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_toolbar_align option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_toolbar_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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: theme_advanced_toolbar_location</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: theme_advanced_toolbar_location</h1>
</div>
<div class="content">
<p>
This option enables you to specify where the toolbar should be located. This option can be set to &quot;top&quot; or &quot;bottom&quot;. The default value is set to &quot;bottom&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 default value of &quot;SimpleLayout&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the theme_advanced_toolbar_location option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>theme_advanced_toolbar_location : "top"</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: trim_span_elements</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: trim_span_elements</h1>
</div>
<div class="content">
<p>
This option turns on/off the span auto removal functionality. Unneeded span element will be removed for example &lt;span class=&quot;someclass&quot;&gt;&lt;span class=&quot;someclass&quot;&gt;content&lt;/span&gt;&lt;/span> will be turned into &lt;span class=&quot;someclass&quot;&gt;content&lt;/span&gt;. This option is set to true by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the trim_span_elements option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>trim_span_elements : 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>

View File

@ -1,46 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: urlconverter_callback</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: urlconverter_callback</h1>
</div>
<div class="content">
<p>
This option enable you to add your own URL converter logic. This option should contain a JavaScript function name. The format of this converter function is: URLConverter(url, node, on_save). There URL is the URL string to convert, node is the element that contains the URL that is to be converted this parameter may be set to null if there is no element for the URL and on_save is set to true when contents is to be extracted from the editor for example when the user submits the HTML form. This function should return the converted URL as a string. This option is set to a internal TinyMCE function &quot;TinyMCE.prototype.convertURL&quot; by default. You may call this function from your extention inorder to use the build in convertor options.
</p>
<div class="separator"></div>
<h3>Example of usage of the urlconverter_callback option:</h3>
<div class="example">
<pre>
function <strong>myCustomURLConverter</strong>(url, node, on_save) {
// Do some custom URL convertion
url = url.substring(3);
// Return new URL
return url;
}
tinyMCE.init({
...
<strong>urlconverter_callback : "myCustomURLConverter"</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>

View File

@ -1,351 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: valid_elements</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: valid_elements</h1>
</div>
<div class="content">
<p>
This option should contain a comma separated list element convertion chunks. Each chunk contains information about how one element and it's attributes should be treated. The default rule set for this option is specified below.
</p>
<p>
<table border="1" cellspacing="0" cellpadding="4">
<thead><td colspan="2">Control characters:</td></thead>
<tbody>
<tr><td><strong>,</strong></td><td>Separates element chunk definitions.</td></tr>
<tr><td><strong>/</strong></td><td>Separates element synonymous. The first element is the one that will be outputted.</td></tr>
<tr><td><strong>|</strong></td><td>Separates attribute definitions.</td></tr>
<tr><td><strong>[</strong></td><td>Starts a new attribute list for a element definition.</td></tr>
<tr><td><strong>]</strong></td><td>Ends a attribute list for a element definition.</td></tr>
<tr><td><strong>=</strong></td><td>Makes the attribute to default to the specified value. For example &quot;target=_blank&quot;</td></tr>
<tr><td><strong>:</strong></td><td>Makes the attribute to be forced to the specified value. For example &quot;border:0&quot;</td></tr>
<tr><td><strong>&lt;</strong></td><td>Verifies the value of a attribute. For example &quot;target&lt;_blank?_self&quot;</td></tr>
<tr><td><strong>?</strong></td><td>Separates attribute verification values, see above.</td></tr>
<tr><td><strong>+</strong></td><td>Makes the element open if no child nodes exists. Example: +a.</td></tr>
</tbody>
</table>
Wildcards such as *,+,? may be used in element or attribute name matching.
</p>
<p>
Special variables:<br />
<strong>{$uid}</strong> Results in a unique ID. For example &quot;p[id:{$uid}]&quot;.<br />
<br />
Use *[*] to include all elements and all attributes this can be very useful when used with the <a href="option_invalid_elements.html">invalid_elements</a> option.
</p>
<div class="separator"></div>
<h3>Example of usage of the valid_elements option:</h3>
<p>
This example string tells TinyMCE to remove all elements that are not a "a, strong, div or br" element, convert b elements to strong elements, default target to "_blank" and keep the href, target and align attributes of the elements.
</p>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>valid_elements : "a[href|target=_blank],strong/b,div[align],br"</strong>
});
</pre>
</div>
<div class="separator"></div>
<h3>Default rule set:</h3>
<p>
This is the default string used by TinyMCE to cleanup the HTML contents.
</p>
<div class="example">
<pre>
+a[name|href|target|title],strong/b[class],em/i[class],strike[class],u[class],p[dir|class|align],ol,ul,li,br,
img[class|src|border=0|alt|title|hspace|vspace|width|height|align],sub,sup,blockquote[dir|style],
table[border=0|cellspacing|cellpadding|width|height|class|align],tr[class|rowspan|width|height|align|valign],
td[dir|class|colspan|rowspan|width|height|align|valign],div[dir|class|align],span[class|align],pre[class|align],
address[class|align],h1[dir|class|align],h2[dir|class|align],h3[dir|class|align],
h4[dir|class|align],h5[dir|class|align],h6[dir|class|align],hr
</pre>
</div>
<div class="separator"></div>
<h3>Full XHTML rule set:</h3>
<p>
This is the default string used by TinyMCE to cleanup the HTML contents.
</p>
<div class="example">
<pre>
valid_elements : &quot;&quot;
+&quot;a[accesskey|charset|class|coords|dir&lt;ltr?rtl|href|hreflang|id|lang|name&quot;
+&quot;|onblur|onclick|ondblclick|onfocus|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|rel|rev&quot;
+&quot;|shape&lt;circle?default?poly?rect|style|tabindex|title|target|type],&quot;
+&quot;abbr[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;acronym[class|dir&lt;ltr?rtl|id|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;address[class|align|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|style|title],&quot;
+&quot;applet[align&lt;bottom?left?middle?right?top|alt|archive|class|code|codebase&quot;
+&quot;|height|hspace|id|name|object|style|title|vspace|width],&quot;
+&quot;area[accesskey|alt|class|coords|dir&lt;ltr?rtl|href|id|lang|nohref&lt;nohref&quot;
+&quot;|onblur|onclick|ondblclick|onfocus|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup&quot;
+&quot;|shape&lt;circle?default?poly?rect|style|tabindex|title|target],&quot;
+&quot;base[href|target],&quot;
+&quot;basefont[color|face|id|size],&quot;
+&quot;bdo[class|dir&lt;ltr?rtl|id|lang|style|title],&quot;
+&quot;big[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;blockquote[dir|style|cite|class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick&quot;
+&quot;|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout&quot;
+&quot;|onmouseover|onmouseup|style|title],&quot;
+&quot;body[alink|background|bgcolor|class|dir&lt;ltr?rtl|id|lang|link|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onload|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|onunload|style|title|text|vlink],&quot;
+&quot;br[class|clear&lt;all?left?none?right|id|style|title],&quot;
+&quot;button[accesskey|class|dir&lt;ltr?rtl|disabled&lt;disabled|id|lang|name|onblur&quot;
+&quot;|onclick|ondblclick|onfocus|onkeydown|onkeypress|onkeyup|onmousedown&quot;
+&quot;|onmousemove|onmouseout|onmouseover|onmouseup|style|tabindex|title|type&quot;
+&quot;|value],&quot;
+&quot;caption[align&lt;bottom?left?right?top|class|dir&lt;ltr?rtl|id|lang|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;center[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;cite[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;code[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;col[align&lt;center?char?justify?left?right|char|charoff|class|dir&lt;ltr?rtl|id&quot;
+&quot;|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown&quot;
+&quot;|onmousemove|onmouseout|onmouseover|onmouseup|span|style|title&quot;
+&quot;|valign&lt;baseline?bottom?middle?top|width],&quot;
+&quot;colgroup[align&lt;center?char?justify?left?right|char|charoff|class|dir&lt;ltr?rtl&quot;
+&quot;|id|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown&quot;
+&quot;|onmousemove|onmouseout|onmouseover|onmouseup|span|style|title&quot;
+&quot;|valign&lt;baseline?bottom?middle?top|width],&quot;
+&quot;dd[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;del[cite|class|datetime|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|style|title],&quot;
+&quot;dfn[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;dir[class|compact&lt;compact|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|style|title],&quot;
+&quot;div[align&lt;center?justify?left?right|class|dir&lt;ltr?rtl|id|lang|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;dl[class|compact&lt;compact|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|style|title],&quot;
+&quot;dt[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;em/i[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;fieldset[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;font[class|color|dir&lt;ltr?rtl|face|id|lang|size|style|title],&quot;
+&quot;form[accept|accept-charset|action|class|dir&lt;ltr?rtl|enctype|id|lang&quot;
+&quot;|method&lt;get?post|name|onclick|ondblclick|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|onreset|onsubmit&quot;
+&quot;|style|title|target],&quot;
+&quot;frame[class|frameborder|id|longdesc|marginheight|marginwidth|name&quot;
+&quot;|noresize&lt;noresize|scrolling&lt;auto?no?yes|src|style|title],&quot;
+&quot;frameset[class|cols|id|onload|onunload|rows|style|title],&quot;
+&quot;h1[align&lt;center?justify?left?right|class|dir&lt;ltr?rtl|id|lang|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;h2[align&lt;center?justify?left?right|class|dir&lt;ltr?rtl|id|lang|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;h3[align&lt;center?justify?left?right|class|dir&lt;ltr?rtl|id|lang|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;h4[align&lt;center?justify?left?right|class|dir&lt;ltr?rtl|id|lang|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;h5[align&lt;center?justify?left?right|class|dir&lt;ltr?rtl|id|lang|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;h6[align&lt;center?justify?left?right|class|dir&lt;ltr?rtl|id|lang|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;head[dir&lt;ltr?rtl|lang|profile],&quot;
+&quot;hr[align&lt;center?left?right|class|dir&lt;ltr?rtl|id|lang|noshade&lt;noshade|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|size|style|title|width],&quot;
+&quot;html[dir&lt;ltr?rtl|lang|version],&quot;
+&quot;iframe[align&lt;bottom?left?middle?right?top|class|frameborder|height|id&quot;
+&quot;|longdesc|marginheight|marginwidth|name|scrolling&lt;auto?no?yes|src|style&quot;
+&quot;|title|width],&quot;
+&quot;img[align&lt;bottom?left?middle?right?top|alt|border|class|dir&lt;ltr?rtl|height&quot;
+&quot;|hspace|id|ismap&lt;ismap|lang|longdesc|name|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|src|style|title|usemap|vspace|width],&quot;
+&quot;input[accept|accesskey|align&lt;bottom?left?middle?right?top|alt&quot;
+&quot;|checked&lt;checked|class|dir&lt;ltr?rtl|disabled&lt;disabled|id|ismap&lt;ismap|lang&quot;
+&quot;|maxlength|name|onblur|onclick|ondblclick|onfocus|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|onselect&quot;
+&quot;|readonly&lt;readonly|size|src|style|tabindex|title&quot;
+&quot;|type&lt;button?checkbox?file?hidden?image?password?radio?reset?submit?text&quot;
+&quot;|usemap|value],&quot;
+&quot;ins[cite|class|datetime|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|style|title],&quot;
+&quot;isindex[class|dir&lt;ltr?rtl|id|lang|prompt|style|title],&quot;
+&quot;kbd[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;label[accesskey|class|dir&lt;ltr?rtl|for|id|lang|onblur|onclick|ondblclick&quot;
+&quot;|onfocus|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout&quot;
+&quot;|onmouseover|onmouseup|style|title],&quot;
+&quot;legend[align&lt;bottom?left?right?top|accesskey|class|dir&lt;ltr?rtl|id|lang&quot;
+&quot;|onclick|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;li[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style|title|type&quot;
+&quot;|value],&quot;
+&quot;link[charset|class|dir&lt;ltr?rtl|href|hreflang|id|lang|media|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|rel|rev|style|title|target|type],&quot;
+&quot;map[class|dir&lt;ltr?rtl|id|lang|name|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;menu[class|compact&lt;compact|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|style|title],&quot;
+&quot;meta[content|dir&lt;ltr?rtl|http-equiv|lang|name|scheme],&quot;
+&quot;noframes[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;noscript[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;object[align&lt;bottom?left?middle?right?top|archive|border|class|classid&quot;
+&quot;|codebase|codetype|data|declare|dir&lt;ltr?rtl|height|hspace|id|lang|name&quot;
+&quot;|onclick|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|standby|style|tabindex|title|type|usemap&quot;
+&quot;|vspace|width],&quot;
+&quot;ol[class|compact&lt;compact|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|start|style|title|type],&quot;
+&quot;optgroup[class|dir&lt;ltr?rtl|disabled&lt;disabled|id|label|lang|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;option[class|dir&lt;ltr?rtl|disabled&lt;disabled|id|label|lang|onclick|ondblclick&quot;
+&quot;|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout&quot;
+&quot;|onmouseover|onmouseup|selected&lt;selected|style|title|value],&quot;
+&quot;p[align&lt;center?justify?left?right|class|dir&lt;ltr?rtl|id|lang|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;param[id|name|type|value|valuetype&lt;DATA?OBJECT?REF],&quot;
+&quot;pre/listing/plaintext/xmp[align|class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick&quot;
+&quot;|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout&quot;
+&quot;|onmouseover|onmouseup|style|title|width],&quot;
+&quot;q[cite|class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;s[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;samp[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;script[charset|defer|language|src|type],&quot;
+&quot;select[class|dir&lt;ltr?rtl|disabled&lt;disabled|id|lang|multiple&lt;multiple|name&quot;
+&quot;|onblur|onclick|ondblclick|onfocus|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|size|style&quot;
+&quot;|tabindex|title],&quot;
+&quot;small[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;span[align|class|class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|style|title],&quot;
+&quot;strike[class|class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|style|title],&quot;
+&quot;strong/b[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;style[dir&lt;ltr?rtl|lang|media|title|type],&quot;
+&quot;sub[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;sup[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title],&quot;
+&quot;table[align&lt;center?left?right|bgcolor|border|cellpadding|cellspacing|class&quot;
+&quot;|dir&lt;ltr?rtl|frame|height|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|rules&quot;
+&quot;|style|summary|title|width],&quot;
+&quot;tbody[align&lt;center?char?justify?left?right|char|class|charoff|dir&lt;ltr?rtl|id&quot;
+&quot;|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown&quot;
+&quot;|onmousemove|onmouseout|onmouseover|onmouseup|style|title&quot;
+&quot;|valign&lt;baseline?bottom?middle?top],&quot;
+&quot;td[abbr|align&lt;center?char?justify?left?right|axis|bgcolor|char|charoff|class&quot;
+&quot;|colspan|dir&lt;ltr?rtl|headers|height|id|lang|nowrap&lt;nowrap|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|rowspan|scope&lt;col?colgroup?row?rowgroup&quot;
+&quot;|style|title|valign&lt;baseline?bottom?middle?top|width],&quot;
+&quot;textarea[accesskey|class|cols|dir&lt;ltr?rtl|disabled&lt;disabled|id|lang|name&quot;
+&quot;|onblur|onclick|ondblclick|onfocus|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|onselect&quot;
+&quot;|readonly&lt;readonly|rows|style|tabindex|title],&quot;
+&quot;tfoot[align&lt;center?char?justify?left?right|char|charoff|class|dir&lt;ltr?rtl|id&quot;
+&quot;|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown&quot;
+&quot;|onmousemove|onmouseout|onmouseover|onmouseup|style|title&quot;
+&quot;|valign&lt;baseline?bottom?middle?top],&quot;
+&quot;th[abbr|align&lt;center?char?justify?left?right|axis|bgcolor|char|charoff|class&quot;
+&quot;|colspan|dir&lt;ltr?rtl|headers|height|id|lang|nowrap&lt;nowrap|onclick&quot;
+&quot;|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown|onmousemove&quot;
+&quot;|onmouseout|onmouseover|onmouseup|rowspan|scope&lt;col?colgroup?row?rowgroup&quot;
+&quot;|style|title|valign&lt;baseline?bottom?middle?top|width],&quot;
+&quot;thead[align&lt;center?char?justify?left?right|char|charoff|class|dir&lt;ltr?rtl|id&quot;
+&quot;|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup|onmousedown&quot;
+&quot;|onmousemove|onmouseout|onmouseover|onmouseup|style|title&quot;
+&quot;|valign&lt;baseline?bottom?middle?top],&quot;
+&quot;title[dir&lt;ltr?rtl|lang],&quot;
+&quot;tr[abbr|align&lt;center?char?justify?left?right|bgcolor|char|charoff|class&quot;
+&quot;|rowspan|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title|valign&lt;baseline?bottom?middle?top],&quot;
+&quot;tt[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;u[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress|onkeyup&quot;
+&quot;|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style|title],&quot;
+&quot;ul[class|compact&lt;compact|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown&quot;
+&quot;|onkeypress|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover&quot;
+&quot;|onmouseup|style|title|type],&quot;
+&quot;var[class|dir&lt;ltr?rtl|id|lang|onclick|ondblclick|onkeydown|onkeypress&quot;
+&quot;|onkeyup|onmousedown|onmousemove|onmouseout|onmouseover|onmouseup|style&quot;
+&quot;|title]&quot;
</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: verify_css_classes</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: verify_css_classes</h1>
</div>
<div class="content">
<p>
If you enable this function, class names placed in class attributes will be verified agains the content CSS. So elements with a class attribute containing a class that doesn't exist in the CSS will be removed.
</p>
<div class="separator"></div>
<h3>Example of usage of the verify_css_classes option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>verify_css_classes : 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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: verify_html</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: verify_html</h1>
</div>
<div class="content">
<p>
This option enabled or disables the element cleanup functionality. If you set this option to false, all element cleanup will be skipped but other cleanup functionality such as URL convertion will still be executed.
</p>
<div class="separator"></div>
<h3>Example of usage of the verify_html option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>verify_html : 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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: visual</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: visual</h1>
</div>
<div class="content">
<p>
This true/false option gives you the ability to turn on/off the visual aid for border less tables. If a the border of a table is set to 0 TinyMCE adds a dotted line around the table by default.
</p>
<div class="separator"></div>
<h3>Example of usage of the visual option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>visual : 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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: visual_table_class</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: visual_table_class</h1>
</div>
<div class="content">
<p>
This option enables you to specify what CSS class to use for presenting visual aids for border less tables. The default value of this option is set to &quot;mceVisualAid&quot;.
</p>
<div class="separator"></div>
<h3>Example of usage of the visual_table_class option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>visual_table_class : "myCustomVisualAidTableClass"</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>

View File

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Option: width</title>
<link href="css/screen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="header">
<h1>Option: width</h1>
</div>
<div class="content">
<p>
This option gives you the ability to specify the width of the editor in pixels or percent. This width can be very useful 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 width of the HTML element TinyMCE replaces for example the pixel width of a textarea.
</p>
<div class="separator"></div>
<h3>Example of usage of the width option:</h3>
<div class="example">
<pre>
tinyMCE.init({
...
<strong>width : "640"</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