TinyMCE Development

For GHOP task #119, I've created a module which creates (or restores) a flexible and secure configuration for TinyMCE with a single button click. You can download the module from the d.o issue queue (after enabling the module, it appears as Administer -> Site configuration -> Set TinyMCE defaults). I would appreciate any feedback on the implementation of the module, the user experience, and the configuration it installs.

My thoughts are below, but I would prefer to hear yours :)

The TinyMCE Defaults module: set up TinyMCE, along with secure input formats, with a mouse click.

Please give feedback on the issue: http://drupal.org/node/202062

@addisun/webchick/other GHOP admins: should I copy the task description over to the GHOP issue queue at http://code.google.com/p/google-highly-open-participation-drupal/issues/... ?

With RC1 of Drupal 6 expected to be released this week, now is the time help update TinyMCE.

Beau Gunderson started a patch back in October, but it isn't finished/functional http://drupal.org/node/180436

If Moxiecode was willing to make changes to TinyMCE to improve functionality with Drupal, what improvements would you like to see?

Has anyone had a chance to try Drush?

http://unbiskant.org/blog/frando/new-drush-module-install-and-update-mod...

This looks like it could either be a solution for TinyMCE's CVS issues or become the reason foreign libraries are going to have to be allowed in the Drupal.org's CVS.

Q. I've added an image/table to my page/story/blog, but it is not showing up when I view it?

A. This is often caused by publishing the item with the Input format set to Filtered HTML. The HTML you've added is inserted into your database, but is filtered out when the item is displayed. This is why you will still see the when you edit the item.

Q. TinyMCE doesn't show up when using theme X?

By far the top issue with TinyMCE are install issues. Of the install issues, the two step install process is the #1 problem users have. I don't think the Moxiecode releases can be included with the module because Moxiecode releases their code with an LGPL license and everything in CVS gets a GPL license automagically. Jeff Eaton wrote about the Drupal and GPL back in February of last year. He used TinyMCE as one of the examples of a module that connects Drupal to non-GPL'ed code.

I spent several hours during OSCMS clearing old issues from the TinyMCE issue queue and grouping issues that have never been resolved or the suggested resolution was never included. My ultimate goal is keep the open issues in the queue limited to 4 or 5 pages. Last weekend by closing all the 4.6 issues, closing old install issues, and marking several issues as duplicate I was able to whittle the list from 13 to 7 pages. I wish I had better tools to group issues and assign tasks, but I'm slogging through this with what I have.

I'm "hosting" the weekly Dojo screencast this week. I will be demo'ing the TinyMCE WYSIWYG toolbar. I will be covering the installation process, the new features available in Drupal 5, and answering as many questions as time allows. I will talk a little bit about the dark days of TinyMCE and how I ended up as the maintainer, but I want to spend more time discussing what direction users what TinyMCE to go. What are the biggest problems that still need to be solved.

Nedjo has done a great job cleaning up CVS and writing 2 feature enabling patches (form based custom TinyMCE configuration and JQuery support). It's been all I could do to keep the back log of issues and feature requests to a minimum while deadlines at my "real" job were my priority.