Rich Text Editor updates

TinyMCE has been used for Wordpress and this bundling includes an image browser but I'm not sure where that component comes from but it must be GPL:
http://mudbomb.com/archives/2005/02/02/wysiwyg-plugin-for-wordpress/

Is this in terms of manager-side editing? Or in regards to Richtext TV controls? Or both?

I think we could achieve this by adding editor options to each document instance and each TV richtext instance. Any other thoughts on implementation?

This would be customizing the buttons per richtext instance. Basically when you choose to add a richtext control you would then choose which buttons would be available in that instance. These would then get passed to the javascript that launches the instance. So I guess we need either a multi-select list or checkboxes somewhere to pick the buttons. Doable?

HTMLArea's image manager is still better than the commercial offering, IMO. The image manager w/ the built-in editor is one of the slickest image selectors that I've ever seen. Personally, I'd love to see it get ported over to both FCK and MCE and perhaps the image popup editor even used in our file manager when an image filetype is detected.

Travis... did you just volunteer?

Sure, as long as Jason doesn't want it/isn't already working on it.

Sure, as long as Jason doesn't want it/isn't already working on it.

I'm focusing on the editors themselves and will be working on identifying common options and encapsulating as much of the code as possible so it's that much easier to integrate additional editors moving forward. So have at the image manager integration.

I should have FCKEditor checked in later today.

has anyone tested TinyMCE with <form> fields? It (the online example) seems like it's not allowing me to insert <form> tags.

Few quick questions for Jason (and comments for everyone):

1) Can you confirm the <form> bug?
(I don't think this is a huge deal for us as I view the rich-text editors as a client-focused support system, and not that likely that clients will be creating forms. Any other thoughts from anyone here? Maybe a dedicated form editor plugin should be created down the road.)

2) Did you manage to get TinyMCE to save any TV changes?

3) How's FCK coming along?

1) Can you confirm the <form> bug?
(I don't think this is a huge deal for us as I view the rich-text editors as a client-focused support system, and not that likely that clients will be creating forms. Any other thoughts from anyone here? Maybe a dedicated form editor plugin should be created down the road.)

Seconded ... on both accounts.

1) Can you confirm the <form> bug?
(I don't think this is a huge deal for us as I view the rich-text editors as a client-focused support system, and not that likely that clients will be creating forms. Any other thoughts from anyone here? Maybe a dedicated form editor plugin should be created down the road.)

Seconded ... on both accounts.

I'll take a look at the form issue, but I'm almost certain that is a configuration option.

Also, I'm still stuck on getting TinyMCE to trigger the onchange event of the TV textareas; if anyone wants to take a look at the keypress event handler and see if they can find the appropriate line( s ) of code to make this happen, I'd be eternally grateful. It apparently isn't quite as easy to trigger as in HTMLArea.