OK - I’ll have to chime in on this too.
The root of my irritation of ANY of the editors is that they do try to do too much. This is especially true in the context of Etomite/MODx where so much of the page is [potentially] coded already as a result of the template, snippets, etc. etc. As a result, all I want available to my content editors are the very basic tools: bold, italic, headings, lists, images, links. To that end, it looks like
widgEditor does exactly that. On top of that it even appears to handle paragraph tagging vs. line break tagging correctly! (And creates nice readable line breaks in code view mode...!)
I suspect that many layouts/templates are similar to mine in that they have separate CSS. This CSS usually doesn’t work inside the WYSIWYG anyway because the WYSIWYG lacks the proper <div> tags and so forth to properly identify the elements (those are in the template). So having styles available does me no good. But that’s okay. I’ve said it before and I’ll say it again- I don’t want my
content editors worrying about
design choices.
So my preference would be to go with a super simple editor
as the default editor. This will keep the default code trim, and functionality streamlined. If more elaborate editors are desired, the plugin route seems to be the perfect way to go.
Right now, widgEditor looks like a very strong candidate. It’s biggest drawback that I can see is the lack of a good image manager.