Re: wysiwyg editors

> Don't forget the worthwhile: HTMLArea 3

Think we need some kind of feature list to evaluate each against. Here's
a very preliminary one - please reply with your own stuff:

Musts:
- compatible license (LGPL, BSD, etc)
- works in IE and Moz
- XHTML output
- well-documented and stable API
- in active development/used in existing projects
- allow multiple editors per page
- relocatable files
- no namespace conflicts with netWindows
- not tied to particular server-side environment

Shoulds:
- fully configurable in JS without modifying files
- extensible design (OO, so we can subclass it if necessary)
- smallest possible footprint (both filesize and browser memory)
- event model that can be hooked into netWindows sigs'n'slots
- editor content can be set in JS
- toolbar is customizable (can I add my own image selection pop-up to
choose from list/upload file? can I add my own save handler?)
- CSS style selection on toolbar (limit users to certain classes, not
just tags)
- expose methods such as Copy and Paste so they can be added to
netWindows menus.

Would be nice:
- toolbar can be located anywhere on page (preferably as toolbar_widget
wrapper subclass)
- Keyboard shortcuts customizable (CTRL-B might be used somewhere else)
- expose version of editor, so wrapper knows it will work

That's about all I can think of off the top. I don't want to spend ages
evaluating every editor out there, but do want to choose the right one.

Last thing. What do you think about producing a generic wrapper class,
then implementing specific functionality for particular editors in
subclasses? That'll involve more overhead. Does netWindows need this
kind of flexibility, or should it just say "this is the best editor, use
it"?

Matt


_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org