[wp-hackers] Greetings from FCKeditor

Otto otto at ottodestruct.com
Wed Mar 12 15:04:37 GMT 2008

On Wed, Mar 12, 2008 at 4:56 AM, Viper007Bond <viper at viper007bond.com> wrote:
> Bundling two RTE's is probably a bad idea. Just adds bloat, extra download,
>  etc. We should pick a horse and stick with it (and I'm not arguing for any
>  particular RTE here).
>  However, I think it'd be a good idea to make WordPress more module when it
>  comes to RTEs, not that it isn't already, but it could probably use some
>  more help.
>  Basically what I'm suggesting is make the core better support a non-bundled
>  plugin that allows the replacement of TinyMCE. So, someone either needs to
>  improve upon the existing plugin or write a new one. Then, wherever there's
>  problems integrating it into WordPress and replacing TinyMCE, a core patch
>  should be made up to fix the problem.
>  And personally, I'm interested in the fruits of this because it seems like
>  I'm constantly going in and fixing up posts made by clients in TinyMCE that
>  resulted in horrible HTML, either due to user error (pasting from MSWord) or
>  TinyMCE error.

Yes, yes, a thousand times yes!

TinyMCE should not be in the core. It's as simple as that. In my
opinion, it should be a plugin. Perhaps a bundled one, perhaps not,
but the only thing that should be in the core is the necessary hooks
to use it, or any other, RTE.

The best way to go down this road would be to do everything possible
to move TinyMCE into a plugin status and to standardize the necessary
hooks and interface to allow things like adding quick-task buttons and
such. The editor can then hook in and intercept these calls, to add
the buttons and so forth.

Keep the core lean. Remove the bloat.

More information about the wp-hackers mailing list