Ian Bicking: the old part of his blog

Re: Evaluating WYSIWYG editors

I don't have edit access to the WYSIWYG wiki page (http://www.openplans.org/projects/opencore/what-wysiwyg-is-up-to) -- not surprisingly -- so for what's it's worth, we have some documentation available for Kupu on our learnplone.org site per your UI requirements/goals bullet on end-user documentation.

See: http://learnplone.org/documentation/video/editing-the-body-text-of-a-page/view http://learnplone.org/documentation/glossary/kupu/view http://learnplone.org/documentation/faq/i-can-t-see-the-visual-editor/view http://learnplone.org/documentation/faq/web-browsers/view?searchterm=kupu http://learnplone.org/documentation/tutorial/quick-start/editing-the-body-text

All of this is under a a creative commons license and we're even delivering the site via lightly customized themes via different urls.

See: http://learnplone.onenw.org/documentation

More info about the learnplone.org project at: http://learnplone.org/about

Obviously, it all could use some editing, work, and polish and we plan to continue putting resources into it at ONE/Northwest.

Comment on Evaluating WYSIWYG editors
by Andrew Burkhalter

Comments:

Yeah, but is there documentation on how to make Kupu work in a non-plone setting?

I really really really wanted to like Kupu. The Plone movies were breathtaking. But I'm not using Plone. We have a custom Zope 3 based CMS. I tried and tried and tried to figure out how to customize Kupu to fit in our environment, and it was damn near impossible.

Kupu's ability to do things like find images and links in the CMS are great. I think that's one of my favorite potential features. But the developer documentation was of little or no help. And the package layout seemed geared in such a way that the only way to add third-party / custom support was just to do it inline with the rest of the package, which sucks as it makes upgrades difficult. It seems engineered exclusively for the projects and people who are working on the core.

We went with TinyMCE instead. I'm not a huge fan of it, but it was the easiest to get up and running.

I still want Kupu - I think I can deliver a better user experience for our customers with it. But for all of its claims of modularity, I found Kupu to be very developer hostile.

# Jeff Shell

Both Xinha and TinyMCE have plugins for image and link management. They don't currently have Plone integration, of course, but one hopes that is simpler than writing it from scratch. (Actually last I looked Xinha required a full enumeration of the site for at least some of its plugins, which isn't feasible and would have to be fixed)

I dislike too much out-of-the-box Javascript/backend integration, and much prefer formal interfaces (i.e., documented APIs). So I tend not to put too much weight on existing integration work.

# Ian Bicking