Closed (won't fix)
Project:
TinyMCE AHAH Integration
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Jan 2009 at 16:56 UTC
Updated:
10 Jun 2009 at 01:13 UTC
Thank you for this module, it´s very important for unlimitted CCK Fields. After using the tinyMCE module I found the tiny tinyMCE module to be my favorite tinyMCE integration in drupal - it´s customizeable with very few javascript.
Unfortunately there are the same problems with CCK like the "normal" Tiny MCE module has and my knowledge about drupal internals is very low...
So my Feature request is - would you please do the same fantastic work for the tiny tinyMCE module?
Comments
Comment #1
effulgentsia commentedSorry for taking so long to respond to this issue. My next step with this module is to get it to work with the wysiwyg project, since I think that's going to become the most standard way of integrating tinymce and other rich text editors into drupal. Once I do that, I'll look into what's involved in also making it work with tiny tiny MCE.
Comment #2
effulgentsia commentedA month ago, I released the Wysiwyg API CCK Integration module. I think the drupal community will benefit from standardizing on the Wysiwyg API module as the way to integrate a text editor (tinymce is a well supported editor within that module). I'm marking this issue as "won't fix" until someone convinces me that there's something important that the tinytinymce module does that the wysiwyg api module doesn't do. But I am open to being convinced of this, so please feel free to re-open this issue to active with a comment indicating why you think the tinytinymce module is still relevant.