Wish list

Support for IMCE http://drupal.org/project/imce

I second xguardianx's request. IMCE integration would be key. It would keep the buttons down but add a whole lot of functionality.

It would be great if this module could be selectively turned off per text area for a time. For example, if you want to fill one particular node text area with PHP code, you currently have to turn the module off while you do it.

Alternatively, it would be useful to have the module have usage permissions per role, i.e. so it could be set as 'on' for authenticated users but 'off' for administrators.

#joe-b: You mean to manually turn it on-off?

sfranchi - yes, exactly, to be able to turn it off for a time, so the textarea degrades to being a regular textarea for a time.

I agree with this. It would be fantastic to have it enabled/disabled on a role by role basis.

Great module so far though.

Taking notes... :)

Perhaps you could include an option to select which content types it is enabled on? Would make it a really flexible and useful module :)

#gbrussel, You mean field name "and" content type?

Yes, lets say I want to enable it on a content type I have called "recipe", but not on "page".

Is there an ETA on this?

Is there a way to add a button for list items (ul & ol)?

I second the demand to toggle on/off

I have evaluated this module and decided it does not meet my needs at this stage. Thought I'd add a few items to the wish list though to potentially help it along a little, since in concept a very light WYSIWYG editor is exactly what I want.

• For "Where to show the rich text editor", the first option should be to display it only on certain paths, rather than managing it by fields. Take a leaf from the block configuration book in this regard—the interface in my opinion should directly replicate that as a starting point, as it is familiar to people. For instance, I want to be able limit jWYSIWYG to only operate on node/*. In the current system, there is no way to know what the true scope of the effects will be. For instance, while the main textarea on the node edit page is called edit-body, there is no way to know whether there may be textareas in other parts of the site (e.g. admin pages) that may also have a textarea called this.
• Having defined the paths on which the module applies, it should then be possible to control by field where it applies within those pages. This interface would basically be along the lines of the current interface, but would be limited by the path preferences above.
• The "jwysiwyg note: The id of this field is edit-body" text is useful when configuring jWYSIWYG, but that is done once whereas that text will be there forever. There should be a preference so this can be turned on during configuration, after which it can be turned off.
• There should be a preference to turn on and off each of the potential styling options. I do not want to give end users the capacity to left-center-right align text, so I should be able to turn this off. In the vast majority of sites, users should never be setting H1s, probably not even H2s, within a textarea, since they should be reserved for site and page titles, so I want to turn those off too. You get the idea.
• H4 would be a good addition/substitution for H1/H2—but that is obviously not a module issue.

About IMCE: http://code.google.com/p/jwysiwyg/issues/detail?id=55#c2 (my solution)

Please test it:)