It'd be an awesome addition to provide the CodeMagic plugin as part of the panopoly_wysiwyg feature. (see https://github.com/tinymce-plugins/codemagic and/or http://drupal.org/project/wysiwyg_codemagic)

Anytime I use this feature (a good bit) I always add it as a more manageable source code editor for the WYSIWYG profile.

CommentFileSizeAuthor
#2 ckeditor.png50.8 KBchriz001

Comments

populist’s picture

populist commented
Project: Panopoly WYSIWYG » Panopoly
Status: Active » Postponed

Very cool feature request! Adding it to the main queue and postponing it for future consideration.

chriz001’s picture

chriz001 commented
StatusFileSize
new ckeditor.png50.8 KB

This module wont work with ckeditor if that becomes the default as suggested here http://drupal.org/node/1965864.

It also uses an older version of jsbeautifier which doesn't seem to format inline elements correctly.

An alternative might be to use ckeditor with the CodeMirror plugin for highlighting (have to use a custom build) and use the 'Apply source formatting' setting in the wysiwyg module or something like that.

this seems to be working pretty well for me now.

mrP’s picture

mrP commented
Title: Add CodeMagic source code editor plugin » Add source code editor plugin

I haven't worked with CodeMirror but the idea seems the same. As chriz001 mentioned, any decision is dependent on the outcome of #1965864: Support CKEditor in Panopoly.

Here is my two cents:
1. TinyMCE 3.x => CodeMagic
2. TinyMCE 4.x (requires WYSIWYG #1968318: Support for TinyMCE 4.x) => ? / CodeMagic
3. CKEditor 4.x => CodeMirror

FWIW, I do think that 3 is the best long-term route to take.

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented
Component: User interface » WYSIWYG
Issue summary: View changes
Status: Postponed » Closed (won't fix)

While this seems like a really cool feature, I'm going to close this as "won't fix". We already have Markitup to help with editing HTML code, and we've lived without it this long... So long as we're not doing anything that prevents users from adding this plugin to their own sites, I think we should leave this be (at least during the Panopoly 1.x cycle, where we're going into maintenance mode).

Feel free to comment or re-open if you disagree!