[wp-trac] [WordPress Trac] #24067: TinyMCE 4.0

[WordPress Trac]

#24067: TinyMCE 4.0
-------------------------+-----------------------------
 Reporter:  josh401      |       Owner:  azaozz
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  Future Release
Component:  TinyMCE      |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+-----------------------------

Comment (by azaozz):

 Upgrading our implementation to TinyMCE 4.0 is a huge task. Additionally
 all WordPress plugins that add TinyMCE plugins or custom code will need to
 be updated (there are lots of them). There is a
 [https://github.com/tinymce/tinymce/tree/master/js/tinymce/plugins/compat3x
 "compat3x" TinyMCE plugin] which only includes several files that have
 been removed from 4.0 for now.

 I'm on the fence on whether we should work on this upgrade in a "core
 plugin", the same way new features are being developed. All it would need
 is an action in `wp_editor()` so a different `_WP_Editors` class can be
 used and couple of feature checks in JS: `if ( tinymce.onAddEditor )...`,
 etc.

 Proposing the following (loose) schedule:

 1. Upgrade the basic WordPress implementation of TinyMCE to 4.0.
  - Translations work differently in 4.0, refactor tinymce/langs/wp-
 langs.php.
  - Refactor `WP_Editors` as needed.
  - Upgrade/refactor the 'wordpress' plugin. It contains most of our
 specific changes.
  - Upgrade the rest of our custom plugins.

 2. Decide on default UI settings. Are we showing the menubar plus one row
 toolbar or are we going to stick to two rows toolbar with hidden second
 row? Default drop-downs to show in the menubar?

 3. Add as much back-compat fixes as possible. As a minimum running any
 external JS or loading 3.x plugins should never break TinyMCE or throw
 errors.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/24067#comment:18>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software