Ticket #585 (closed Enhancement: wontfix)
Use CKEditor Inline mode
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.2 |
Component: | DeepaMehta Standard Distribution | Version: | 4.1.3 |
Keywords: | Cc: | dgf, Malte, JuergeN, ziegi | |
Complexity: | 3 | Area: | GUI / Usability |
Module: | deepamehta-webclient |
Description
We should update CKEditor and check out its new Inline mode.
Currently we use CKEditor 3.6.2.
Current version is 4.3.1 (released Dec 10, 2013).
CKEditor's Inline mode means editing the page directly (and not in a separate iframe). So there is no difference between looking at a page and editing the page (they call it "real WYSIWYG"). But the main advantage of Inline mode is the floating toolbar. It appears only when an editable element has focus, and is not visible otherwise. So it doesn't clutter the screen when not needed. And it floats above the page, it never scrolls out-of-view.
Change History
comment:2 Changed 11 years ago by Jörg Richter
comment:3 Changed 11 years ago by Jörg Richter
comment:4 Changed 11 years ago by jri
CKEditor's inline editing should be turned off again. It causes new usability problems, and makes sense only when DM actually support inline editing, that is: no Edit button! Instead initiate per-field editing just by clicking inside the field (see #416).
For the moment I wish we could combine CKEditor's "classic" iframe based editing and combine it with the inline mode's floating toolbar. Does anybody if this is supported by CKEditor?
comment:5 Changed 11 years ago by Jörg Richter
CKEditor: return to "framed" editing (#585).
Update CKEditor 4.3.1 -> 4.3.2
Note: the Webclient's internal "ckeditor_plugin" is dropped. It cared about destroying editor instances. It doesn't work anymore with new CKEditor versions (exception occurs). Anyway, explicit destroying editor instances is apparently not required anymore.
See #585.