[wp-hackers] Question about the architecture of the admin widgets.php

[Andy Skelton]

On Mon, Jan 4, 2010 at 5:09 PM, scribu <scribu at gmail.com> wrote:
> If you sent a duplicate email on purpose, please don't do it again. Thanks.

This adds nothing of value.

On Mon, Jan 4, 2010 at 1:02 AM, John BouAntoun <jbouantoun at gmail.com> wrote:
> So the general solution would be to use a queuable event binding mechanism
> for all events in Wordpress, but failing that, the specific solution would
> be to allow me to wire in a pre-display event and a pre-save event, to allow
> me to do my mce control clean up and save triggering.

The way TinyMCE is integrated into WordPress, you already have a
general method for extending TinyMCE in plugins and themes. Use
WordPress action hooks to inject your javascript at the appropriate
times. Use filters to modify the editor's configuration.

> Can anyone suggest a better approach to solve my issue or let me know the
> likelyhood of either solution (general or specific) happening in the near
> future so that I know if it's worth updating my plugin with the dirty hack
> or not?

Study the way WordPress modifies the behavior of TinyMCE. Then do as core does.

Cheers,
Andy