| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 1735 | Composr | core_rich_media | public | 2014-12-06 00:07 | 2016-01-24 16:50 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 1735: Better Comcode WYSIWYG editing | ||||
| Description | It's messy having Comcode tags written in text in the WYSIWYG editor, and people love to use lots of Comcode, more and more. See the attached screenshot. The top half is how it looks now. The bottom half is how it would ideally look. If you pressed the Comcode button while inside a Comcode element it would take you to a screen IN FRONT OF the current start of the Comcode tag assistant. This screen would ask you whether you wanted to: - edit that element (which one, if multiple are nested) - delete that element (which one, if multiple are nested) - insert a new one. On an implementation level we'd do this by supporting tags like "x-cms-media_set" within the editor. It would not be all Comcode tags, but a large number of those that wrap content (quote, code, codebox, surround, all come to mind). We'd process these back out when saving from the WYSIWYG editor, and smartly insert them when generating for the WYSIWYG editor. One important check is to ensure we only place these if the Comcode tags align with the tree structure of the HTML. If we had something like the following, we could not do it in that particular case: <div>[surround]</div>[/surround] It would be super-awesome if we could do this for Tempcode directives too. Lots of ugliness comes from these. Just in a basic way. | ||||
| Tags | Pseudo-addon: CKEditor | ||||
| Time estimation (hours) | 16 | ||||
| Sponsorship open | |||||
- Anonymous
