Index: /FCKeditor.Java/trunk/src/site/apt/connector.apt =================================================================== --- /FCKeditor.Java/trunk/src/site/apt/connector.apt (revision 3078) +++ /FCKeditor.Java/trunk/src/site/apt/connector.apt (revision 3079) @@ -24,7 +24,15 @@ Connector - Bla bla.. + The integration pack offers you to provide an arbitrary file storage location + for files accessed/stored from the File Browser. Read on to see how you can refit the system to your needs: + +* Rationale + + Hard-coded file locations can be cumbersome under certain circumstances. You may + need to change the storage path on-the-fly or serve paths on a user/request + basis. you are able to calculate the absolute storage path as well as the responded + URL the way you want according to the underlying {{{connector.html}Connector}}. * The interface @@ -40,9 +48,9 @@ * {{{java-core/apidocs/net/fckeditor/connector/impl/AbstractLocalFileSystemConnector.html}<<>>}} (abstract class): - A standard stub implementation of a connector according to the + A standard stub implementation of a connector according to the {{{http://docs.fckeditor.net/FCKeditor_2.x/Developers_Guide/Server_Side_Integration#The_Commands}Server Side Integration}} It may serve you as a skeleton for your implementation as it does for the - two upcoming. - + two upcoming. + * {{{java-core/apidocs/net/fckeditor/connector/impl/ContextConnector.html}<<>>}} (default): A connector serving all files from the current context. @@ -70,5 +78,5 @@ A connector (at least a predefined one) interacts very closely with a <<>> implementation, great care must be excercised while choosing an implementation - and userpath properties configuration. An improper configuration may result + and userpath properties configuration. An improper configuration may result in erroneous and undefined behavior. See {{{userpathbuilder.html}UserPathBuilder}} for more details. Index: /FCKeditor.Java/trunk/src/site/apt/connector_servlet.apt =================================================================== --- /FCKeditor.Java/trunk/src/site/apt/connector_servlet.apt (revision 3078) +++ /FCKeditor.Java/trunk/src/site/apt/connector_servlet.apt (revision 3079) Index: /FCKeditor.Java/trunk/src/site/apt/download.apt.vm =================================================================== --- /FCKeditor.Java/trunk/src/site/apt/download.apt.vm (revision 3078) +++ /FCKeditor.Java/trunk/src/site/apt/download.apt.vm (revision 3079) @@ -19,5 +19,5 @@ ~~ @version $Id: installation.apt.vm 2162 2008-07-03 18:11:08Z mosipov $ ------------------------------ - Download + Download ------------------------------ Index: /FCKeditor.Java/trunk/src/site/apt/ext_overview.apt =================================================================== --- /FCKeditor.Java/trunk/src/site/apt/ext_overview.apt (revision 3078) +++ /FCKeditor.Java/trunk/src/site/apt/ext_overview.apt (revision 3079) @@ -32,7 +32,7 @@ * <>: Gives you full control over any action the user can do in the File Browser. - + * <>: Enables you to construct a user-dependent file path. - + * <>: Gives you the ability to handle server-side connector requests the way you want. @@ -42,5 +42,5 @@ [] - + Please read the extending parts carefully if you intend to deploy the FCKeditor in a particular system! Index: /FCKeditor.Java/trunk/src/site/apt/index.apt =================================================================== --- /FCKeditor.Java/trunk/src/site/apt/index.apt (revision 3078) +++ /FCKeditor.Java/trunk/src/site/apt/index.apt (revision 3079) Index: /FCKeditor.Java/trunk/src/site/apt/properties.apt =================================================================== --- /FCKeditor.Java/trunk/src/site/apt/properties.apt (revision 3078) +++ /FCKeditor.Java/trunk/src/site/apt/properties.apt (revision 3079) Index: /FCKeditor.Java/trunk/src/site/apt/taglibrary.apt =================================================================== --- /FCKeditor.Java/trunk/src/site/apt/taglibrary.apt (revision 3078) +++ /FCKeditor.Java/trunk/src/site/apt/taglibrary.apt (revision 3079) Index: /FCKeditor.Java/trunk/src/site/apt/upgrade_notes.apt.vm =================================================================== --- /FCKeditor.Java/trunk/src/site/apt/upgrade_notes.apt.vm (revision 3078) +++ /FCKeditor.Java/trunk/src/site/apt/upgrade_notes.apt.vm (revision 3079) Index: /FCKeditor.Java/trunk/src/site/apt/useraction.apt =================================================================== --- /FCKeditor.Java/trunk/src/site/apt/useraction.apt (revision 3078) +++ /FCKeditor.Java/trunk/src/site/apt/useraction.apt (revision 3079) @@ -86,4 +86,4 @@ The system will respond messages to the user as they may be necessary. You can - localized every one of them. See {{{localization.html}Localization}} for more + localized every one of them. See {{{localization.html}Localization}} for more details. Index: /FCKeditor.Java/trunk/src/site/apt/userpathbuilder.apt =================================================================== --- /FCKeditor.Java/trunk/src/site/apt/userpathbuilder.apt (revision 3078) +++ /FCKeditor.Java/trunk/src/site/apt/userpathbuilder.apt (revision 3079) @@ -31,8 +31,8 @@ * Rationale - Hard-coded file locations can be cumbersome under certain circumstances. You may - need to change the storage location on-the-fly or serve location on a user/request + Hard-coded storage paths can be cumbersome under certain circumstances. You may + need to change the storage path on-the-fly or serve paths on a user/request basis. you are able to calculate the absolute storage path as well as the responded - URL the way you want according to the underlying {{{connector.html}Connector}}. + URL the way you want according to the underlying {{{connector.html}Connector}}. * The interface @@ -72,19 +72,19 @@ There is one common way to easily configure paths for an existing or a custom - implementation: + implementation: Create/edit the <<>> and set <<>> and <<>> properties according to the semantics of the chosen implementation (see {{{properties.html}Configuration}} for details). - + If you decide to create your own implementation, you are free to use our properties but if you do so, access them by calling <<>> and <<>>. - + If this still does not fit your needs, calculate the paths dynamically in the getter methods and return whatever makes sense to you. - + [Attention:] Every Connector relies on a specific <<>> implementation because it serves the paths the way the connector needs them. Make sure that your implemention is accompanied by the correct Connector. E.g. using the <<>> with the <<>> - may result in erroneous and undefined behavior. + may result in erroneous and undefined behavior.