CKEditor for MODx is released. Bye TinyMCE!

Although with it working, the command S save shortcut doesn't work in Safari. Still works for other fields, just not the rich text field.

Susan, thank you again
Firefox has no javascript property location.origin. But I don't even need it. I have uploaded fixed version 1.0.2-beta3

Quote from: sottwell at Dec 07, 2012, 06:08 AM

Although with it working, the command S save shortcut doesn't work in Safari. Still works for other fields, just not the rich text field.

This is strange. I'll check it.

UPD: Indeed. The conflict of my custom save command with built in one. I'll fix it later. And thank you again [ed. note: danya_postfactum last edited this post 11 years, 5 months ago.]

Looks and works great.

Are the following two TinyMCE features not available

Search for ID - when you're linking text or an image etc
Image browse - when you're adding an image to the page

P

You can use drag'n'drop from trees for linking your resources or files. The second feature will be added in the nearest future.

Using drag/drop to make links doesn't enable the Save button. Simply pressing a non-character key on the keyboard, like one of the arrow keys, is a workaround, as is adding then removing a space. I don't know if this is also the case in TinyMCE, as I have not used it much in Revo.

And just to prove that no good deed goes unpunished, do you plan to configure it to ignore MODx tags?

Also a question; could you tell me how to load custom plugins? http://docs.ckeditor.com/#!/guide/plugin_sdk_intro

Seems easy enough to do, but can't seem to find where exactly to add the config.extraPlugins = 'timestamp'; line. I tried the config.js file, but that didn't do anything.
It would be interesting to allow the addition of snippet and chunk and placeholder tags, while ignoring whatever gets put inside of them, as well as not forcing block tags around them. Basically treat them like HTML comment tags, except display them (perhaps highlighted in some color) in the rte field.

So, how does CKEditor compare to TinyMCE, in practice, used with MODx?
TinyMCE is well established together with MODx and the plugin is, afaik, maintained by the MODx team. I see that as an advantage to TinyMCE.

HTML5 support
Drag'n'Drop from trees support
Ctrl+S support [broken for now]
Switching modes (source/wysiwyg) without loosing of changes.
Maintained by me . Just compare Ace vs CodeMirror for example.

I'd like to implement: html5 tags buttons, clearer dialog windows (less unnesessary parameters), copy/paste for images with transarent for user (hidden) uploading. Syntax highlighting of source. Inline editing for frontend (for admins). These are the part of list of features I want to impement. Do you really think MODx team has a time for improving of content editor? I don't think.

I'm not doubting the communitys, or your, ability to make a great, integrated, plugin/extension to MODx. It's just that I think people are generally more comfortable with "official" plugins.

I'd love for CKEditor to be officially integrated as the main WYSIWYG editor, and thus supported by MODx a bit more "officially". It just feels safer for big production sites, and probably makes it better integrated into MODx (as MODx core team can make core changes to MODx specifically for CKEditor).

I really like the new things that CKEditor brings, and your dedication to make it even better. BTW, does that mean that you're working on core CKEditor stuff, or do you plan to only improve the MODx version of CKEditor?

Is your plugin ready to be used in production?
Do you have a road map, or loose ETAs, for your "I'd like to implement" stuff?

Once again, I'm not doubting any of this, contrary I think it sounds great, so I'd like to know more about it