Hey everybody,

Although this change is not trumpeted in any of our public release notes, support for TinyMCE and FCKeditor was improved to a usable state during this last release. Obviously there are some more polishing things to be done (keyboard shortcuts don't work uniformly), we've added all the basic functionality into both these editors (extensions, templates, links, images).

We will be switching to a new editor for 8.07 - by 8.05.1 (slated for the end of this month), we want to have a decision made.

Internally, we're leaning towards FCKeditor due to its code structure and its larger community. However, if there are enough voices who feel TinyMCE is a better choice, we'll certainly take a second look.

Do you have an opinion either way? Please let us know!

Well, I was using TinyMCE before. but I had to change it to Xinha because of templates. I liked TinyMCE, I had no problem with that, but FCKeditor won't bother me also. I wonder that what the main reason is for passing to FCKeditor. (Don't think this as I am opposing to FCKeditor. I want to learn if FCKed. have advantages or TinyMCE have disadvantages)

Both are very good editors and I've used each one in other web applications. The reasons for FCKeditor are sound and I have found it a fairly easy to customize. It does appear to have more active development than TinyMCE when you review the current features and updates.

I was able to add a third row of buttons. I added such things as the Paste from Word, Show Blocks, insert quote, search and replace, spellchecker, special characters, smileys, styles, insert rule and select all. All of these features appear to function fine. I understand the desire to maintain simplicity and keep the toolbar as uncluttered as possible, but these are helpful features.

It works well within Safari, except for the context menu. It is partially off the bottom of the browser screen and pretty much unuseable within Safari. The problem does not exist in Firefox on the Mac.

Exactly, the templates was one of the largest reasons we moved ours back to Xinha from TinyMCE. There were quite a few other anomalies we ran into as well with TinyMCE as far as formating went. As for FCKeditor I believe the bigest turn off was that it was not embeded in the page and caused some discomfort as it was another window to deal with.

This is my concern with FCKeditor. I noticed on the opengarden site that the FCKeditor was used, and it showing up at the top of the page, and being movable, was very different and not expected. If it's possible to force FCK to dock by default similar to Xinha then I look forward to the change.

FCKeditor does have the paste from MSWord feature. That's a big plus for end users who need to move data from already existing Word documents into a wiki page.

We've added Aspell integration for FCKedit so that users without text-box spell checking at least get a clue when they can't type straight...

What were the steps to add Aspell?

It seems that the common suggestion for FCKeditor is the fixed toolbox That was the reason for me to prefer TinyMCE instead of FCKeditor.

We've gotten lots of feedback on this. We'll continue to experiment and to figure out what works best. The benefit of the floating toolbar is that when you work on large pages and you don't have to scroll up to access the toolbar. That said, the jury is still out if we can make feel natural.