On 2006.10.06, Robrecht Jacques wrote:
Just to step in. I'm not sure we need a #wysiwyg property. I think we need a #html property. This would say: it makes sense to put HTML codes inside this textarea. If not set, one would be "required" to input plain text. This makes the property *semantically* correct and could even be used inside core.
Then, i suggested :
But i think #wysiwyg is very semantic too if the purpose is to indicate that a RTE must be used because the content may some BBcode (and not HTML) for example. :/ Well, why do not simply say the kind of content expected here simply like a text-based MIME type (and the RTE is invoked then only if can manipulate/generate that MIME type, and Drupal stay that powerfull format independant...) If you agree, what name should have that property in such a case ? Why not something like #mime-type (or simply #mime) or #content-type or better #accept-content (or simply #accept like at <http://www.whatwg.org/specs/web-forms/current-work/#accept> => <http://www.whatwg.org/specs/web-forms/current-work/#extensions1>
The #accept attribute is a proposal to extend #type="textarea" in WobForms2, and it already exists for #type="file" in HTML4... But thinking about it later, it came to me that we are looking for something that must indicate the IME (Input Method Editor) and not the Content-Type accepted (thus, they are related here). And guess what? Xforms specifications suggest #inputmethod for that... <http://xformsinstitute.com/essentials/browse/book.php#ch06-14-fm2xml> <http://www.w3.org/TR/xforms/sliceE.html> :/
On 06 Oct 2006, at 3:05 PM, Michelle Cox wrote:
While I don't agree that Drupal needs a WYSIWYG built in, I do like this idea. If I'm understanding right, it's basically a hook to call whatever editor the user has installed or a plain text area if none. From my non-dev perspective, that sounds like a useful thing. Would be especially nice if there was a way to make it so that, for example, my users get BBCode and I get QuickTags. And that they only show up when editing the main text of a node. for the longest time i've advocated that the tinymce module etc just extend the form and add a '#wysiwyg' => true property, to whatever field they want.
this means anyone else can also go and add that property to any form they feel like.
if the element is set , and the module is not available, it is just ignored.
for the longest time i've advocated that the tinymce module etc just extend the form and add a '#wysiwyg' => true property, to whatever field they want.
this means anyone else can also go and add that property to any form they feel like.
if the element is set , and the module is not available, it is just ignored.
-- little thoughts