But the good thing for all users is that both sides are constantly developing new features;)

Editor Online

tinyMCE.init({
mode : “textareas”
});

tinyMCE.init({
mode : “textarea”
});

This is some content that will be editable with TinyMCE.

What I was thinking might be a quick and easy implementation would be to use either of these plug ins as follows:
– allow them put together a draft through the plugin with whatever formatting is required, perhaps pasting from existing word documents)
– when they save it, save the converted HTML to disk, and then convert the HTML to a word doc using a HTML to RTF converter
– when they want to make subsequent edits to the word document “open” the document in the editor

The last step is the one that may cause me issues, but I am sure once I get into the code that I will be able to resolve it.

Am I going a really bas way about this? I am confident I can implement it from the ASP side of things but I want to be sure that I wont hit a brick wall. Time is really against me so maybe one or other would be more appropriate/easier to implement. I would welcome any feedback/criticism/advice etc.
Thanks,
David

On TinyMCE, here was the output code:

On FCKEditor

My point is FCKEditor does not nest HR elements in paragraphs, making it more valid and neat code.

I wanted to test these because my site is strictly valid XHTML and I am developing a CMS, so I needed a good WYSIWYG editor (though I am well advanced in HTML and definitely can code for myself) so I saw the two, ran a simple test, and searched FCKEditor vs TinyMCE.

I think I’ll go to Tiny because it make very easy to create layers. and for users nodeveloppers it’s useful.

there is some free file managers and I like the idea of the compressor.
I didn’t see multilangues on it but I hope it has

the only bad is it seems not easy to change tables and layers when you have created (there is no “properties” on right click)

step to simulate

Create Table – > select any cell -> cell properties -> Set Bordercolor .

Now You have invalid attribute Bordercolor .

Tinymce handle this very easy.

Thanks

“FCKEditor allows you to insert images from the server that you uploaded but without CKFinder you can delete images.”

Is this right? I thought that, without CKFinder, you *can’t* delete images.

Or have I got that wrong?

Joe Stack says, November 13th, 2008

There’s just one problem boys and girls… you keep saying that it is easy to install both of these. Yet when I go out to the web I see hordes of people ripping their hair out just trying to get either FCKeditor or TinyMCE to work at all.

The untold story is that for all but a handful, FCKeditor and TinyMCE are simply not an option because NOBODY has troubled themselves to write a decent set of installation instructions for ordinary users.”

I think it largely depends on how you are aiming to use either of these. For Drupal it was a breeze and minus the download time it took me more than a few minutes to set it up and have it working. As far as the lack of documentation? I found some for Drupal right here: http://drupal.org/handbook/modules/tinymce

I imagine if I wanted to use it for another CMS or web application I could find more documentation, and if not I’d write it and contribute to that particular CMS. Instead of complaining about the lack of documentation or how hard something is to get working, I personally like to challenge myself with getting it to work and then write it up, but hey that’s me. That in my mind is in the spirit of open-source; coders write code, writers, users and CMS builders should write instructions, once they figure it out of course.

The untold story is that for all but a handful, FCKeditor and TinyMCE are simply not an option because NOBODY has troubled themselves to write a decent set of installation instructions for ordinary users.

It seems like a badge of honor for both communities to make basic installation of these great little web page editors as inaccessable as possible.

I understand that coders like to write code and dislike writing instructions, especially installation instructions, but they do themselves and their code a great disservice when they confuse availability for accessibility. If you can’t install the things, you never use them.

“Instructions” like, “Just extract the contents of the downloaded file to your website root file…” are meaningless. Have you ever tried to get a zip/unzip application to put the extracted file directly from your desktop to a file folder on the web server? It can’t be done. Yet that’s what people think you mean when you say things like that.

I hate to be a killjoy, but both communities are fooling themselves and losing a great opportunity for huge increases in the use of these two wonderful little web page editors. I’d like to see a fraction of the time and energy now spent on comparing the two editors put to use to write a set of really crystal clear instructions for ordinary people.