[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:25 nacin]:
 > The first editor could retain the existing ID. Subsequent ones can be
 new IDs.

 The only changed IDs are on the switching buttons, the rest are new. Of
 course the quicktags toolbar ID is changed too but that's in #16695.

 > The point is simple: Everyone uses it. It should stay and be a wrapper.

 You mean don't deprecate the_editor()? That would make two wrappers for
 the same thing :)
 The arguments have changed (not in a breaking way), thinking by
 deprecating it we will draw attention to that.

 > There's no need for a lot of those functions to become methods... All of
 these functions should still exist on their own.

 Added them in the class as it's only loaded (lazily) when needed and these
 functions are only used there. Can probably move wp_link_query() directly
 to admin-ajax.php as it can only be usefull from there. Don't see a point
 for wp_fullscreen_html() and wp_link_dialog() to be separate functions.
 Furthermore they will be loaded on each run of WP (on the front end) which
 is undesirable.

 Actually we have quite a bit of code in wp-includes that is loaded on each
 run of WP but used once in a while (1 in 10,000?). Even some functions
 that cannot be run unless wp-admin is loaded. All this eats some resources
 which multiplied by many millions amount to a lot :)

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