TinyMCE is now a plugin

Today I’ve completely separated the TinyMCE RichText editor into a plugin that’s very easy to install uninstall or disable without any problems at all.

The total size of the manager after the separation is currently at 3.26MB unzipped

FCKEditor is now the default editor for the manager. Do you think we should move it’s files into the media/editor/ folder or let it remain as media/fckeditor/ ?

I’d say move it to media editor, or even better, also make it a plugin, albeit distributed by default with the main branch. That way if someone wants to remove it for whatever reason, they can.

Quote from: rthrash at Jun 20, 2005, 08:47 AM

I’d say move it to media editor, or even better, also make it a plugin, albeit distributed by default with the main branch. That way if someone wants to remove it for whatever reason, they can.

I am against moving this into the /editor directory, I don’t understand the point -- and I would have removed FCK and kept TinyMCE, as I still am not at all satisfied with the content generated by FCK. Also, I agree with Ryan, if one is a plugin, all should be...

Raymond is cooking up some really interesting stuff with FCK to make use of the mysterious (to me, anyway) templates button on the full layout. So there is reason to his madness.

Given that though, I prefer the heck out of Tiny MCE myself. I can’t currently navigation with cursor keys inside an FCK instance, for example.

Hi,

We need at least one editor to be built-in. This built-in editor would be used in chunks, templates, etc.

IMO and from tests that I’ve done FCK is much faster than tinyMCE and it’s widely supported. TinyMCE is easier to setup but it’s much slower when editing content.

Having a built-in editor means that we can customize that editor to work much more closely with the system and provide a way for users to run the system out of the box. FCK can be easily integrated with snippets, templates, chunks, etc to give the user a very powerful WySIWYG experience. The editor is lacking a few good things but from the looks of things on the FCK discussion board think will get better very soon.

I’m for FCK as the built-in editor. I’m also for merging HTMLAre’s image manager with FCK filemanager and adding some of TinyMCE image editor features such as Mouse over.

Now do we make all plugins or do we make TinyMCE or FCK the built-in?

I vote for all plugins. Some developers will in fact prefer to not have rich text editors at all, or very, very light ones like widgEditor (~100Kb total code with super-simple formatting only), Markdown or Textile.

Well that’s two down for RichText editors as plugins (Ryan and Jason). I’m for (FCK integrated)

What anyone else?

Make that three for plugins

Quote from: sottwell at Jun 21, 2005, 02:25 AM

Make that three for plugins? ?

Ok You guys win

I’ll make FCKEditor a plugin as well. I’ll remove the editor folder and add a stand-alone filebrowser folder. The file browser will be used for TVs and other things.

This means that the RichText TV will require that at least one of the editors must be installed.

Yeah... I think that Richtext should not even be an option UNLESS a RTE is installed. A little error checking I guess.