hi allen,

another option would be to replace everything with something like xinha, that has plain text and wysiwyg modes in the editor itself. yeah, i get that is probably out of the scope of what you want to consider here ... but just a thought.

Allen Gilliland wrote:
Okay, this is what I propose for the editors ...

1. The only editors enabled by default in new installations will be the "text" and 
"rte/dhtml" editors.

2. I recommend we remove/consolidate the midas, dhtml, text-js, and rte editors 
into a single javascript/dhtml editor.  The look will be based on the rte/dhtml 
editors.  Assuming time permits, we would update this editor to contribute 
better html.

3. The ekit editor is very nice looking, but seems to have some problems.  It always started my 
documents with "<html>" which is bad, and it won't work too well with the 2 
textareas.  I would like to EOL this editor and move it to the sandbox or contrib area where 
someone else can continue supporting it if they want.  It won't be available in a default 
Roller install though.

4. The wiki-js editor will also be removed or placed somewhere like the sandbox 
or contrib areas.

That covers all 7 of our editors.  Speak now if you are really adverse to any 
of these changes.

-- Allen


On Wed, 2006-02-01 at 11:18, Allen Gilliland wrote:
On Wed, 2006-02-01 at 10:54, Lance Lavandowska wrote:
The old configuration had a place for listing which editors to make
available to users (I haven't upgraded since before 1.0) and I don't
recall you removing this when you rewrote the configuration bits.
still there.  a simple comma separated list in the admin UI config page.

On the 2 sections: the "editors" are really just replacements for the
textarea that holds the main content.  You could use an editor twice,
once for the main content and once for the excerpt.  I suppose there
may be issues with the javascript-powered editors, and I wouldn't want
to load up two Ekit applets per page.
exactly.  i took a very brief look at some of the editors and many of them have 
code in them specific to the single textarea approach.

Are you certain modifying the editors is the right solution to the
problem of two textareas?
i'm not sure how else to do it.  if we are going to offer 2 textareas then the 
editors need to support that one way or another.

-- Allen

Lance

Reply via email to