[wp-trac] [WordPress Trac] #17144: Editor API enhancement

[WordPress Trac]

#17144: Editor API enhancement
-------------------------+------------------
 Reporter:  azaozz       |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  3.3
Component:  Editor       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+------------------

Comment (by azaozz):

 Replying to [comment:22 dd32]:

 Patch coming up.

 Replying to [comment:23 nacin]:
 > The HTML/CSS doesn't look backwards compatible in terms of class names
 or IDs. I don't think it would be difficult to retain this.

 The old HTML didn't allow multiple editors on the same page, retaining the
 IDs would mean we still ban that.

 > the_editor() should not be deprecated. It should simply wrap WP_Editor.

 Most of the functionality of the old `the_editor()` is in
 `$wp_editor->editor()`. We can have it as a separate function (again) but
 don't see the point since `wp_tiny_mce()` is now gone.

 > the_editor() appears twice in the code. trunk is probably fatal
 erroring.

 Not seeing that (and trunk doesn't fatal error).

 > Not sure I get the internal linking refactoring, or why wp_link_query()
 isn't still a function that, if appropriate, calls WP_Editor/$wp_editor.

 There's no refactoring. Only moved the JS and CSS out of the TinyMCE
 directory as they are used for the HTML editor too.

 > I really wish we saw a patch and explanations before these major patches
 land. This has bit us before and I sense a lot of backwards
 incompatibility issues will arise.

 Was planning to put a patch up first, but it became too big for that :)

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