Let me first say that I'm not against a WYSIWYG editor that works. 

I've just never found one that does.  I've tried TinyMCE on Drupal and have run into more work cleaning up the code it produces than it helped solve in the first place.  I visited the FCKeditor site and managed to break their demo version.

Even when coddled and the desired visual effect is achieved - the code they produce still isn't clean - almost always with superfluous open and close tags that then throw the formatting off for the rest of the page.

This conversation has been had a dozen times on the forum and the general consensus seems to have been.  'Build one that woks, and it will be considered, but right now their isn't one that seems to work *good enough for core*' 

Not to mention we are in code freeze....


Sam Tresler
Skype: samtresler
http://www.treslerdesigns.com

Trae McCombs wrote:
I would +1 this personally.  But the biggest hurdle might be license.  I don't know.

I think by default though, it would be great to have the easy editor for things.  I have a client that has a bunch of 65+ old ladies using Drupal, and teaching them html gets scary.  :)

If we are including things like AJAX and such, why not just trick out the text editors, of course, offer the ability to fall back to normal input mode.

Personally, I'd love to have a vim module for editing in a form! ;)

Trae

On 10/6/06, Drupal Indonesia <support@drupal-id.com> wrote:
Why Drupal 5.x must have built-in WYSIWYG Editor?
General discussion · Drupal 5.x
Drupal-id.com - October 6, 2006 - 07:18

I am a web developer with long experience in PHP Nuke, OpenPHP, and
Mambo/Joomla. After take a deep look at the Drupal source code and coding that
available on TinyMCE and FCKEditor module, I can say that next Drupal version
must has a builtin WYSIWYG Editor. Please CMIIW, but read my reasons first
before you have different opinion:

1. Both TinyMCE and FCKEditor only find <textarea> then translate to their
editor interface.
   Then how to avoid certain Textarea not converted? The anwer is not possible.
What
  TinyMCE does only disable editor on certain page and FCkEditor will work if
the
  textarea >= n rows.

  The real case is disknode module. When you set disnode to allow more than 1
file per disknode
  then the <textarea> of file upload list will converted to Editor. Currently,
you can disable the
  <textarea> on this page but the <textarea> for type description of disknode
will be disabled too.
  You may say, that you can enable the rich-editor-toggle, but you can't set 2
default value:
  the description using Editor and the file upload list using <textarea>.

2. A best solution, IMHO, is provide a function in Drupal to call the Editor.
    This Editor() function simply call the ediitor if available, but if no
editor installed
    then Editor() uses <textarea>.

What are the advantages if Drupal has Editor() function?
1. Developer like me, will be easier to create module that need both Editor and
<textarea>
    in same page/block
2. We can extend the User Administration: adding capability to select which
default editor for
    each users. We can set that default editor for user is: none (mean using
textarea), TinyMCE,
    HTMLArea, FCKEditor or any editor that installed by third party modules.
3. Easier for community website which contain people that aren't not familiar
with HTML tag
4. Easier for blogging site, since blogger usually a person with limited website
knowledge,
    such as journalist, teacher, employee or doctor
5. At the rest, Drupal will no doubt called as the killer CMS. This will add
more powerful to
    Drupal, the best CMS that I love.




--
    Trae McCombs || http://occy.net/
  Founder - Themes.org // Linux.com