[development] rich text editor

David Metzler metzlerd at metzlerd.com
Tue Feb 5 04:42:49 UTC 2008

Yes there were several discussions about this prior to code freeze  
for D6.  Issues were filed which mainly got marked as postponed, for  
all the right reasons.

I submitted one myself, but have since come to believe that Gabor has  
the closest take on this.  I'd love to see the ability for RTE enable/ 
disable to be tied to the type of markup rather than wether we have a  
textarea field.  Basically I think it boils down to giving the RTE  
maintainers some meta data beyond is it a text area.

Currently it's difficult to tell the difference between a textarea  
filed that's designed for a "show this block on these pages" textarea  
and a "Here's the HTML markup for the view header" textarea.  Ideally  
we need to know which input filters are selected and be able to say,  
"enable or disable RTE for these textareas.".  There might be a way  
to do this by examining the forms array in a form alter hook. but if  
it is realy easy, I'd love to see at minimum helper functions to  
attempt this.  There's a lot of room for improvement here without  
trying to solve all of the issues associated with RTE's.

On Feb 4, 2008, at 3:53 AM, catch wrote:

> On Feb 4, 2008 11:34 AM, Greg Knaddison wrote:
> I personally am mostly interested in the discussion in terms of "how
> can I the user or module developer be sure that the RTE isn't applied
> to certain textboxes" since these can be a bit of a pain on
> admin/settings/ pages.
> Regards,
> Greg
> Did I see discussion somewhere about adding a fapi #editor  
> property? Is there an issue for this somewhere or did it stay as  
> discussion?
> The big thing for me is that although I really dislike wysiwyg, my  
> users really need code insertion buttons  (this  is mainly in a  
> forum, they're generally comfortable with bbcode, and would end up  
> typing it directly into a wysiwyg for weeks if I switched) - so any  
> editor in core that I wouldn't immediately switch off on every site  
> would need to have a permanent 'code view'  - not as a switch in  
> the editor itself, but an admin setting which removes js  
> representation in the text area itself, so it just deals with  
> insertion of the actual tags. Something which does what both  
> wymeditor (which looks like it's moving towards opera/safari  
> support) and jTagEditor does really. This, again, would reduce the  
> need for quite so many contribs, and make it very useful for  
> install profiles (on for bloggers, off for forums - or a mixture of  
> the two for a community site by node type).

More information about the development mailing list