[wp-trac] [WordPress Trac] #12423: Include Ace (or similar) as default code editor

[WordPress Trac]

#12423: Include Ace (or similar) as default code editor
-----------------------------+----------------------------
 Reporter:  scribu           |       Owner:  afercia
     Type:  feature request  |      Status:  assigned
 Priority:  normal           |   Milestone:  4.8
Component:  Editor           |     Version:  3.0
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  accessibility
-----------------------------+----------------------------

Comment (by westonruter):

 @georgestephanis great! I opened a PR to collaborate on:
 https://github.com/xwp/wordpress-develop/pull/217

 The remaining functional pieces would seem to be:

 * Incorporate with plugin file editor.
 * Utilize in Custom CSS customizer control.
 * Employ in HTML tab for the WP editor.

 '''However''', I realized that I hadn't actually done a search to see what
 plugins already exist that integrate CodeMirror, or another editor
 library, into WordPress. Doing a quick survey of plugins, there are
 ''several'':

 * [https://wordpress.org/plugins/html-editor-syntax-highlighter/ HTML
 Editor Syntax Highlighter], for content editor, also uses CodeMirror.
 * [https://wordpress.org/plugins/advanced-code-editor/ Advanced Code
 Editor], for theme and plugin file editing, also uses CodeMirror.
 * [https://wordpress.org/plugins/syntax-highlighter-for-postpage-html-
 editor/ Syntax Highlighter for Post/Page HTML Editor], also uses
 CodeMirror.
 * [https://wordpress.org/plugins/syntax-highlighter-for-wp-editor/ Syntax
 Highlighter for WP Editor], CodeMirror yet again, for the theme and plugin
 file editors.
 * Jetpack, as you know, uses CodeMirror for Custom CSS.

 Good news is that CodeMirror came up over and over again in my quick
 search. But to move forward with incorporating CodeMirror and implementing
 it—for the theme and plugin file editor, content HTML editor, and the
 Custom CSS customizer control—I think we are first beholden to list out
 all of the plugins that already implement these fully and to loop in their
 authors to the conversation so that we don't reinvent the wheel, so we can
 incorporate the best of each of their plugins, and also so that we can be
 good neighbors since we'd effectively be deprecating their plugins.

 All of this to say, it seems the next steps for this would be less
 technical and more communicative.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/12423#comment:48>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform