[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Phpgroupware-cvs] news_admin/js/fckeditor/_docs/contents 004.html, 1.1
|
From: |
skwashd |
|
Subject: |
[Phpgroupware-cvs] news_admin/js/fckeditor/_docs/contents 004.html, 1.1 005.html, 1.1 006.html, 1.1 007.html, 1.1 003.html, 1.1 002.html, 1.1 001.html, 1.1 008.html, 1.1 009.html, 1.1 010.html, 1.1 011.html, 1.1 012.html, 1.1 |
|
Date: |
Tue, 24 May 2005 16:32:00 +0200 |
Update of news_admin/js/fckeditor/_docs/contents
Added Files:
Branch: MAIN
004.html
005.html
006.html
007.html
003.html
002.html
001.html
008.html
009.html
010.html
011.html
012.html
Log Message:
I am working on a much better version of news_admin, this is just a taste of
what is coming.
Adding FCKeditor, which has the following issues:
* Images and files support FCKd
* Spellcheck FCKing up
Didn't include non php code or samples other unneeded crap
====================================================
Index: 004.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-10 18:20:56
-->
<html>
<head>
<title>FCKeditor - Installation Instructions</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>Installation Instructions</H1>
<P>Installing FCKeditor is quite a simple task. Just follow
these simple steps:
</P>
<P></P>
<OL>
<LI>
<STRONG>Donwload</STRONG> the last version of
the editor at the following url:<BR>
<A
href="http://sourceforge.net/project/showfiles.php?group_id=75348";>http://sourceforge.net/project/showfiles.php?group_id=75348</A>
<LI>
<STRONG>Uncompress</STRONG>
the file to a directory called "FCKeditor"* in the root
of your web site.
<LI>
The editor is now <STRONG>ready to
use</STRONG>. To see it immediatelly at work
just browse to:<BR>
<A
href="http://<your-site>/FCKeditor/_samples/default.html">http://<your-site>/FCKeditor/_samples/default.html</A></LI></OL>
<P>
* You can place the files in any directory. "FCKeditor"
is the default one. If
you prefer using another one, just set the editor's
base path in the code. For
example:<BR>
oFCKeditor.BasePath = '/Components/FCKeditor/' ;<BR>
<BR>
You can optionally delete all directories started with
underline ("_"). They
are not necessary to the editor to run.</P>
<H2>Using the editor</H2>
<P>The package comes with a test sample page available for
every programming
languages that the editor is compatible to. Take a look
at the _samples directory.<!-- DOCMANAGER DOCUMENT END -->
</P>
</body>
</html>
====================================================
Index: 005.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-10 18:20:46
-->
<html>
<head>
<title>FCKeditor - Localization (Interface Translation)</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>Localization (Interface Translation)</H1>
<P>The languages files must be created inside the "editor/lang"
directory of the
project. You can use the file <STRONG>en.js</STRONG> as
the base file for your
translations. The file names respect the <A
href="http://www.faqs.org/rfcs/rfc3066.html"; target="_blank">
RFC 3066</A> <STRONG></STRONG>standards (but in
lowercase). So, for
example, a file for the <STRONG>Portuguese
language</STRONG> should be called <STRONG>pt.js</STRONG>.</P>
<P>Translation could also be localized for a specific country.
In this case, for
example, a Brazilian Portuguese translation file should
be called <STRONG>pt-br.js</STRONG>.</P>
<P>The clients language auto detection system uses the first
available language
that best fits the client settings. For example, if a
client computer is set to
Brazilian Portuguese and there is no pt-br.js file
available, the pt.js is used
if available. If not, the default language is used
(from the configuration
file).</P>
<P>When creating new language files, you need to add an entry
for it in the
"edit/lang/fcklanguagemanager.js" file. Something like
this:<BR>
<BR>
<code>FCKLanguageManager.AvailableLanguages =
<BR>
{<br>
<BLOCKQUOTE dir="ltr" style="PADDING-RIGHT:
0px; MARGIN-TOP: 0px; PADDING-LEFT: 0px; MARGIN-BOTTOM: 0px; PADDING-BOTTOM:
0px; MARGIN-RIGHT: 0px; PADDING-TOP: 0px">
en : 'English',<BR>
<STRONG>pt : 'Portuguese'</STRONG>
</BLOCKQUOTE>}
<BR>
</code>
<p>
An important thing is to save the files in a
<STRONG>UTF-8</STRONG> encoded
format. In other case, some strange characters could
appear instead of some
special chars, like accented letters, symbols, etc.
</p>
<P>All translated files must be sent by e-mail to <A
href="mailto:address@hidden";>
address@hidden</A> as well
as published in our "<A
href="http://sourceforge.net/tracker/?group_id=75348&atid=543655";
target="_blank">Patches
Tracker</A>" on Sourceforge for availability to
other users.
</P>
<P>
Before starting a new translation, please take a look
at our web site (<A href="http://www.fckeditor.net/Developers/";
target="_blank">http://www.fckeditor.net/Developers/</A>)
and check if there is no translator assigned to your
language. It is a
good practice to contact FredCK (using the same
address) asking if the
translation was not yet started by another person.
</P>
</body>
</html>
====================================================
Index: 006.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-17 15:39:11
-->
<html>
<head>
<title>FCKeditor - Styles</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>Styles</H1>
<p>The editor offers a complete and powerful support for
separating text formatting
definitions from the text itself. And even more, it is
possible to offer a
complete set of predefined formatting definitions to
the end-user (writer) so
the text can be well designed without messing up the
HTML source.</p>
<p>To do that, the <STRONG>Style</STRONG> toolbar command has
been introduced. It
shows a complete list of available styles with preview
for text styles.</p>
<H3>Customizing the Styles list</H3>
<p>The list of available styles is completely customizable for
your needs. It is
based on a <STRONG>XML</STRONG> file. This file can be
placed anywhere in your
site. You just need to point the editor to the right
path using the following
configuration setting:</p>
<code>FCKConfig.<STRONG>StylesXmlPath</STRONG> =
'../fckstyles.xml' ;</code>
<H3>
The Styles XML file</H3>
<p>It is a simple file that describes how to name and apply
each style available in
the editor. This is a sample:</p>
<code><?xml version="1.0" encoding="utf-8" ?><br>
<<STRONG>Styles</STRONG> ><br>
<<STRONG>Style</STRONG>
name="My Image"
element="img"><br>
<<STRONG>Attribute</STRONG> name="style"
value="padding: 5px" /><br>
<<STRONG>Attribute</STRONG>
name="border"
value="2" /><br>
</<STRONG>Style</STRONG> ><br>
<<STRONG>Style
</STRONG>name="Italic" element="em"
/><br>
<<STRONG>Style</STRONG>
name="Title"
element="span"><br>
<<STRONG>Attribute</STRONG> name="class"
value="Title" /><br>
</<STRONG>Style</STRONG>
><br>
<<STRONG>Style</STRONG>
name="Title H3" element="h3"
/><br>
</<STRONG>Styles</STRONG>></code>
<p>The above sample shows how to define four styles, one for a
"Object" element (in
this case for images) and three for text. The
editor will show the styles
in a context sensitive fashion, so when and image is
select only the <STRONG>My
Image</STRONG> style will be available in the
list and when text is
selected the <STRONG>Italic</STRONG>,
<STRONG>Title</STRONG> and <STRONG>Title
H3</STRONG> will be shown.</p>
<p>The root node of the Styles XML file must be named
<STRONG>Styles</STRONG>.
Each style definition must be a child of it with a
<STRONG>Style</STRONG>
name.</p>
<p>The <STRONG>Style</STRONG> nodes have two mandatory
attributes:</p>
<BLOCKQUOTE dir="ltr" style="MARGIN-RIGHT: 0px">
<p><STRONG>name</STRONG>: defines the text shown in the
styles list.<br>
<STRONG>element</STRONG>: the element used to
apply the style on text selection
or the object element to witch the style can be
applied.</p>
</BLOCKQUOTE>
<p>For example: suppose we have the text This is a Style
Command test inside the
editor and we select Style Command. If we apply the
Italic style the source
result will be something like this:</p>
<code>This is a <STRONG><em></STRONG>Style
Command<STRONG></em></STRONG>
test</code>
<p>So the editor used the <STRONG>em</STRONG> tag to apply the
style, as defined
in the XML file.</p>
<p>We can also combine elements and their attributes when
applying a style. To do
this we can add <STRONG>Attribute</STRONG> nodes inside
the <STRONG>Style</STRONG>
node definition. We can add as many attributes we want.
The <STRONG>Attribute</STRONG>
node has two mandatory attributes:</p>
<BLOCKQUOTE dir="ltr" style="MARGIN-RIGHT: 0px">
<p><STRONG>name</STRONG>: the attribute name.<br>
<STRONG>value</STRONG>: the value to be set to
the attribute.</p>
</BLOCKQUOTE>
<p>So, using the same sample, but now selection the Title
style, the source
result should be:</p>
<code>This is a <STRONG><span
class="Title"></STRONG>Style Command<STRONG></span></STRONG>
test</code>
<p>We can also combine many styles over the same selection. So
with the above
sample, without changing the selection, and applying
the Italic style, the
result should be:</p>
<code>This is a <STRONG><span
class="Title"><em></STRONG>Style
Command<STRONG></em></span></STRONG>
test</code>
<p>The user can decide to remove the applied style. He just
need to click in the
style name again to remove it.</p>
<H3>Object elements</H3>
<p>The editor is context sensitive. If the user selects some
text, only the text
styles will be available in the styles list. In the
other case, if an object is
select, the list will show only styles defined to that
object (for now it is
available only over Internet Explorer).</p>
<p>The object elements supported by the editor are:
<STRONG>IMG</STRONG>, <STRONG>TABLE</STRONG>,
<STRONG>TR</STRONG>, <STRONG>TD</STRONG>,
<STRONG>INPUT</STRONG>, <STRONG>SELECT</STRONG>,
<STRONG>TEXTAREA</STRONG>, <STRONG>HR</STRONG> and
<STRONG>OBJECT</STRONG>.</p>
<p>When selecting an Object element and applying a style, no
tags will be added
surrounding the element, but just the defined
attributes will be applied to
that element.</p>
<p>For example, if you have and image in the editor and apply
the My Image style
(from out sample) the source could be something like
this:</p>
<code><img src="Image.jpg" <STRONG>style="padding: 5px"
border="2"</STRONG>></code>
</body>
</html>
====================================================
Index: 007.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-10 18:17:54
-->
<html>
<head>
<title>FCKeditor - Built in File Manager</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>Built in File Browser</H1>
<P>The editor comes with a default, generic, File Browser that
is, for now, used by
the Link and Image dialog windows (throw the
"Browser Server" button).
This File Browser offers a <STRONG>unique
interface</STRONG> that can be used
by all server side languages throw a "Connector" that
is based on standard <STRONG>XML</STRONG>
messages. The developer, when implementing FCKeditor on
his site, can decide
wich Connector to used based on his server capabilities
and preferences.</P>
<P>Today, there are available Connectors for
<STRONG>ASP</STRONG>, <STRONG>PHP</STRONG>
and <STRONG>ASP.NET</STRONG>.</P>
<H3>Configuring the Connector</H3>
<P>All connectors available in the editor package can be found
at the following
folder:
"editor/filemanager/browser/default/connectors". Each server side
language has its own folder there, with the Connector
file inside it. To choose
witch connector to use, the developer just edit
the configuration file and
modify the following key (in this case for the Link
Dialog box):</P>
<code>FCKConfig.<STRONG>LinkBrowserURL</STRONG> =
FCKConfig.BasePath +
"filemanager/browser/default/browser.html?Connector=<STRONG>connectors/aspx/connector.aspx</STRONG>"
;</code>
<P>The Connector path is relative to the
"editor/filemanager/browser/default"
folder. The user could even written his custom
Connector and point the <STRONG>LinkBrowserURL</STRONG>
to it, like
"?Connector=/<STRONG>MyFolder/MyConnector.php</STRONG>
" for example.
<P>The same thing applies to the "ImageBrowserURL"
configurations.</P>
<H3>Configuring the Server Directory</H3>
<P>
All files handled by the editor point to a directory tree
placed in the server
side. In this way, all uploads and urls point to that tree.
<P>This tree has a single Root directory that is called, by
default, "<STRONG>/UserFiles/</STRONG>
". You should create this folder on you web site to avoid
problems with the
File Browser.
<P>In any case, it is possible to point the Root directory of
your File Browser to
any directory you want. For example, suppose I wan't my
files on a
"/Files/EditorFiles/" directory. I just need add an
optional parameter to the
"LinkBrowserURL" configuration string. This paramenter
is called "<STRONG>ServerPath</STRONG>
". So, using our sample, the LinkBrowserURL string
should be something like
this:</P>
<code>FCKConfig.<STRONG>LinkBrowserURL</STRONG> =
FCKConfig.BasePath +
"filemanager/browser/default/browser.html?Connector=connectors/aspx/connector.aspx<STRONG>&ServerPath=/Files/EditorFiles/</STRONG>"
;</code>
<P>The same thing applies to the "ImageBrowserURL"
configurations.</P>
</body>
</html>
====================================================
Index: 003.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-10 18:21:06
-->
<html>
<head>
<title>FCKeditor - Performance</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>Performance</H1>
<P>End users who need to work with FCKeditor want the most
short loading and
response time from it. They want to start reading and
editing the content
quickly. This is a big problem for almost all
on-line text editors.
There are many files that have to be downloaded from
the server to make the
editor work:</P>
<UL>
<LI>
The called page and all images and scripts not related
to the editor.
<LI>
If using Javascript integration, the JS file with the
scripts to create the
editor
<LI>
The page that works as the editor area (it's loaded in
a IFrame)
<LI>
All the JS files with the scripts for the editor engine
(more than 10 for
version 1.x)
<LI>
The language file
<LI>
The editor's skin files
<LI>
All images that are used as the toolbar buttons
(every button has it's own
image)</LI></UL>
<P>All these calls generate a lot of work and traffic throw the
client's browser
and the server. And worth, as many files are called,
even if small
size, as much time to wait.</P>
<P>Two solutions have been developed for version 2.0 to solve
this problem:
accurate loading order and scripts compression.</P>
<H2>Loading Order</H2>
<P>From version 2.0, the editor separe it's loading into
steps:</P>
<UL>
<LI>
The called page (that holds the editor) and the script
to loaded the
editor is loaded.
<LI>
The basic scripts to create the editor are loaded
<LI>
The editor's skin and language files are loaded
<LI>
The editor is created
<LI>
The content is loaded in the editor
<LI>
[ At this point the user can start reading and writing
with some limitations
(drag-and-drop is disabled - cut and paste are disabled
- the toolbar is
not yet available ]
<LI>
The editor's engine scripts are loaded
<LI>
The toolbar is created and shown to the user (even if
the buttons images are
not yet loaded)
<LI>
[ At this point the editor has all it's
feature enabled ]
<LI>
The toolbar icons are loaded.</LI></UL>
<H2>Scripts Compression</H2>
<P>The editor's scripts (JS files) are now pre-processed
before packing any
new version. This are the processing steps:</P>
<UL>
<LI>
Remove all comments from the code.
<LI>
Remove all unuseful blank spaces, tabs and carriage
returns
<LI>
Merge the scripts in fewer files.</LI></UL>
<P>With this process we can reduce the file sizes up to
50%. Another good
think is that the editor code can now be fully
commented (I avoid code
commenting on version 1.x to reduce the files size).</P>
<P>The original code will still be available in the package in
a folder called
"_source".</P>
</body>
</html>
====================================================
Index: 002.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-10 18:21:14
-->
<html>
<head>
<title>FCKeditor - Using FCKeditor with JavaScript</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>Server Side Integration Guidelines</H1>
<P>This documet offers some guidelines that must be considered
when
developing server side integration for FCKeditor
(alias Server Side
Integration Pack).</P>
<P>There a few points of integration that every server side
technology should have
to be completely ready for FCKeditor. These are the
main features:</P>
<UL>
<UL>
<LI>
<A href="#FCKeditorCreator">FCKeditor
Creator</A>
<LI>
<A href="#FileUploadManager">File
Upload Manager</A>
<LI>
<A href="#FileBrowser">File Browser</A>
<LI>
<A href="#Samples">Samples</A>
<LI>
<A
href="#Documentation">Documentation</A></LI></UL>
</UL>
<P>This document will present the basic (minimum) features the
integration must
accomplish to. Any other feature is a welcome surplus.
The scope of this
document is to provide a generic pattern in the
way the editor can have a
homogeneous programming style even throw different
languages.</P>
<HR width="100%" SIZE="1">
<H2 id="FCKeditorCreator">FCKeditor Creator</H2>
<P>This is the main integration feature needed. It makes it
possible to create an
instance of FCKeditor in a page using the desired
server side language. Object
oriented programming (OOP) should be used wherever is
possible. These are the
tasks the Integration Pack should propose to the end
user programmer:</P>
<UL>
<UL>
<LI>
Editor Instance Creation
<LI>
Configuration and Settings
<LI>
Automatic Browser Compatibility
Detection:
<UL>
<LI>
Output HTML of the editor
IFRAME for compatible browsers.
<LI>
Output HTML of a simple
TEXTAREA for not compatible browsers.</LI></UL>
</LI>
</UL>
</UL>
<P>Suppose the editor instance is called "MyEditor". For
compatible browser the
Integration Pack should output HTML like this:</P>
<code><div><BR>
<input type="hidden" id="<STRONG>MyEditor</STRONG>"
name="MyEditor" value="<STRONG><EM>initial
value (HTML encoded)</EM>
</STRONG>"><BR>
<input type="hidden"
id="<STRONG>MyEditor</STRONG>___Config"
value="<STRONG>Key1=Value1&Key2=Value2&...
<EM>(Key/Value:HTML
encoded)</EM></STRONG>"><BR>
<iframe id="<STRONG>MyEditor</STRONG>___Frame"
src="<STRONG>/FCKeditor/</STRONG>editor/fckeditor.html?InstanceName=<STRONG>MyEditor</STRONG>&Toolbar=<STRONG>Default</STRONG>"
width="<STRONG>100%</STRONG>"
height="<STRONG>200</STRONG>" frameborder="no"
scrolling="no"></iframe><BR>
</div><BR>
</code>
<P>While non compatible browsers should get:</P>
<code><div><BR>
<textarea name="<STRONG>MyEditor</STRONG>" rows="4"
cols="40" style="WIDTH: <STRONG>
100%</STRONG>; HEIGHT: <STRONG>200px</STRONG>"
wrap="virtual"><STRONG><EM>initial
value (HTML
encoded)</EM></STRONG></textarea><BR>
</div></code>
<H3>FCKeditor Class</H3>
<P>The Integration pack should usually offer a main class,
called "FCKeditor", in a
file called "fckeditor.ext" placed in the root of the
editor's distribution
package. To be able to use the class the end user
should just include a "link"
to that file and then easily create an instance of it.
Obviously this is the
common scenario for scripting languages. Other
languages should just reflect
this situation in the better way it's possible.</P>
<P>This is the basic structure of the FCKeditor Class:</P>
<BLOCKQUOTE dir="ltr" style="MARGIN-RIGHT: 0px">
<div class="classDefinition">
<P><STRONG>Constructor</STRONG></P>
<BLOCKQUOTE dir="ltr" style="MARGIN-RIGHT: 0px">
<P>FCKeditor( instanceName )</P>
</BLOCKQUOTE>
<P><STRONG>Properties</STRONG></P>
<BLOCKQUOTE dir="ltr" style="MARGIN-RIGHT: 0px">
<P>InstanceName<BR>
Width
<BR>
Height
<BR>
ToolbarSet
<BR>
Value
<BR>
BasePath</P>
</BLOCKQUOTE>
<P><STRONG>Collections</STRONG></P>
<BLOCKQUOTE dir="ltr" style="MARGIN-RIGHT: 0px">
<P>Config <EM>(Only if possible to use
collections)</EM></P>
</BLOCKQUOTE>
<P><STRONG>Methods</STRONG></P>
<BLOCKQUOTE dir="ltr" style="MARGIN-RIGHT: 0px">
<P>Create()<BR>
SetConfig( key, value )
<EM>(Only if not possible to use collections)</EM></P>
</BLOCKQUOTE>
</div>
</BLOCKQUOTE>
<P>The implementation should be based on the Javascript
implementation (see
fckeditor.js file). See <A
href="../Using%20FCKeditor/Javascript.html">/_documentation/Developers/Using
FCKeditor/Javascript.html</A> for a complete
explanation of the class
elements.</P>
<HR width="100%" SIZE="1">
<H2 id="FileUploadManager">File Upload Manager</H2>
<P>[ Documentation not yet available ]</P>
<HR width="100%" SIZE="1">
<H2 id="FileBrowser">File Browser</H2>
<P>The editor gives the end user the flexibility to create a
custom file browser
that can be integrated on it. This is a powerful
feature, because every case is
a different case and so different and specific problems
must be solved. In any
case, the editor package offers a default
implementation of the File Browser so
the user has a ready to use software without having to
develop anything.</P>
<P>On prior versions, a sample File Browser was available for
each server side
technology the editor was integrated. The problem with
that approach is that
each sample had a different implementation and worked
completed different from
each other. And worst, on some of then it was really
poor.</P>
<P>To solve that problems the actual version offers a
<STRONG>unique interface</STRONG>
that can be used by all server side languages. The
interface was developed
completely on Javascript DHTML and the integration is
available by <STRONG>XML</STRONG>.
In this way the developer that wants to integrate with
it doesn't have be
worried about the presentation layer of it.</P>
<H3>The Architecture</H3>
<P>The following graphic shows how the File Browser Integration
works:</P>
<P align="center"><IMG src="002/FileBrowserConnector.gif"></P>
<P align="left">The "Connector" is the main file to be
developed in this case
regarding the server side integration with the File
Browser. The following
tasks must be done by the Connector:</P>
<UL>
<UL>
<LI>
<DIV align="left">Receive the File
Manager requests.</DIV>
<LI>
<DIV align="left">Execute operations in
the File System, like folder and files
creations and listings.</DIV>
<LI>
<DIV align="left">Build the XML
response in the right format and syntax.</DIV>
<LI>
<DIV align="left">Receive and handle
file uploads from the File Browser.</DIV>
</LI>
</UL>
</UL>
<H3>The File Browser Requests</H3>
<P>All requests are simply made by the File Browser using the
normal HTTP channel.
The request info is always passed by QueryString in the
URL that reflects the
following format:</P>
<code>connector.ext?Command=<STRONG>CommandName</STRONG>&Type=<STRONG>ResourceType</STRONG>&CurrentFolder=<STRONG>FolderPath</STRONG>&ServerPath=<STRONG>ServerPath</STRONG></code>
<p><STRONG>CommandName</STRONG><BR>
Is the command the Connector must execute. For now
there are three commands
that must be handled: "GetFolders",
"GetFoldersAndFiles" and "CreateFolder".</p>
<P><STRONG>ResourceType</STRONG><BR>
The File Browser is used on many parts of the editor,
like the Link and Image
dialog boxes and in the future Flash and Multimedia
dialogs. So to
separate each "Resource Type" the following type
names are
used: "File", "Image", "Flash" and "Media".</P>
<P><STRONG>FolderPath</STRONG><BR>
Represents the path of the actual folder visible in the
File Browser. This path
is not the final URL path for that folder, but it is
relative to the Resource
Type folder. The final folder is composed by:
"Configured User Files Path" +
"Resource Type" + "Folder Path". For example, the
Folder Path "/Docs/Test/"
of resources type "Image" could correspond to
the following URL path:
"/UserFiles/Image/Docs/Test/".</P>
<P>The Folder Path must always begin and finish with a slash
("/").</P>
<P><STRONG>ServerPath</STRONG><BR>
Is the path to the root directory for the files handled
by the connector. This
is not the best approach to set the server directory to
use but its a option
the end user can have.</P>
<P>The developer is encouraged to make available an easy and
secure way to
configure the "Server Path" folder by the end user. For
example, for the
ASP.NET Connector the user can use the global
Web.config file to set witch
folder to use the file. In case of absent configuration
the Connector must use
the "/UserFiles/" folder. The Connector should also
automatically create the
folder in the case it not exists.</P>
<P>Please try to let any configuration setting to be done
outside the editor
package directory. In this way it is easy to the end
user to handle future
editor updates (just replacing the entire directory
with the new version).</P>
<H3>The Connector Responses</H3>
<P>All Connector responses have the same base XML structure,
like this:</P>
<code><?xml version="1.0" encoding="utf-8" ?>
<br>
<Connector
command="<STRONG>RequestedCommandName</STRONG>"
resourceType="<STRONG>
RequestedResourceType</STRONG>"><br>
<CurrentFolder
path="<STRONG>CurrentFolderPath</STRONG>"
url="<STRONG>CurrentFolderUrl</STRONG>" /><BR>
<STRONG><!-- Here goes all
specific command data --></STRONG>
<br>
</Connector> </code>
<P>Some important things must be considered when building the
response:</P>
<UL>
<UL>
<LI>
The response encoding must be set to "text/xml".
<LI>
The "Cache-Control" HTTP header must be set to
"no-cache". This is need because
the browsers usually cache the requests for XML
files and this is not wanted in
this case.
<LI>
The Path and the URL must always start
and finish with a slash (/).</LI></UL>
</UL>
<H3>The Commands</H3>
<P>The actual File Browser version has 3 commands that
wait for XML responses
and 1 command that wait for HTML:</P>
<UL>
<UL>
<LI>
<STRONG>GetFolders</STRONG>
(XML): gets the list of the children folders of
a folder.
<LI>
<STRONG>GetFoldersAndFiles</STRONG>
(XML): similar to the above command, gets the
list of the children folders and
files of a folder.
<LI>
<STRONG>CreateFolder</STRONG>
(XML): creates a child folder.
<LI>
<STRONG>FileUpload</STRONG> (HTML):
adds a file in a folder.</LI></UL>
</UL>
<P>Sample responses can be found in the "[Docs
Path]/contents/002/FileBrowserConnectors/SampleResponses" folder.</P>
<P><STRONG>GetFolders<BR>
</STRONG>Gets the list of the children folders of a
folder.</P>
<P>Sample Request:</P>
<code>connector.ext?Command=<STRONG>GetFolders</STRONG>&Type=<STRONG>File</STRONG>&CurrentFolder=<STRONG>/Samples/Docs/</STRONG>
</code>
<P>Sample Response:</P>
<CODE><?xml version="1.0" encoding="utf-8" ?>
<BR>
<Connector
command="<STRONG>GetFolders</STRONG>"
resourceType="<STRONG>File</STRONG>"><BR>
<CurrentFolder
path="<STRONG>/Samples/Docs/</STRONG>"
url="<STRONG>/UserFiles/File/Samples/Docs/</STRONG>"
/><BR>
<STRONG> <Folders><BR>
<Folder
name="Documents" /><BR>
<Folder
name="Files" /><BR>
<Folder
name="Other Files" /><BR>
<Folder
name="Related" /><BR>
</Folders><BR>
</STRONG></Connector> </CODE>
<P><STRONG><STRONG>GetFoldersAndFiles</STRONG>
<BR>
</STRONG>Gets the list of the children folders and
files of a folder.</P>
<P>Sample Request:</P>
<p></p>
<CODE>connector.ext?Command=<STRONG>GetFoldersAndFiles</STRONG>&Type=<STRONG>File</STRONG>&CurrentFolder=<STRONG>/Samples/Docs/</STRONG></CODE>
<P></P>
<P>Sample Response:</P>
<CODE><?xml version="1.0" encoding="utf-8" ?>
<BR>
<Connector
command="<STRONG>GetFoldersAndFiles</STRONG>"
resourceType="<STRONG>File</STRONG>"><BR>
<CurrentFolder
path="<STRONG>/Samples/Docs/</STRONG>"
url="<STRONG>/UserFiles/File/Samples/Docs/</STRONG>"
/><BR>
<STRONG> <Folders><BR>
<Folder
name="Documents" /><BR>
<Folder
name="Files" /><BR>
<Folder
name="Other Files" /><BR>
<Folder
name="Related" /><BR>
</Folders><BR>
<Files><BR>
<File name="XML
Definition.doc" size="14" /><BR>
<File
name="Samples.txt" size="5" /><BR>
<File
name="Definition.txt" size="125" /><BR>
<File
name="External Resources.drw"
size="840" /><BR>
<File
name="Todo.txt" size="2" /><BR>
</Files><BR>
</STRONG></Connector> </CODE>
<P>The file size must be expressed as KBytes (KB).</P>
<P><STRONG>CreateFolder<BR>
</STRONG>Creates a child folder.</P>
<P>Sample Request:</P>
<p></p>
<CODE>connector.ext?Command=<STRONG>CreateFolder</STRONG>&Type=<STRONG>File</STRONG>&CurrentFolder=<STRONG>/Samples/Docs/</STRONG>&NewFolderName=<STRONG>FolderName</STRONG></CODE>
<P></P>
<P>Sample Response:</P>
<CODE><?xml version="1.0" encoding="utf-8" ?>
<BR>
<Connector
command="<STRONG>CreateFolder</STRONG>"
resourceType="<STRONG>File</STRONG>"><BR>
<CurrentFolder
path="<STRONG>/Samples/Docs/</STRONG>"
url="<STRONG>/UserFiles/File/Samples/Docs/</STRONG>"
/><BR>
<STRONG> <Error number="0"
/><BR>
</STRONG></Connector> </CODE>
<P>Possible Error Numbers are:</P>
<UL>
<UL>
<LI>
<STRONG>0</STRONG>
: No Errors Found. The folder has been created.
<LI>
<STRONG>101</STRONG>
: Folder already exists.
<LI>
<STRONG>102</STRONG>
: Invalid folder name.
<LI>
<STRONG>103</STRONG>
: You have no permissions to create the folder.
<LI>
<STRONG>110</STRONG> : Unknown error
creating folder.</LI></UL>
</UL>
<P><STRONG>FileUpload<BR>
</STRONG>Adds a file in a folder.</P>
<P>This is a special command that doesn't require a XML
response. A common
"multipart/form-data" post goes with the request.
The posted file is named
"<STRONG>NewFile</STRONG>".</P>
<P>In the case a file with the same name already exists, the
Connector must
automatically rename it adding a progressive
number suffix. For
example, if the posted file is named "Test.doc", the
names to be used, in
order, are: "Test(1).doc", "Test(2).doc",
Test(3).doc"... and so on.</P>
<P>Sample Request:</P>
<CODE>connector.ext?Command=<STRONG>FileUpload</STRONG>&Type=<STRONG>File</STRONG>&CurrentFolder=<STRONG>/Samples/Docs/</STRONG></CODE>
<P>Sample Response (Simple HTML):</P>
<CODE><script type="text/javascript"><BR>
window.parent.frames['frmUpload'].OnUploadCompleted(<STRONG>0</STRONG>) ;<BR>
</script></CODE>
<p>The "OnUploadCompleted" is a JavaScript function that is
called to expose the
upload result. The possible values are:</p>
<UL>
<UL>
<LI>
OnUploadCompleted( <STRONG>0</STRONG>
) : no errors found on the upload process.
<LI>
OnUploadCompleted( <STRONG>201,
'FileName(1).ext'</STRONG>
) : the file has been uploaded successfully,
but it's name has been changed to
"FileName(1).ext".
<LI>
OnUploadCompleted( <STRONG>202</STRONG>
) : invalid file.</LI></UL>
</UL>
<H3>Configuring the Connector</H3>
<P>All connectors available in the editor package can be found
at the following
folder:
"editor/filemanager/browser/default/connectors". Each server side
language has its own folder there, with the Connector
file inside it. To choose
witch connector to use, the end-user just go to the
configuration file and
modify the following key (in this case for the Link
Dialog box):</P>
<P>FCKConfig.<STRONG>LinkBrowserURL</STRONG> =
FCKConfig.BasePath +
"filemanager/browser/default/browser.html?Connector=<STRONG>connectors/aspx/connector.aspx</STRONG>"
;</P>
<P>The Connector path is relative to the
"editor/filemanager/browser/default"
folder. The user could even written his custom
Connector and point the <STRONG>LinkBrowserURL</STRONG>
to it, like
"?Connector=/<STRONG>MyFolder/MyConnector.php</STRONG>" for
example.</P>
<HR width="100%" SIZE="1">
<H2 id="Samples">Samples</H2>
<P>The easiest way to the end user to understand how to use the
editor is to see it
in action. So it's important to make available samples
that clearly show how to
use it.</P>
<P>The developers are invited to create samples similar to that
available for the
Javascript Integration Pack. Please take a look at the
<STRONG>_samples/html</STRONG>
folder. All files must be put together in a folder
under the _samples
folder.</P>
<P>All samples should post the posted data to a single page
that shows that data.
The Javascript integration module use an ASP file,
called <STRONG>sampleposteddata.asp</STRONG>, that
does that (just because it doesn't go on server
side). That file can be
used as a reference for a custom implementation. Please
use the same file name,
like sampleposteddata.ext.</P>
<HR width="100%" SIZE="1">
<H2 id="Documentation">Documentation</H2>
<P>[ Documentation not yet available ]</P>
</STRONG>
</body>
</html>
====================================================
Index: 001.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-23 18:05:58
-->
<html>
<head>
<title>FCKeditor - Using FCKeditor with JavaScript</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>Using FCKeditor with JavaScript</H1>
<P>The "JavaScript Integration Module" is the client side
option to include
FCKeditor in your web pages. It is quite easy to use
and configure.</P>
<H3>Step 1</H3>
<P>Suppose that the editor is installed in the /FCKeditor/ path
of your web site.
The first thing to do is to include the "JavaScript
Integration Module" scripts
inside the <HEAD> of your page, just like
this:</P>
<code><script type="text/javascript"
src="<STRONG>/FCKeditor/fckeditor.js</STRONG>"></script></code>
<H3>Step 2</H3>
<P>Now the FCKeditor class is available and ready to use. There
are two ways to
create an FCKeditor in you page:</P>
<P>Method 1: The inline method (preferred): Go to the body
of your page, in
the place you want the editor to be (usually inside a
form) and place the
following script:</P>
<code><script type="text/javascript"><BR>
<STRONG> var oFCKeditor = new FCKeditor(
'FCKeditor1' ) ;<BR>
oFCKeditor.Create() ;<BR>
</STRONG></script></code>
<P>Method 2: The TEXTAREA replacement method: In the
"onload" method on your
page, add the following code to replace a existing
TEXTAREA in the page:</P>
<code><html><BR>
<head><BR>
<script
type="text/javascript"><BR>
window.onload =
function()<BR>
{<BR>
<STRONG>var
oFCKeditor = new FCKeditor(
'MyTextarea' ) ;<BR>
oFCKeditor.ReplaceTextarea()
;<BR>
</STRONG> }<BR>
</script><BR>
</head><BR>
<body><BR>
<textarea
id="<STRONG>MyTextarea</STRONG>"
name="MyTextarea">This is <b>the</b>
initial
value.</textarea><BR>
</body><BR>
</html></code>
<H3>Step 3</H3>
<P>The editor is now ready to be used. Just open the page in
your browser to see it
at work.</P>
<H2>The FCKeditor Class</H2>
<P>This is the main class used to create an instance of
FCKeditor in a web page.</P>
<div class="classDefinition">
<P><A href="#Constructor">Constructor</A></P>
<P><A href="#Properties">Properties</A></P>
<BLOCKQUOTE dir="ltr" style="MARGIN-RIGHT: 0px">
<P><A href="#pInstanceName">InstanceName</A><BR>
<A href="#pWidth">Width</A>
<BR>
<A href="#pHeight">Height</A>
<BR>
<A href="#pToolbarSet">ToolbarSet</A>
<BR>
<A href="#pValue">Value</A>
<BR>
<A href="#pBasePath">BasePath</A>
<BR>
<A
href="#pCheckBrowser">CheckBrowser</A>
<BR>
<A
href="#pDisplayErrors">DisplayErrors</A></P>
</BLOCKQUOTE>
<P><A href="#Collections">Collections</A></P>
<BLOCKQUOTE dir="ltr" style="MARGIN-RIGHT: 0px">
<P><A href="#cConfig">Config</A></P>
</BLOCKQUOTE>
<P><A href="#Methods">Methods</A></P>
<BLOCKQUOTE dir="ltr" style="MARGIN-RIGHT: 0px">
<P><A href="#mCreate">Create</A><BR>
<A
href="#mReplaceTextarea">ReplaceTextarea</A></P>
</BLOCKQUOTE>
</div>
<H3 id="Constructor">Contructor</H3>
<P class="classPropMeth">FCKeditor( instanceName[, width,
height, toolbarSet,
value] )</P>
<P>
<TABLE class="paramsDefinition" id="Table1"
cellSpacing="0" cellPadding="0" border="0">
<TR>
<TD>instanceName
</TD>
<TD>The unique name that represents the
editor instance.</TD>
</TR>
<TR>
<TD>width</TD>
<TD>the width of the editor in pixels
or percents. (Optional, Default: "100%").</TD>
</TR>
<TR>
<TD>height</TD>
<TD>the height of the editor in pixels
or percents. (Optional, Default: "200").</TD>
</TR>
<TR>
<TD>toolbarSet</TD>
<TD>the name of the Toolbar set to use.
(Optional, Default: "Default").</TD>
</TR>
<TR>
<TD>value</TD>
<TD>the initial value (HTML) of the
editor. (Optional)</TD>
</TR>
</TABLE>
</P>
<P>Example:</P>
<code>var oFCKeditor = new <STRONG>FCKeditor( 'FCKeditor1'
)</STRONG> ;</code>
<H3 id="Properties">Properties</H3>
<P class="classPropMeth" id="pInstanceName">InstanceName</P>
<P>The name of the this editor instance.</P>
<P class="classPropMeth" id="pWidth">Width</P>
<P>The width of the editor in pixels or percent. Numeric values
are handled as
pixels.</P>
<P>Default Value: "100%"</P>
<P>Examples:<BR>
<code>oFCKeditor.<STRONG>Width</STRONG> = 400 ; // 400
pixels</code> <code>oFCKeditor.<STRONG>Width</STRONG>
= "250" ; // 250 pixels</code>
<code>oFCKeditor.<STRONG>Width</STRONG> =
"80%" ; // 80 percent</code>
</P>
<P class="classPropMeth" id="pHeight">Height</P>
<P>The height of the editor in pixels or percent. Numeric
values are handled as
pixels.</P>
<P>Default Value: "200"</P>
<P>Examples:<BR>
<code>oFCKeditor.<STRONG>Height</STRONG> = 400 ; // 400
pixels</code> <code>oFCKeditor.<STRONG>Height</STRONG>
= "250" ; // 250 pixels</code>
<code>oFCKeditor.<STRONG>Height</STRONG> =
"100%" ; // 100 percent</code>
</P>
<P class="classPropMeth" id="pToolbarSet">
ToolbarSet</P>
<P>The Toolbar set to use. Refers to the configurations set at
the fckconfig.js
file.</P>
<P>Default Value: "Default"</P>
<P>Example:<BR>
<code>oFCKeditor.<STRONG>ToolbarSet</STRONG> =
"MyToolbar" ;</code></P>
<P class="classPropMeth" id="pValue">Value</P>
<P>The initial value (the HTML) to show in the editor at
startup.</P>
<P>Default Value: <empty></P>
<P>Example:<BR>
<code>oFCKeditor.<STRONG>Value</STRONG> =
"<h1>Testing</h1>This is a
<b>sample</b>." ;</code></P>
<P class="classPropMeth" id="pBasePath">
BasePath</P>
<P>The path used by the editor to find its code base. In other
words, the directory
where the editors package has been installed in your
site.</P>
<P>Default Value: "/fckeditor/"</P>
<P>Example:<BR>
<code>oFCKeditor.<STRONG>BasePath</STRONG> =
"/Components/FCKeditor/" ;</code></P>
<P>Remarks:<BR>
Avoid using relative paths. It is preferable to set the
base path starting from
the root (/). Always finish the path with a slash
(/).</P>
<P class="classPropMeth" id="pCheckBrowser">
CheckBrowser</P>
<P>Tells this class instance to check the browser compatibility
when rendering the
editor.</P>
<P>Default Value: true</P>
<P>Example:<BR>
<code>oFCKeditor.<STRONG>CheckBrowser</STRONG> = true
;</code></P>
<P>Remarks:<BR>
This option could be useful if the check was made
at the server side.</P>
<P class="classPropMeth" id="pDisplayErrors">
DisplayErrors</P>
<P>Tells this class instance to show error messages on errors
while rendering the
editor.</P>
<P>Default Value: true</P>
<P>Example:<BR>
oFCKeditor.<STRONG>DisplayErrors</STRONG> = false
;</CODE></P>
<H3 id="Collections">Collections</H3>
<P class="classPropMeth" id="cConfig">Config[ key ] = value</P>
<P>This collection holds all configurations set in the editor
instance.</P>
<P>Example:<br>
<code>oFCKeditor.<STRONG>Config[ "AutoDetectLanguage"
]</STRONG> = false ;<BR>
oFCKeditor.<STRONG>Config[ "DefaultLanguage"
]</STRONG> = "pt-BR" ;</code></P>
<H3 id="Methods">Methods</H3>
<P class="classPropMeth" id="mCreate">
Create()</P>
<P>Builds and outputs the editor in the exact place where its
called.</P>
<P>Example:<BR>
<code>oFCKeditor.<STRONG>Create()</STRONG> ;</code></P>
<P class="classPropMeth" id="mReplaceTextarea">
ReplaceTextarea()</P>
<P>
Replaces an existing <TEXTAREA> in the page with
the
FCKeditor instance. The Textarea must has
its "id" set to the editor InstanceName. The the
"id" is not
found, the editor uses the TEXTAREA "name" for the
replacement.</P>
<P>Example:<BR>
<code>window.onload = function()<BR>
{<BR>
var oFCKeditor = new FCKeditor(
'<STRONG>MyTextarea</STRONG> ' ) ;<BR>
oFCKeditor.<STRONG>ReplaceTextarea()</STRONG>
;<BR>
}<BR>
...<BR>
<textarea id="<STRONG>MyTextarea</STRONG>"
name= "MyTextarea">This is
<b>the</b> initial
value.</textarea></code>
</P>
<p>
If you are intended to post the editor contents throw a
form (the most obvious
use of the editor), you must set the "name" attribute
of the TEXTAREA. It is
useful, to not get confused, to use the same value
used in the "id"
attribute.
</p>
</body>
</html>
====================================================
Index: 008.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-19 18:14:12
-->
<html>
<head>
<title>FCKeditor - Scripts Compression</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>Scripts Compression</H1>
<P>The editor scripts source can be found in the package
at the
"editor/_source/" directory. It is "human readable" as
well as
commented. There are a lot of files there that are
organized on groups.</P>
<P>
To maximize loading and execution performance,
the production
distribution code in compressed on
<STRONG>fewer</STRONG> and <STRONG>smaller</STRONG>
files, as described on "<A
href="003.html">Performance</A>". These files can be
found at the "editor/js/" directory.</P>
<H3>How to develop using the "_source" files?</H3>
<P>It is possible to run the editor using the original
scripts in the
"_source" directory. It is usefull when developing or
debugging the
editor. It is quite easy to do that. Just go
the "editor" directory
and overwrite <STRONG>fckeditor.html</STRONG> with
<STRONG>fckeditor.original.html</STRONG>
(remember to backup the first one).</P>
<P>So, to start using again the "compressed" files, just
recover the backup
"fckeditor.html" file.</P>
<H3>Generating the compressed scripts</H3>
<P>
An application has been developed to make it easy to
update the compressed file
in the "js" directory. It is called
"<STRONG>FCKeditor.Packager</STRONG>". You can find it in the
"_packager" directory.
<P>Further documentation (readme) is available in the
"_packager" directory itself.</P>
</body>
</html>
====================================================
Index: 009.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-10 18:17:17
-->
<html>
<head>
<title>FCKeditor - Support</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>Support</H1>
<H3>E-Mail Support</H3>
<P>Donators that make an offer of minimum Euro 150,00 will
automatically receive <STRONG>
1 year of e-mail support</STRONG>.
<BR>
It is easy to donate and you can do it online, right
now. Take a look at our <A href="http://www.fckeditor.net/donate/";
target="_blank">
Donation</A> pages. E-Mail support is available
only upon this system.
</P>
<H3>Online Resources</H3>
<P>This project is also hosted by <A
href="http://sourceforge.net/projects/fckeditor/"; target="_blank">
Sourceforge</A>. A big knowledge base
has been build there, so
use it to find out solutions or discuss about your
problems with the
community, or just leave some words about FCKeditor.
Please use the following
links:
</P>
<UL>
<LI>
<A
href="https://sourceforge.net/tracker/?group_id=75348&atid=543654?group_id=75348&atid=543654";
target="_blank">Support
Requests</A></LI>
<LI>
<A
href="https://sourceforge.net/tracker/?group_id=75348&atid=543653?group_id=75348&atid=543653";
target="_blank">Bugs Reporting</A></LI>
<LI>
<A
href="https://sourceforge.net/forum/?group_id=75348?group_id=75348";
target="_blank">
Discussion Forums</A></LI></UL>
</body>
</html>
====================================================
Index: 010.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-10 18:21:29
-->
<html>
<head>
<title>FCKeditor - License</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>License</H1>
<P>This library is free software; you can redistribute it
and/or modify it
under the terms of the <STRONG>GNU Lesser General
Public (<A href="http://www.opensource.org/licenses/lgpl-license.php";
target="_blank">LGPL</A>)
License</STRONG> as published by the Free
Software Foundation; either
version 2.1 of the License, or any later version.</P>
<P>This library is distributed in the hope that it will be
useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE. See the GNU Lesser General
Public License for more
details.</P>
<P>You should have received a copy of the GNU Lesser General
Public License along
with this library; if not, write to the Free Software
Foundation, Inc., 59
Temple Place, Suite 330, Boston, MA 02111-1307 USA
</P>
<H3>Key Concepts</H3>
<P>The key concepts of the LGPL license are:</P>
<UL>
<LI>
You have all rights to execute the program
for any need.</LI>
<LI>
You have all rights to study and modify the
program to your needs.</LI>
<LI>
You have all rights to distribute copies of the
original packages to help
people.</LI>
<LI>
You have all rights to develop the library an
make it better. You must puslish
your changes under the LGPL license.</LI>
<LI>
You must not change or remove any copyright and
notices and disclaimer of
warranty from the original files.</LI>
<LI>
Programs that use or link this library can be
licensed under terms of your
choice, including proprietary, commercial,
software.</LI>
<LI>
<DIV class="tiny">If you copy or distribute the
library, you must accompany it with
the complete corresponding
machine-readable source code or with a written
offer, valid for at least three years,
to furnish the complete corresponding
machine-readable source code. You need
not provide source code to programs
which link to the library.</DIV>
</LI>
</UL>
<P class="tiny">The above list doesn't represent the actual
licensing terms.
For precise and deep information, please refer to
the complete LGPL
license text. It can be found at <A
href="http://www.opensource.org/licenses/lgpl-license.php"; target="_blank">
http://www.opensource.org/licenses/lgpl-license.php</A>.</P>
<H3>Copyright</H3>
<P>All files distributed by the project are copywritten to
"<STRONG>Frederico Caldeira
Knabben</STRONG>", except when explicetelly
indicated.</P>
</body>
</html>
====================================================
Index: 011.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-10 19:04:40
-->
<html>
<head>
<title>FCKeditor - License</title>
<link href="../fck_docs.css" type="text/css" rel="stylesheet">
</head>
<body>
<H1>Spell Checker</H1>
<P>FCKeditor comes with bult-in integration with two spell
checkers: <STRONG>ieSpell</STRONG>
and <STRONG>Speller Pages</STRONG>. In this page you
will find some info about
these spell checkers and how to configure then.</P>
<H3>ieSpell</H3>
<P>As the name says, ieSpell is an extension for Internet
Explorer
that makes possible to make spell checking at client
side. It is quite simple
and efficient, but it runs on IE/Windows only.</P>
<P>To use ieSpell just set the following configuration ad
fckconfig.js:</P>
<P><code>FCKConfig.SpellChecker = '<STRONG>ieSpell</STRONG>'
;</code>
</P>
<P>At the first time a user run the Spell Checker, he/she will be automatically
informed that ieSpell is not installed and will be redirected to the download
URL (the URL can also be configured).</P>
<P>When running FCKeditor with ieSpell over browsers different than
IE/Win, the "Check Spell" button will be automaticaly disabled.</P>
<P>Attention, ieSpell is free for personal use. Commercial licenses are
available for very low prices. For more info about ieSpell, its licensing,
configurations and more, go to <A href="http://www.iespell.com/";
target="_blank">http://www.iespell.com/</A>.</P>
<H3>Speller Pages</H3>
<P>
Speller Pages is a free, Open Source, server side spell
checker that uses the powerfull <A href="http://aspell.net/"; target="_blank">GNU
Aspell</A> engine for the hard work. This
should be the preferred spell checker, but it requires some server side
configurations (this is why it is not set as the default one).</P>
<P>To use ieSpell just set the following configuration ad fckconfig.js:</P>
<P><CODE>FCKConfig.SpellChecker = '<STRONG>SpellerPages</STRONG>' ;</CODE> </P>
<P>FCKeditor uses a customized version of Speller Pages, so any specific
configuration must be done in the files found at:
editor/dialog/fck_spellerpages/spellerpages. All changed lines have been marked
with a "by FredCK" comment.
<P>The files included in the package are set to run over Windows with PHP.
Usefull inforrmation about Windows configurations can be found here: <A
href="http://sourceforge.net/docman/display_doc.php?docid=19473&group_id=86602";
target="_blank">Windows/PHP Installation Instructions</A>.
<P>For more info about Speller Pages, its licensing, installation,
configurations and more, go to <A href="http://spellerpages.sourceforge.net/";
target="_blank">http://spellerpages.sourceforge.net/</A>.</P>
</body>
</html>
====================================================
Index: 012.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
* FCKeditor - The text editor for internet
* Copyright (C) 2003-2004 Frederico Caldeira Knabben
*
* Licensed under the terms of the GNU Lesser General Public License:
* http://www.opensource.org/licenses/lgpl-license.php
*
* For further information visit:
* http://www.fckeditor.net/
*
* Version: 2.0 RC3
* Modified: 2005-02-17 13:30:10
-->
<html>
<head>
<title>FCKeditor - Configuration File</title>
<style>
.ConfigTable TD { padding-top: 15px }
.ConfigTable UL { margin-top: 0px; margin-bottom: 0px }
.ConfigTable OL { margin-top: 0px; margin-bottom: 0px }
</style>
</head>
<body>
<h1>Configurations File</h1>
<p>The editor comes with a rich set of configurations that
makes it possible to
customize its appearance, features and behaviors. The
main configuration file
is named "<strong>fckconfig.js</strong>".</p>
<p>You can edit the main configuration file or override just
your required
configurations in a separated file. Javascript syntax
is used to set the
configurations.</p>
<h3>Overriding the Default Configurations</h3>
<p>To make it easier to make future updates of FCKeditor over
your sites, the best
approach is to put all your configurations in a
separated file, outside the
editor's package directory structure. In this way, you
just need to overwrite
the editor's directory to update it to a newer
version.</p>
<p>For example, suppose you want to force FCKeditor to always
use the French
language for its interface. To do so, you just need to
create a file called,
for example, "myconfig.js" and put it in the root
directory of the site (or
wherever you want). Inside the file you just write the
following lines:</p>
<p><code>FCKConfig.AutoDetectLanguage = <strong>false</strong>
;<br>
FCKConfig.DefaultLanguage =
'<strong>fr</strong>' ;</code>
</p>
<p>Now we have to tell the editor that it has to load my
custom
configurations. The first way to do that is changing
the following line in the
main configuration file (fckconfig.js):</p>
<p><code>FCKConfig.CustomConfigurationsPath
= '<strong>/myconfig.js</strong>' ;<br>
</code>
</p>
<p>The above method is good, but, as you can imagine, you loose
the facility to not
touch the original files. In any case it is easier to
remember that you just
need to change one line, and all the other things
remain separated.</p>
<p>There is a even better way to have the same results
described above, but without
touching the fckconfig.js file. You can set the custom
configurations path from
the page that uses the editor. For example, with
Javascript, you could do
something like this:</p>
<p><code>var oFCKeditor = new FCKeditor( 'FCKeditor1' ) ;<br>
<strong>oFCKeditor.Config['CustomConfigurationsPath']
= '/myconfig.js' ;</strong><br>
oFCKeditor.Create() ;<br>
</code>
</p>
<p>The same method can be used with your preferred server side
language. Take a
look at the samples to find out how to manipulate the
configurations by code.</p>
<p>When overriding configurations, the following steps are
done:</p>
<ol>
<ol>
<li>
The configurations in the main configuration file
(fckconfig.js) are
loaded.
<li>
The configurations are overridden by that ones
available in the custom
configuration file (if provided).
<li>
The configurations are overridden by that one
set in the editor page (if
provided), except for the
"CustomConfigurationsPath", that is set after step 1.</li></ol>
</OL>
<p><strong>Important: remember to reset your browser cache when
doing changes to the
configurations file, otherwise you may not see
your changes.</strong></p>
<h3>Configurations Options</h3>
<p>The following list describes all possible configurations
found in the
fckconfig.js file:</p>
<table cellspacing="5" cellpadding="0" width="90%" border="0"
align="center" class="ConfigTable">
<tr>
<td valign="top"><strong>AutoDetectLanguage<br>
</strong>(true / false)</td>
<td valign="top">When set to "true", tells
the editor to automatically detect
the user language preferences to adapt
its interface language.<br>
With Internet Explorer, the
language configured in the Windows Control
Panel is used.<br>
With Firefox, the browser language
is used.</td>
</tr>
<tr>
<td valign="top"><strong> BaseHref<br>
</strong>(string)</td>
<td valign="top">
Base URL used to resolve links (on
images, links, styles, etc.).<br>
For example, if BaseHref is set to
'http://www.fredck.com', an image that
points to "/images/Logo.gif" will be
interpreted by the editor as
"http://www.fredck.com/images/Logo.gif";, without touching the "src" attribute
of the image.</td>
</tr>
<tr>
<td valign="top"><strong>
ContentLangDirection<br>
</strong>('ltr' / 'rtl')</td>
<td valign="top">
Sets the direction of the editor area
contents. The possible values are:
<ul>
<li>
ltr - Left to Right
<li>
rtl - Right to
Left</li></ul>
</td>
</tr>
<tr>
<td valign="top">
<strong>ContextMenu<br>
</strong>(string array)</td>
<td valign="top">
Sets the list of active options in the
context menu.<br>
</td>
</tr>
<tr>
<td valign="top">
<strong>CustomConfigurationsPath<br>
</strong>(string)</td>
<td valign="top">
Sets the path of a custom file that can
override some configurations. Leave it
empty to ignore.<br>
It is recommended to use absolute paths
(starting with /), like
"/myfckconfig.js".</td>
</tr>
<tr>
<td valign="top">
<strong>Debug<br>
</strong>(true / false)</td>
<td valign="top">
Enables the debug window to be shown
when calling the FCKDebug.Output()
function.</td>
</tr>
<tr>
<td valign="top">
<strong>DefaultLanguage<br>
</strong>(string)</td>
<td valign="top">
Sets the default language used for the
editor's interface localization.<br>
The default language is used when the
AutoDetectLanguage options is disabled or
when the user language is not
available.</td>
</tr>
<tr>
<td valign="top">
<strong>EditorAreaCSS<br>
</strong>(string)</td>
<td valign="top">
Set the CSS styles file to be used in
the editing area. In this way you can
point to a file that reflects your web
site styles.</td>
</tr>
<tr>
<td valign="top">
<strong>EnableSourceXHTML<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", tells the editor to
process the HTML source to XHTML when
switching from WYSIWYG to Source
view.</td>
</tr>
<tr>
<td valign="top">
<strong>EnableXHTML<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", tells the editor to
process the HTML source to XHTML on
form post.</td>
</tr>
<tr>
<td valign="top">
<strong>FillEmptyBlocks<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", block elements
(like P, DIV, H1, PRE, etc...) are forced to
have content (a &nbsp;).<br>
Empty blocks are "collapsed" by while
browsing, so a empty <p></p>
is not visible. While editing, the
editor "expand" empty blocks so you can
insert content inside
then. Setting this option to
"true" results useful to reflect
the same output when browsing and
editing.</td>
</tr>
<tr>
<td valign="top">
<strong>FontColors<br>
</strong>(string)</td>
<td valign="top">
Sets the colors that must be shown in
the colors panels (in the toolbar).</td>
</tr>
<tr>
<td valign="top">
<strong>FontFormats<br>
</strong>(string)</td>
<td valign="top">
Sets the list of formats to be shown in
the "Format" toolbar command.</td>
</tr>
<tr>
<td valign="top">
<strong>FontNames<br>
</strong>(string)</td>
<td valign="top">
Sets the list of fonts to be shown in
the "Font" toolbar command.</td>
</tr>
<tr>
<td valign="top">
<strong>FontSizes<br>
</strong>(string)</td>
<td valign="top">
Sets the list of font sizes to be shown
in the "Size" toolbar command.</td>
</tr>
<tr>
<td valign="top">
<strong>ForcePasteAsPlainText<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", converts the
clipboard contents to pure text on pasting
operations.</td>
</tr>
<tr>
<td valign="top">
<strong>ForceSimpleAmpersand<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", on XHTML
processing, forces the ampersands (&) on tags
attributes to not be converted to
"&amp;". This conversion is a W3C
requirement for XHTML, so it is
recommended to leave this option to "false".</td>
</tr>
<tr>
<td valign="top">
<strong>FormatIndentator<br>
</strong>(string)</td>
<td valign="top">
Sets the characters to be used when
indenting the HTML source when
formatting it. Useful values are a
sequence of spaces
(' ') or a tab
char ('\t').</td>
</tr>
<tr>
<td valign="top">
<strong>FormatOutput<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", the output HTML
generated by the editor will be processed
and formatted.</td>
</tr>
<tr>
<td valign="top">
<strong>FormatSource<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", the HTML shown
by the editor, while switching from
WYSIWYG to Source views, will be
processed and formatted.</td>
</tr>
<tr>
<td valign="top">
<strong>FullPage<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", enables full page
editing (from <HTML> to
</HTML>). It also enables the
"Page Properties" toolbar button.</td>
</tr>
<tr>
<td valign="top">
<strong>GeckoUseSPAN<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", tells Gecko
browsers to use SPAN instead of <B>.
<I> and <U> for bold,
italic an underline.</td>
</tr>
<tr>
<td valign="top">
<strong>IeSpellDownloadUrl<br>
</strong>(string)</td>
<td valign="top">
Points the editor to the URL used to
download the ieSpell program setup.</td>
</tr>
<tr>
<td valign="top">
<strong>ImageBrowser<br>
</strong>(true / false)</td>
<td valign="top">
If set to "true", the "Browse Server"
button is visible in the "Image" dialog
window.</td>
</tr>
<tr>
<td valign="top">
<strong>ImageBrowserURL<br>
</strong>(string)</td>
<td valign="top">
Sets the URL of the page called when
the user clicks the "Browse Server" button
in the "Image" dialog window.<br>
In this way, you can create your custom
Image Browser that is well integrated
with your system.</td>
</tr>
<tr>
<td valign="top">
<strong>ImageBrowserWindowHeight<br>
</strong>(number)</td>
<td valign="top">
Sets the height, in pixels, of the
"Image Browser" window (shown when the
"Browse Server" button is clicked in
the Image dialog window.</td>
</tr>
<tr>
<td valign="top">
<strong>ImageBrowserWindowWidth<br>
</strong>(number)</td>
<td valign="top">
Sets the width, in pixels, of the
"Image Browser" window (shown when the
"Browse Server" button is clicked in
the Image dialog window.</td>
</tr>
<tr>
<td valign="top">
<strong>LinkBrowser<br>
</strong>(true / false)</td>
<td valign="top">
If set to "true", the "Browse Server"
button is visible in the "Link" dialog
window.</td>
</tr>
<tr>
<td valign="top">
<strong>LinkBrowserURL<br>
</strong>(string)</td>
<td valign="top">
Sets the URL of the page called when
the user clicks the "Browse Server" button
in the "Link" dialog window.<br>
In this way, you can create your custom
File Browser that is well integrated
with your system.</td>
</tr>
<tr>
<td valign="top">
<strong>LinkBrowserWindowHeight<br>
</strong>(number)</td>
<td valign="top">
Sets the height, in pixels, of the
"File Browser" window (shown when the
"Browse Server" button is clicked in
the Link dialog window.</td>
</tr>
<tr>
<td valign="top">
<strong>LinkBrowserWindowWidth<br>
</strong>(number)</td>
<td valign="top">
Sets the height, in pixels, of the
"File Browser" window (shown when the
"Browse Server" button is clicked in
the Link dialog window.</td>
</tr>
<tr>
<td valign="top">
<strong>Plugins<br>
</strong>(object)</td>
<td valign="top">
With this object you can register the
plugins to be loaded by the editor
calling it "Add()" function.</td>
</tr>
<tr>
<td valign="top">
<strong>PluginsPath<br>
</strong>(string)</td>
<td valign="top">
Sets the base path used when looking
for registered plugins.</td>
</tr>
<tr>
<td valign="top">
<strong>ShowBorders<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", show "fake" table
and cells borders on table that has the
border attribute set to zero.</td>
</tr>
<tr>
<td valign="top">
<strong>SkinPath<br>
</strong>(string)</td>
<td valign="top">
Sets the path to the skin (graphical
interface settings) to be used by the
editor.</td>
</tr>
<tr>
<td valign="top">
<strong>SmileyColumns<br>
</strong>(number)</td>
<td valign="top">
Sets the number of columns to be shown
in the "Smiley" dialog window.</td>
</tr>
<tr>
<td valign="top">
<strong>SmileyImages<br>
</strong>(string array)</td>
<td valign="top">
Sets the list of images to available in
the "Smiley" dialog window.</td>
</tr>
<tr>
<td valign="top">
<strong>SmileyPath<br>
</strong>(string)</td>
<td valign="top">
Sets the base path for the smiles
images.</td>
</tr>
<tr>
<td valign="top">
<strong>SmileyWindowHeight<br>
</strong>(number)</td>
<td valign="top">
Sets the height, in pixels, of the
"Smiley" dialog window.</td>
</tr>
<tr>
<td valign="top">
<strong>SmileyWindowWidth<br>
</strong>(number)</td>
<td valign="top">
Sets the width, in pixels, of the
"Smiley" dialog window.</td>
</tr>
<tr>
<td valign="top">
<strong>SpellChecker<br>
</strong>('ieSpell' /
'SpellerPages')</td>
<td valign="top">
Sets the spell checker to be used on
spell checking operations. For more info, <a href="011.html">
click here</a>.</td>
</tr>
<tr>
<td valign="top">
<strong>StartupFocus<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", forces the
editor to get the keyboard input focus
on startup (page load).</td>
</tr>
<tr>
<td valign="top">
<strong>StylesXmlPath<br>
</strong>(string)</td>
<td valign="top">
Sets the path to the XML file that has
the definitions and rules of the
styles used by the "Style" toolbar
command. For more info, <a href="006.html">click
here</a>.</td>
</tr>
<tr>
<td valign="top">
<strong>TabSpaces<br>
</strong>(number)</td>
<td valign="top">
Set the number of spaces (&nbsp;)
to be inserted when the user hits the
"tab" key.<br>
This is an Internet Explorer only
feature. Other browsers insert spaces
automatically by default.</td>
</tr>
<tr>
<td valign="top">
<strong>ToolbarCanCollapse<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", tells the editor
that the toolbar can be Collapsed/Expanded
by the user when clicking the vertical
bar placed on the left of it (on the
right for "rtl" languages).</td>
</tr>
<tr>
<td valign="top">
<strong>ToolbarSets<br>
</strong>(object)</td>
<td valign="top">
With this object you can define which
items to be shown in the toolbar. You can
define more than one toolbar in the
configuration file.<br>
</td>
</tr>
<tr>
<td valign="top">
<strong>ToolbarStartExpanded<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", the toolbar is
Expanded on startup, otherwise it is
Collapsed and the user must click on it
to show it.</td>
</tr>
<tr>
<td valign="top">
<strong>UseBROnCarriageReturn<br>
</strong>(true / false)</td>
<td valign="top">
When set to "true", inserts a
<BR> tag when the user hits the "enter"
key, instead of starting a new
paragraph (<P> or <DIV>).<br>
This is an Internet Explorer only
feature. Other browsers insert the <BR>
tag by default.</td>
</tr>
</table>
</body>
</html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Phpgroupware-cvs] news_admin/js/fckeditor/_docs/contents 004.html, 1.1 005.html, 1.1 006.html, 1.1 007.html, 1.1 003.html, 1.1 002.html, 1.1 001.html, 1.1 008.html, 1.1 009.html, 1.1 010.html, 1.1 011.html, 1.1 012.html, 1.1,
skwashd <=
- Prev by Date:
[Phpgroupware-cvs] news_admin/js/fckeditor/editor/_source/internals fckselection_gecko.js, 1.1 fckselection_ie.js, 1.1 fcktablehandler.js, 1.1 fcktablehandler_gecko.js, 1.1 fckselection.js, 1.1 fckscriptloader.js, 1.1 fckdialog_ie.js, 1.1 fcklanguagemanager.js, 1.1 fckplugins.js, 1.1 fckregexlib.js, 1.1 fcktablehandler_ie.js, 1.1 fcktoolbaritems.js, 1.1 fckxhtml.js, 1.1 fckxhtml_gecko.js, 1.1 fckxhtml_ie.js, 1.1 fckxhtmlentities.js, 1.1 fckurlparams.js, 1.1 fcktools_ie.js, 1.1 fcktoolbarset.js, 1.1 fcktools.js, 1.1 fcktools_gecko.js, 1.1 fckdialog_gecko.js, 1.1 fckdialog.js, 1.1 fck_1_ie.js, 1.1 fck_2.js, 1.1 fck_2_gecko.js, 1.1 fck_2_ie.js, 1.1 fck_1_gecko.js, 1.1 fck_1.js, 1.1 fck.js, 1.1 fck_last.js, 1.1 fck_onload.js, 1.1 fckcontextmenu_gecko.js, 1.1 fckcontextmenu_ie.js, 1.1 fckcoreextensions.js, 1.1 fckdebug.js, 1.1 fckcontextmenu.js, 1.1 fckconfig.js, 1.1 fckbrowserinfo.js, 1.1 fckcodeformatter.js, 1.1 fckcommands.js, 1.1
- Next by Date:
[Phpgroupware-cvs] news_admin/js/fckeditor/editor/images/smiley/fun rasta2.gif, 1.1 rastapop.gif, 1.1 rosebud.gif, 1.1 sad.gif, 1.1 question2.gif, 1.1 question.gif, 1.1 obanon.gif, 1.1 ouaip.gif, 1.1 pleure.gif, 1.1 plugin.gif, 1.1 sad2.gif, 1.1 shocked.gif, 1.1 smiley_peur.gif, 1.1 sors.gif, 1.1 sovxx.gif, 1.1 spamafote.gif, 1.1 smile.gif, 1.1 sleep.gif, 1.1 sick.gif, 1.1 sick2.gif, 1.1 slaap.gif, 1.1 nuts.gif, 1.1 notify.gif, 1.1 icon12.gif, 1.1 icon23.gif, 1.1 icon26.gif, 1.1 icon_angel.gif, 1.1 happy.gif, 1.1 halm.gif, 1.1 double0smile.gif, 1.1 eek3.gif, 1.1 eltaf.gif, 1.1 gele.gif, 1.1 icon_bandit.gif, 1.1 icon_bravo.gif, 1.1 mad.gif, 1.1 megaphone.gif, 1.1 mmm.gif, 1.1 music.gif, 1.1 love.gif, 1.1 lol3.gif, 1.1 icon_clown.gif, 1.1 jesors.gif, 1.1 jesors1.gif, 1.1 tap67.gif, 1.1 thumbdown.gif, 1.1 urgeman.gif, 1.1 vanadium.gif, 1.1 wink.gif, 1.1 worship.gif, 1.1 tuffgong.gif, 1.1 tongue.gif, 1.1 thumbup.gif, 1.1 tigi.gif, 1.1 toad666.gif, 1.1 wouaf.gif, 1.1 wow.gif, 1.1 zoor.gif, 1.1 youpi.gif, 1.1 xp1700.gif, 1.1 yltype.gif, 1.1 yopyopyop. gif, 1.1 devil2.gif, 1.1 devil.gif, 1.1 asthanos.gif, 1.1 bazuzeus.gif, 1.1 beaute.gif, 1.1 bigsmile.gif, 1.1 assjani.gif, 1.1 apophys.gif, 1.1 alien.gif, 1.1 alien2.gif, 1.1 angry.gif, 1.1 angry1.gif, 1.1 blush.gif, 1.1 boid.gif, 1.1 cool.gif, 1.1 crazy.gif, 1.1 cwm14.gif, 1.1 demis_roussos.gif, 1.1 confused.gif, 1.1 capo.gif, 1.1 bonk.gif, 1.1 bored.gif, 1.1 borg.gif, 1.1 ak.gif, 1.1 aiua.gif, 1.1
- Previous by thread:
[Phpgroupware-cvs] news_admin/js/fckeditor/editor/_source/internals fckselection_gecko.js, 1.1 fckselection_ie.js, 1.1 fcktablehandler.js, 1.1 fcktablehandler_gecko.js, 1.1 fckselection.js, 1.1 fckscriptloader.js, 1.1 fckdialog_ie.js, 1.1 fcklanguagemanager.js, 1.1 fckplugins.js, 1.1 fckregexlib.js, 1.1 fcktablehandler_ie.js, 1.1 fcktoolbaritems.js, 1.1 fckxhtml.js, 1.1 fckxhtml_gecko.js, 1.1 fckxhtml_ie.js, 1.1 fckxhtmlentities.js, 1.1 fckurlparams.js, 1.1 fcktools_ie.js, 1.1 fcktoolbarset.js, 1.1 fcktools.js, 1.1 fcktools_gecko.js, 1.1 fckdialog_gecko.js, 1.1 fckdialog.js, 1.1 fck_1_ie.js, 1.1 fck_2.js, 1.1 fck_2_gecko.js, 1.1 fck_2_ie.js, 1.1 fck_1_gecko.js, 1.1 fck_1.js, 1.1 fck.js, 1.1 fck_last.js, 1.1 fck_onload.js, 1.1 fckcontextmenu_gecko.js, 1.1 fckcontextmenu_ie.js, 1.1 fckcoreextensions.js, 1.1 fckdebug.js, 1.1 fckcontextmenu.js, 1.1 fckconfig.js, 1.1 fckbrowserinfo.js, 1.1 fckcodeformatter.js, 1.1 fckcommands.js, 1.1
- Next by thread:
[Phpgroupware-cvs] news_admin/js/fckeditor/editor/images/smiley/fun rasta2.gif, 1.1 rastapop.gif, 1.1 rosebud.gif, 1.1 sad.gif, 1.1 question2.gif, 1.1 question.gif, 1.1 obanon.gif, 1.1 ouaip.gif, 1.1 pleure.gif, 1.1 plugin.gif, 1.1 sad2.gif, 1.1 shocked.gif, 1.1 smiley_peur.gif, 1.1 sors.gif, 1.1 sovxx.gif, 1.1 spamafote.gif, 1.1 smile.gif, 1.1 sleep.gif, 1.1 sick.gif, 1.1 sick2.gif, 1.1 slaap.gif, 1.1 nuts.gif, 1.1 notify.gif, 1.1 icon12.gif, 1.1 icon23.gif, 1.1 icon26.gif, 1.1 icon_angel.gif, 1.1 happy.gif, 1.1 halm.gif, 1.1 double0smile.gif, 1.1 eek3.gif, 1.1 eltaf.gif, 1.1 gele.gif, 1.1 icon_bandit.gif, 1.1 icon_bravo.gif, 1.1 mad.gif, 1.1 megaphone.gif, 1.1 mmm.gif, 1.1 music.gif, 1.1 love.gif, 1.1 lol3.gif, 1.1 icon_clown.gif, 1.1 jesors.gif, 1.1 jesors1.gif, 1.1 tap67.gif, 1.1 thumbdown.gif, 1.1 urgeman.gif, 1.1 vanadium.gif, 1.1 wink.gif, 1.1 worship.gif, 1.1 tuffgong.gif, 1.1 tongue.gif, 1.1 thumbup.gif, 1.1 tigi.gif, 1.1 toad666.gif, 1.1 wouaf.gif, 1.1 wow.gif, 1.1 zoor.gif, 1.1 youpi.gif, 1.1 xp1700.gif, 1.1 yltype.gif, 1.1 yopyopyop. gif, 1.1 devil2.gif, 1.1 devil.gif, 1.1 asthanos.gif, 1.1 bazuzeus.gif, 1.1 beaute.gif, 1.1 bigsmile.gif, 1.1 assjani.gif, 1.1 apophys.gif, 1.1 alien.gif, 1.1 alien2.gif, 1.1 angry.gif, 1.1 angry1.gif, 1.1 blush.gif, 1.1 boid.gif, 1.1 cool.gif, 1.1 crazy.gif, 1.1 cwm14.gif, 1.1 demis_roussos.gif, 1.1 confused.gif, 1.1 capo.gif, 1.1 bonk.gif, 1.1 bored.gif, 1.1 borg.gif, 1.1 ak.gif, 1.1 aiua.gif, 1.1
- Index(es):