danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0: ASP integration Samples List — CKEditor
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0: CKEditor Samples List for ASP — CKEditor Sample
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0: Overview
danielebarchiesi@0:
danielebarchiesi@0:
The ckeditor.asp file provides a wrapper to ease the work of creating CKEditor instances from classic Asp.
danielebarchiesi@0:
To use it, you must first include it into your page:
danielebarchiesi@0:
danielebarchiesi@0: <!-- #INCLUDE file="../../ckeditor.asp" -->
danielebarchiesi@0:
danielebarchiesi@0: Of course, you should adjust the path to make it point to the correct location, and maybe use a full path (with virtual="" instead of file="")
danielebarchiesi@0:
danielebarchiesi@0:
After that script is included, you can use it in different ways, based on the following pattern:
danielebarchiesi@0: Create an instance of the CKEditor class:
danielebarchiesi@0:
dim editor
danielebarchiesi@0: set editor = New CKEditor
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0: Set the path to the folder where CKEditor has been installed, by default it will use /ckeditor/
danielebarchiesi@0:
editor.basePath = "../../"
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0: Now use one of the three main methods to create the CKEditor instances:
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0: Replace textarea with id (or name) "editor1".
danielebarchiesi@0:
editor.replaceInstance "editor1"
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0: Replace all textareas with CKEditor.
danielebarchiesi@0:
editor.replaceAll empty
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0: Create a textarea element and attach CKEditor to it.
danielebarchiesi@0:
editor.editor "editor1", initialValue
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0:
danielebarchiesi@0:
Before step 3 you can use a number of methods and properties to adjust the behavior of this class and the CKEditor instances
danielebarchiesi@0: that will be created:
danielebarchiesi@0:
danielebarchiesi@0:
returnOutput : if set to true, the functions won't dump the code with response.write, but instead they will return it so
danielebarchiesi@0: you can do anything you want
danielebarchiesi@0:
basePath: location of the CKEditor scripts
danielebarchiesi@0:
initialized: if you set it to true, it means that you have already included the CKEditor.js file into the page and it
danielebarchiesi@0: doesn't have to be generated again.
danielebarchiesi@0:
textareaAttributes: You can set here a Dictionary object with the attributes that you want to output in the call to the "editor" method.
danielebarchiesi@0:
danielebarchiesi@0:
config: Allows to set config values for all the instances from now on.
danielebarchiesi@0:
instanceConfig: Allows to set config values just for the next instance.
danielebarchiesi@0:
danielebarchiesi@0:
addEventHandler: Adds an event handler for all the instances from now on.
danielebarchiesi@0:
addInstanceEventHandler: Adds an event handler just for the next instance.
danielebarchiesi@0:
addGlobalEventHandler: Adds an event handler for the global CKEDITOR object.
danielebarchiesi@0:
danielebarchiesi@0:
clearEventHandlers: Removes one or all the event handlers from all the instances from now on.
danielebarchiesi@0:
clearInstanceEventHandlers: Removes one or all the event handlers from the next instance.
danielebarchiesi@0:
clearGlobalEventHandlers: Removes one or all the event handlers from the global CKEDITOR object.