this won't go in because;
1- For 6.x there is no such api. It may be for 7.x
2- BUEditor is not a wysiwyg editor. There are usecases for plain-text fields where for example some characters not available on user's keyboard or some predefined phrases need to be inserted.
1. I know that a some modules still use this feature in D6 (I don't remember if FCK or other editors still do that), so why don't do BUEditor?
2. You're right, so maybe BUEditor (for predefined phrases) will have to filter available buttons? I mean, inserting an IMG tag where the textarea is only for plain text isn't right..
Posted by Dave Reid on February 16, 2010 at 5:33pm
@ufku: I'd really like you to re-consider this. A *LOT* of contrib modules are already using this as an easy way to indicate a settings textarea should never be WYSIWYG or have HTML code at all.
Comments
#1
This patch implements this features...
I'm still asking myself if this module is still maintained anymore...
#2
Re-Rolled against latest -dev (February) release.
#3
this won't go in because;
1- For 6.x there is no such api. It may be for 7.x
2- BUEditor is not a wysiwyg editor. There are usecases for plain-text fields where for example some characters not available on user's keyboard or some predefined phrases need to be inserted.
#4
Hi, thank you for your reply.
1. I know that a some modules still use this feature in D6 (I don't remember if FCK or other editors still do that), so why don't do BUEditor?
2. You're right, so maybe BUEditor (for predefined phrases) will have to filter available buttons? I mean, inserting an IMG tag where the textarea is only for plain text isn't right..
Regards
#5
@ufku: I'd really like you to re-consider this. A *LOT* of contrib modules are already using this as an easy way to indicate a settings textarea should never be WYSIWYG or have HTML code at all.
#6
Seems work is already ongoing : #429684: Add editor: BUEditor
#7
Closing 6.x-1.x issues as this branch is no more supported.