Rich Text Editor updates

In my SVN branch, i have committed the following changes:

* Removed HTMLArea as a rich-text editor option in the manager and in Richtext TV displays
* Replaced old TinyMCE with latest version (1.44)
* Refactored manager to use TinyMCE for all content and TV's
* Refactored richtext TV control to use TinyMCE instead of HTMLArea

Known issues with the commit:

* TV content is not saving after being editing with TinyMCE

Things left to do with Rich Text Editing:

* Add FCKEditor option to manager and Richtext TV controls
* Add various options to manager for TinyMCE and/or FCKEditor
* Replace HTMLArea Image Manager being used for various TV controls and user photos
* Remove HTMLArea completely

Let me know if there are other considerations I am missing.

* Replace HTMLArea Image Manager being used for various TV controls and user photos

What will this one be replaced with? I'm yet to see a better Image Manager than the one that works wil HTMLArea. It is both a image file manager and an image editor!

I'm more for merging this Image editor with TinyMCE's image manager. It can be invoked by adding a browse button inside the TinyMCE image editor.

Good job so far - keep it up

* Replace HTMLArea Image Manager being used for various TV controls and user photos

What will this one be replaced with? I'm yet to see a better Image Manager than the one that works wil HTMLArea. It is both a image file manager and an image editor!

I'm more for merging this Image editor with TinyMCE's image manager. It can be invoked by adding a browse button inside the TinyMCE image editor.

Good job so far - keep it up

Good question; I haven't fully researched the TinyMCE plugins, but that sounds like a good plan to me. Anyone have other ideas or thoughts before we add that task?

We perhaps should get the wider community to develop plugins and enhance TinyMCE to work like this editor

http://www.telerik.com/Default.aspx?PageId=1586

It's the most powerful HMTL editor that's available today.

Have a look at the table maker. If we can create somthing like this then that would be a plus for the CMS

That's a cool, nice looking editor.

Honestly, I think the biggest thing people will use is simple formatting options (bold, italics, perhaps color, and lists ... maybe indenting), and inserting images and links to PDF or .zip files.

With that in mind, we should create some "dumbed-down" set of buttons that does just those functions.

TinyMCE has already stated that they will be focusing on Safari and CSS support in their next release, which is undergoing development right now. It already renders the page and buttons, so it's probably not that far off from working.

I have not played with it yet, but they also have some image manager and file manager plugins too. I'd rather focus on getting one VERY right right now, and then work on others as plugins later.

With that in mind, we should create some "dumbed-down" set of buttons that does just those functions.

This is what I was getting at in another post where I talked about being able to set options on the editors so that one instance of it might only allow bold and font choices but another will feature everything. This is an excellent way to constrain editors to certain options depending on the content they are working with.

Did you ever make headway in getting the plugins (file and image manager) from TinyMCE workign? Or when you mentioned plugins, did you mean teh Rich Text Display Control and the TV editing functions?

Did you ever make headway in getting the plugins (file and image manager) from TinyMCE workign? Or when you mentioned plugins, did you mean teh Rich Text Display Control and the TV editing functions?

Actually, I think there may be some confusion here.

First, their is an AdvImage plugin activated in the current version I have configured. It's decent, though no in-place image editing capabilities.

Second, Moxiecode offers two separate products, MCFileManager and MCImageManager, but these are COMMERCIALLY LICENSED and cost money, though they claim they can be integrated with other editors.

Not sure how to proceed yet. Any other ideas?

With that in mind, we should create some "dumbed-down" set of buttons that does just those functions.

This is what I was getting at in another post where I talked about being able to set options on the editors so that one instance of it might only allow bold and font choices but another will feature everything. This is an excellent way to constrain editors to certain options depending on the content they are working with.

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?

I think there problably should be a site wide option on what to use for everything, which can be overridden on an increasingly granular level if desired.

E.g., ship with one config to address Content/TV editing view, and another to control the richtext controls that can appear in client-side apps. We can add the granularity later.