[wp-hackers] <!--nextpage--> and other tinymce stuff

Jess Planck jess at funroe.net
Tue Nov 4 20:16:54 GMT 2008

As I was saying before my phone crapped out and just decided to send  
my unfinished message:

I was hoping that these functions would be split into separate tinymce  
plugins / javascript functions. I would not consider this the easiest  
task, so I would not expect it for 2.7. There are a ton of functions  
in the wordpress tinymce plugin; page more, next page, advanced  
toolbar, wordpress help, and not to mention core controls for the  
editor that do hot keys and build in the media buttons. It might be  
time to split out some of those functions.

If More and Next Page were in a wp-paging tinymce plugin and advanced  
toolbar were in a kitchensink tinymce plugin. They could be easily  
removed or modified by plugin authors. Very easy to override. I don't  
know if I get this right, but wpeditimage buttons live in the  
wordpress plugin while the wpeditimage has it's own plugin?

Yea, I wouldn't expect that sort of cleanup to happen for 2.7 no way...

On Nov 4, 2008, at 11:32 AM, Idled Soul wrote:

> Jess Planck wrote:
>> I thought about this the other day because of issues with the  
>> advanced  toolbar button. Right now all the WordPress  
>> customizations for tinymce  reside in one tinymce plugin
> I just feel, that it should have been already added in as core  
> before. Not needing a plugin for it at all. It should have been  
> taken care of along with that link_before / link_after stuff for  
> wp_list_pages / and so forth, while it was added into core. It  
> shouldn't be considered a "feature" at all. Sure one could refer to  
> it as a feature, but really it's part of WordPress now, it's there.  
> When we tell the doctor our foot is aching, we don't say... "Doctor,  
> I'm having bad aches and pains in my foot feature below" ...

More information about the wp-hackers mailing list