Thank god they changed the name. This is truly a great editor and I've seen it used many times, but I always felt uneasy saying it out loud or even typing it to someone who had never heard of it. It's just awkward. The new name has no (blatant) bad connotations.
Looks hopefully like a great rewrite. FCK = Definitely a major player in the wysiwyg scene for long years. I have fingers x-ed on this being the step that resolves the search. Finding a wysiwig that is not bloated and overly complex, bug-free and has the essentials, has occupied me for years. The one thing CK clearly swung and missed in their demo though is the seeming thrill they express about being "colorful". The defaults for modal dialog buttons: bright orange, yellow and green!! CKEditor, you could not have done anything more to suggest you were somehow ignoring or out of touch with the evolution of web UI than this. Now I know that this is all css customizable. Great. I look forward to altering those. But really, if you can show us a web site with good design that uses flaring colors in a text editor UI, I will be stunned. Anyway, sorry for the rant... thrilled that you have moved this forward and can't wait to try. I hope though that you quickly iterate the defaults and the demo on the site to be in line with the notion that UI widgets should not scream for attention, but emphasize the clean and functional.
Haha, definitely agree with this. I took some time to override much of the Kama skin's CSS (including the dialogs) for Wygwam. Ended up with something much more clean: http://brandon-kelly.com/fieldframe/showcase
As far as I know codepages is all about the browser (usually handles this well) and server-side solution (your milage may vary). When it comes to problems with (F)CKEditor, my problem in this particular case is usually the markup.
The markup from Word may be "slightly" mangled and all, but you need massive amounts of server-side code to clean it up and it just feels so unnecessary when it actually renders fine in the editor client-side.
Small but very annoying bug. In the end I switched to the YUI rich-text editor and it seems to be working better.
I'm very pleased with the accessibility improvements. Not just because it's the right thing to do, but it means that building interactive sites where accessibility is a project requirement will be a lot easier.
It would be useful to have a simple editor like TinyMCE but with image browsing/uploading plugin that doesn't just provide you with a file system interface. Instead it would be more useful, IMO, to have a database backend powered images table that you can search through via autocomplete/tags that you can give to each image when uploading it. It would also be useful to have a module in that plugin to search flickr and other services images for CC friendly images that you can transfer to your site easily - retaining all the authors info (to be displayed next to an image).
Actually I have this in my TODO list somewhere down the road.
I thought this editor looked familiar, my University (IU & IUPUI) has been using the same 'FCKEditor' for 5+ years now; nevertheless, it serves as our WYSIWYG editor for sending messages back and forth via our University's version of Sakai's (http://sakaiproject.org/portal) messaging system, I couldn't tell you how many times my session has timed out costing me a couple paragraphs of my time o_O
while I agree that F?CKedit is a lot of baggage and not very friendly to program against, the timing out sessions are a problem of the guys that implemented your messaging system and not a problem of CKedit.
There is a “notes on the new name” section on the linked article:
“For years we have been fighting with a relatively important issue with FCKeditor. While its quality has been strongly accepted, its name brought us troubles, mainly inside English speaking countries. The fact is that the initials of Frederico Caldeira Knabben have an unfortunate match with the most used English bad word.”
fckeditor code was such a pain to explore, hopefully this complete rewrite solves those problems. we use it over tinymce at work because of the free upload addons.
I used to curse FCKEditor because it was so slow and unweildy for ajax apps. Creating and destroying and then customizing was a pain. Not many WYSIWYG editors really do these nicely. They all seem to be made to work in a static load once html page. Now CKEditor says you can do all that so I'm very excited. If it is fast, can create and destroy with ease and plays well with jquery then it's my new favorite editor!
One of our users had dropped this into their web structure years ago, never updated it, and had their account nicely owned due to a years-old vulnerability.