Even if this release is not yet targeted to production web sites, it's stable enough for it.
It may be stable but it's by no means ready, this is really unfortunate. The new icons are really ugly too I don't see why you couldn't have used the old ones these new ones aren't polished. Also the source code is really messy and was in gigantic condensed lines thanks for making it easy to read for us to help.
Also using a function to find the location of where CKeditor is installed is not recommended. I have made a PHP script that essentially gathers required JS files (for ckeditor and my own personal applications) and puts them in a single <script> tag, that way you don't have a dozen <script>'s in your code and making it very messy. So a config option for the install path would be nice, I modified the baseurl variable to do what i needed it to do but again, condensed code makes it difficult to find.
Also when you go to resize the ckeditor it seems to have a problem and all of a sudden has a minimum width of 750ish pixels. after mashing my way through the javascript and clearing up my toolbars of un-needed or non-functioning icons my editor instance is well below this size and there is no need for this minimum size
the options are not listed or well explained at all anywhere that i could find easily and there's no file upload support which is a huge disappointment
so even though FCKeditor is old and klunky it is a much better choice right now
edit...
sorry i didn't mean to just say the bad but that's where i ended up
it was very easy to install, and loads much MUCH faster. the default skin is neat but a little large but i think some tweaking would make it look way better than the default now. using the editor was simple and the basic javascript ajax controls seem to work well
Re: first impressions from a developer's point of view
You can use config.resize_minWidth = 500; It will work with IE and FF, but in Safari it may still be too wide unless you rearrange the toolbar buttons. Currently Safari cannot wrap long CKE toolbars (BUG).
Re: first impressions from a developer's point of view
It's always good to have feedback as it points to the things we need to work on. Your message actually points to a single direction: the documentation.
The fact is that all you have talked about is already manageable with CKEditor. It's just a matter of knowing how to do things:
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: first impressions from a developer's point of view
Re: first impressions from a developer's point of view
I agree that the new icons are ugly but why not simply re-skin using the older style? They did make that an option for us to reskin on our own, at least that is what I did. When I create my instance I tell it as part of my config to use the "v2" skin that you can see located in the skins folder fo teh ckeditor.