Posted by douggreen on September 20, 2008 at 5:07pm
Jump to:
| Project: | Coder |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Issue Summary
I think that hiding the selection form in the fieldset can be confusing to users. Does this patch improve the usability of the coder selection form?
| Attachment | Size |
|---|---|
| selectionform.patch | 733 bytes |
Comments
#1
Ok, first off the patch works and applies cleanly.
I've never had any problems with the usability of the form, but then I'm probably too familiar with it and someone who uses the module less frequently should review the patch. However, here's my 2cents:
It does make the text for the collapsed fieldset longer, and therefore possibly easier for people to spot. It'd be nice if we could separate it from the result sets a bit more. Perhaps we could separate the selection form from the results by using some text? At present if the form fieldset is collapsed some extra text appears above it - this is done using the #prefix attribute. We could add a #suffix one? We could also consider putting all of the result fieldsets into one parent "Results" fieldset to separate it even more.
Actually I think a combination of these would work best, so put all the result fieldsets into one container and give the container some #prefix text explaining the results. For example, you could say that collapsed result sets mean there are no problems with that module, or you could explain the different message severities.
Cheers,
Stella