Integration"

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

(Created page with '{{CKFinder_2.x Integration Introduction|language=ColdFusion|ext=cfm|classext=cfc}} === Examples === To start the CKFinder, basically we need to do three things: * Create an inst…')
 
Line 1: Line 1:
 +
__TOC__
 
{{CKFinder_2.x Integration Introduction|language=ColdFusion|ext=cfm|classext=cfc}}
 
{{CKFinder_2.x Integration Introduction|language=ColdFusion|ext=cfm|classext=cfc}}
  
=== Examples ===
+
=== Example ===
To start the CKFinder, basically we need to do three things:
+
To launch CKFinder, basically we need to do three things:
* Create an instance of the CKFinder class/component.
+
* Create an instance of a CKFinder class/component.
 
* Assign CKFinder properties.
 
* Assign CKFinder properties.
 
* Call the '''Create''' function.
 
* Call the '''Create''' function.
  
 
{{CKFinder_2.x Integration Javascript Example}}
 
 
The example of creating CKFinder using a ColdFusion component:
 
The example of creating CKFinder using a ColdFusion component:
 
<pre>
 
<pre>
Line 19: Line 18:
 
</pre>
 
</pre>
  
For a full working examples please refer to the "'''_samples'''" directory. Note that in case of javascript integratino method it is required to include the integration file (ckfinder.js) to have access to the CKFinder class.
+
For a full working examples please refer to the "'''_samples'''" directory.
  
{{CKFinder_2.x Integration Javascript}}
+
== Integration methods ==
  
{{CKFinder_2.x Integration Properties|language=cfm}}
+
* [[/JavaScript|JavaScript integration]] - The preferred method of integration, simple, yet powerful.
 +
* [[/JavaScript V1|JavaScript integration (V1)]] - The old "V1" way, useful when migrating from CKFinder 1.x because it is possible to reuse the old code.
 +
* [[/ColdFusion V1|ColdFusion integration]] - If you haven't worked with JavaScript before or the JavaScript integration seems to be too complicated  then it might be the way to go for you.

Revision as of 09:40, 18 May 2010

Introduction

Before reading this section, please read the installation and configuration instructions and make sure that the examples located in the _samples directory are working correctly.

The _samples directory contains HTML files with examples of launching CKFinder by using the JavaScript code as well as a cfm folder with examples of launching CKFinder by using the ColdFusion language.

The following files are used when either the JavaScript or the ColdFusion method of launching CKFinder is used:

  • ckfinder.js in case of the JavaScript integration method,
  • ckfinder_v1.js in case of JavaScript V1 integration method (useful when migrating from CKFinder 1.x),
  • ckfinder.cfc in case of the ColdFusion integration method.

Example

To launch CKFinder, basically we need to do three things:

  • Create an instance of a CKFinder class/component.
  • Assign CKFinder properties.
  • Call the Create function.

The example of creating CKFinder using a ColdFusion component:

<cfscript>
ckfinder = createObject( "component", "ckfinder" ) ;
ckfinder.basePath = "/ckfinder/" ;
ckfinder.width = 400 ;
ckfinder.Create() ; // create the editor.
</cfscript>

For a full working examples please refer to the "_samples" directory.

Integration methods

  • JavaScript integration - The preferred method of integration, simple, yet powerful.
  • JavaScript integration (V1) - The old "V1" way, useful when migrating from CKFinder 1.x because it is possible to reuse the old code.
  • ColdFusion integration - If you haven't worked with JavaScript before or the JavaScript integration seems to be too complicated then it might be the way to go for you.