Richtext CKEditor 4
Package Specification Summary for Package: richtext-ckeditor4
Summary: | Richtext editor plugin for integrating CKeditor 4 with acs-templating |
Description: | |
Maturity: | Mature |
This package depends on: | acs-templating acs-tcl attachments |
Packages that depend on richtext-ckeditor4: | xowiki |
Package parameters: |
|
Bug Tracker Summary for Package: richtext-ckeditor4
There is no package with the name "richtext-ckeditor4" known to bug-tracker.
Code Metrics Summary for Package: richtext-ckeditor4
# Tcl Procs | 9 |
# Tcl Lines | 667 |
# Tcl Blank Lines | 91 |
# Tcl Comment Lines | 135 |
# Automated Tests | 0 |
# Stored Procedures | PG: 0 ORA: 0 |
# SQL Lines | PG: 0 (blank 1 comments 0) ORA: 0 (blank 1 comments 0) |
# ADP pages | 1 |
# ADP lines | 11 |
# Include pages (richtext-ckeditor4/lib/) | 1 |
# Documentation pages | 0 |
# Documentation lines | 0 |
Browse Source | API-browser |
Github Repository: | https://github.com/openacs/richtext-ckeditor4/tree/oacs-5-10 |
In general, the CKEditor can be used via CDN (zero configuration, default) or via local files. One can use /acs-admin/ (section "Site-wide Service Administration" to download a version to your local site to reduce latency or to use local modifications. By default, the "standard" preset is downloaded. By altering the variable "ck_package" in packages/richtext-ckeditor4/tcl/richtext-procs, one can download other presets as well (see https://ckeditor.com/presets-all).
The CKEditor widget can be used at least in two scenarios: (a) as a richtext-widget or (b) within xowiki as a class of a form-field.
- (a) Here is an example for the use of the richtext widget configured for ckeditor4, showing some options:
text:richtext(richtext),nospell,optional {label "CKEditor"} {html {rows 15 cols 50}} {options { editor ckeditor4 plugins wsc extraAllowedContent "u;span{color}"} }
This minimal example should work with the "standard" distribution of CKEditor and adds the "wsc" (Web Spell Checker) plugin, and allows the tag <u>u and <span style="color:...">...</span> to be used in the content. Otherwise, these flags are removed by the context filter of the editor (for details, see CKEditor documentation). Additional "options" are "skin" and "customConfig", where the latter refers to a JavaScript file which can be used for detailed configuration (for more details, see https://docs.ckeditor.com/#!/guide/dev_configuration).
Note, that the usual constraints for richtext widgets holds like for all other richtext implementations (e.g. the editor will only be activated, if UseHtmlAreaForRichtextP is set to true). - (b) when used as a form-field within xowiki forms, there are detailed config options available: mode, displayMode, skin, toolbar, CSSclass, uiColor, allowedContent, customConfig, extraPlugins, extraAllowedContent, templatesFiles, templates, contentsCss, imageSelectorDialog, and additionalConfigOptions. A short introduction to form-fields is in http://alice.wu-wien.ac.at:8000/xowiki-doc/#forms. One should set the PreferredRichtextEditor (xowiki global parameter) to ckeditor4.