There have been some usability issues with users installing whizzywig, and not knowing how to add icons to buttons (see http://drupal.org/node/200332 and http://drupal.org/node/208456 for more information)

I'll never understand why all these modules don't just include a version of the editor. After installing both this and the extension to allow for XHTML, I tried to create a story with the editor. This editor has a slightly different interface than the rest. While most editors use some relatively standard icons to indicate what the buttons will do, Whizzywig uses only text. I have no problem with text, but this makes it so that the toolbars take up more room in the editor. Additionally, there is no way to tell when the different text styles (bold, italic, etc) are activated. There was really only one other problem I had with the editor. Once I created a link, it was nearly impossible to tell it that I only wanted the link to be on one word, not the whole paragraph.
Screenshot

Comments

westwesterson’s picture

westwesterson commented

Also, this is unrelated, but would it be possible considering both the whizzywig liscense and the drupal liscense to package whizzywig either on site or off, so that users wouldn't have to hunt for all the components on the whizzywig website. This would be a huge usability improvement for module install.

sdecabooter’s picture

sdecabooter commented
Assigned: Unassigned » sdecabooter

Hi,

Thanks for your comments.
When i find some time, i will add the information about the buttons more clearly in the root README.txt file, as currently it directs the user to the README.txt in the /whizzywig folder for more info about this...

Regarding packaging the whizzywig module together with the editor itself: I'm not sure whether this is 'allowed' by the licenses (i'm no license expert at all).
I also seem to remember reading somewhere that Dries (and others) highly discourage putting 3rd party modules in the Drupal CVS, unless really really necessary.
The main reason for me to NOT put the whizzywig editor files in the package itself, is because this way users always have the latest version of Whizzywig upon install. I can't keep myself busy with checking all the time if an updated version of the editor is available on the official website.

However, i might consider adding at least the buttons to the whizzywig Drupal module, as they don't get updated normally anyway (still need to check about licenses though).

Kind regards,
Sven

sdecabooter’s picture

sdecabooter commented
Status: Active » Fixed

I have added the buttons in the CVS repository and update the README.txt files.
I will not package the whizzywig JS files in the CVS repository, for the reasons mentioned in my post above.

I hope adding the buttons automatically fixes the usability issue a bit.

Kind regards,

Sven

westwesterson’s picture

westwesterson commented

great work, thanks, improves this a lot

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.