FCKeditor --> CKeditor

[pgmarshall]

I have just been reading this site which has released a much smaller and quicker WYSIWYG editor ... the next version of FCKeditor ... skinable, resizeable, faster ... looks great!

Any thoughts - should we upgrade oscmax to use this?

Regards,

[JohnW]

Did you know that there is a FCKeditor config file you can make changes with? It's FCKeditor/fckconfig.js if you want to play with it. Handy if you want it to use a certain doctype and you can customize quite a bit with it.

PS. I didn't realize they're the same people as FCKeditor. Have you tried it?

[pgmarshall]

JohnW,

No I haven't tried it yet ... bit short of time at the moment. I will have a go at switching soon though as the new code looks to be quicker with a neater interface and a few extra wizzy bits (eg. resize the text window).

Regards,

[pgmarshall]

Michael,

I have been having a look at CK editor v3.0 - which is the new version of FCK editor and was wondering if it might sneek its way into the v2.1 release?

The plugin seems to be a lot quicker than the old FCK editor, has a nicer interface and can be dynamcially resized.

Edit: The install is a bit more involved than I had hoped ... anyway food for thought on future releases of osCmax - this is not critical and I would prefer to see One Page Checkout!

Regards,

[ridexbuilder]

...would prefer to see One Page Checkout!

I'd prefer to see existing functionality/modules working.

[michael_s]

I'd prefer somebody else do all this work so I can take a vacation

[ridexbuilder]

Touche.



[I take a mini one and the flippin' car breaks down and it's not even a Jeep ]

[pgmarshall]

Michael,

If there is anything I can do to help ... let me know!
But quite right ... more patience required!
Thanks for all the hard work.

Regards,

[michael_s]

If you code something that you want included or think is a good addition, feel free to package it up (or merge into a source copy of SVN or 2.0.3) and I will add it to the package (a al EJ's Mopics/Slimbox work)

Make sure whatever you code does not break any other features if you are putting it in 2.0.3. There is a little more leeway for 2.1 since it is not stable yet.