CKFinder 2.x/Developers Guide/ASP/Plugins/Writing ASP - Revision history

Wiktor: /* Enabling JavaScript plugin */

2010-05-26T08:05:20Z

‎Enabling JavaScript plugin

Wiktor: /* Enabling JavaScript plugin */

2010-05-26T08:04:48Z

‎Enabling JavaScript plugin

Wiktor: /* Enabling JavaScript plugin */

2010-05-26T08:03:50Z

‎Enabling JavaScript plugin

Wiktor: /* Enabling JavaScript plugin */

2010-05-26T08:00:44Z

‎Enabling JavaScript plugin

Wiktor: /* Step2: Create a class */

2010-05-26T07:51:51Z

‎Step2: Create a class

Wiktor: /* ASP plugin system */

2010-05-26T07:51:27Z

‎ASP plugin system

Wiktor: /* ASP plugin system */

2010-05-26T07:50:47Z

‎ASP plugin system

Wiktor: /* ASP plugin system */

2010-05-26T07:48:23Z

‎ASP plugin system

Wiktor at 07:44, 26 May 2010

2010-05-26T07:44:27Z

Wiktor: /* Full source code */

2010-05-26T07:37:40Z

‎Full source code

@@ Line 50: / Line 50: @@
 config.extraPlugins = 'myplugin';
 </source>
-but the advantage of defining it in plugin.php is that it will be enabled only when the server side plugin is also enabled.
+but the advantage of defining it in plugin.asp is that it will be enabled only when the server side plugin is also enabled.
 {{CKFinder_2.x Sample Plugin Introduction|ext=asp}}

@@ Line 39: / Line 39: @@
 === Enabling JavaScript plugin ===
-Sometimes a server side plugin might come with a client side (JavaScript) plugin, that should be automatically enabled when the server side plugin is enabled. To do this, use <code>CKFinder_AddPlugin</code> function.
+Sometimes a server side plugin might come with a client side (JavaScript) plugin, that should be automatically enabled when the server side plugin is enabled. To enable a JavaScript plugin inside your ASP plugin, use <code>CKFinder_AddPlugin</code> function.
 To enable a plugin, simply call CKFinder_AddPlugin.

@@ Line 39: / Line 39: @@
 === Enabling JavaScript plugin ===
-Sometimes a server side plugin might come with a client side (JavaScript) plugin, that should be automatically enabled when the server side plugin is enabled.<br>
+Sometimes a server side plugin might come with a client side (JavaScript) plugin, that should be automatically enabled when the server side plugin is enabled. To do this, use <code>CKFinder_AddPlugin</code> function.
 To enable a plugin, simply call CKFinder_AddPlugin.

@@ Line 42: / Line 42: @@
 The <code>$config['Plugins']</code> variable is a special array that does that.
-To enable a plugin, simply add it's name to this array.
+To enable a plugin, simply call CKFinder_AddPlugin.
-<source lang="php">
+<source lang="asp">
-$config['Plugins'][] = 'myplugin';
+CKFinder_AddPlugin "myplugin"
 </source>

@@ Line 139: / Line 139: @@
 <source lang="asp">
 class CKFinder_Connector_CommandHandler_FileSize
-	'pseudo inheritance
+	' Pseudo inheritance
 	private base

@@ Line 58: / Line 58: @@
 <source lang="asp">
 <script runat="server" language="VBScript">
-−
 class CKFinder_Connector_CommandHandler_FileSize
      'pseudo inheritance
      private base
-     ' Since we want to send a XML response, we'll extend the XmlCommandHandlerBase class
+     ' (2) Since we want to send a XML response, we'll extend the XmlCommandHandlerBase class
      Private Sub Class_Initialize()
          Set base = new CKFinder_Connector_CommandHandler_XmlCommandHandlerBase
@@ Line 82: / Line 83: @@
      End Property
-     ' (5) The buildXml method is used to construct an XML response
+     ' (4) The buildXml method is used to construct an XML response
      function buildXml( oXML )
          Dim fileName
@@ Line 93: / Line 94: @@
          filePath = oUFS.combinePaths(currentFolder.getServerPath(), fileName)
-         ' (6) Adding a <FileSize> element to the XML response.
+         ' (5) Adding a <FileSize> element to the XML response.
          Dim size, oNode
          size = oUFS.GetFileSize(filePath)
@@ Line 121: / Line 122: @@
 Set CommandHandler_FileSize = new CKFinder_Connector_CommandHandler_FileSize
-' Object assigned to a hook must contain event listener named "onEventName"
+' (1) Object assigned to a hook must contain event listener named "onEventName"
 ' (the event name is BeforeExecuteCommand, so we must define an onBeforeExecuteCommand method).
 CKFinder_AddHook "BeforeExecuteCommand", CommandHandler_FileSize
@@ Line 166: / Line 167: @@
 </source>
-==== Step6: Construct the XML response ====
+==== Step5: Construct the XML response ====
 The main task of the buildXml method is to construct an XML response, so we're doing it below:
 <source lang="asp">
@@ Line 182: / Line 183: @@
 <script runat="server" language="VBScript">
 class CKFinder_Connector_CommandHandler_FileSize
      'pseudo inheritance
      private base
-     ' Since we want to send a XML response, we'll extend the XmlCommandHandlerBase class
+     ' (2) Since we want to send a XML response, we'll extend the XmlCommandHandlerBase class
      Private Sub Class_Initialize()
          Set base = new CKFinder_Connector_CommandHandler_XmlCommandHandlerBase
@@ Line 210: / Line 212: @@
      End Property
-     ' (5) The buildXml method is used to construct an XML response
+     ' (4) The buildXml method is used to construct an XML response
      function buildXml( oXML )
@@ Line 244: / Line 246: @@
          End if
-         ' (6) Adding a <FileSize> element to the XML response.
+         ' (5) Adding a <FileSize> element to the XML response.
          Dim size, oNode
          size = oUFS.GetFileSize(filePath)
@@ Line 273: / Line 275: @@
      Set CommandHandler_FileSize = new CKFinder_Connector_CommandHandler_FileSize
-     ' Object assigned to a hook must contain event listener named "onEventName"
+     ' (1) Object assigned to a hook must contain event listener named "onEventName"
      ' (the event name is BeforeExecuteCommand, so we must define an onBeforeExecuteCommand method).
      CKFinder_AddHook "BeforeExecuteCommand", CommandHandler_FileSize

@@ Line 168: / Line 168: @@
 ==== Full source code ====
 ===== plugin.asp =====
-The full source code of a plugin with all necessary security checks: (save the code as '''plugin.php''' in "plugins/myplugin" folder)
+The full source code of a plugin with all necessary security checks: (save the code as '''plugin.asp''' in "plugins/myplugin" folder)
 <source lang="asp">