[rkward-devel] plugins: optionset; use and usability

[Jan Wort]

Hello RKWard Developers, 

We already mailed about some problems usability challenges with the optionlist-dialog. I took a look at the current problems and created some suggestions for a solution that might be easier to use. 

Core problem for the current optionlist is mainly the mapping: It is not easy to know which values from the table map to which gui elements and what the results of this are. This is as well related to the GUI connected to otionset and not only a problem of the optionset control alone. 

E.g. the recode GUI could be redesigned like this: (http://imgur.com/bh9s9N6) so that is is easier to recognize what does what: The titles offer some natural language like accout of what is happening; The NA-coding is either a possible value or a checkbox.

Still, that optionset has some problems on its own, mainly that (visually) the same controls are used for different valuesets (which you select in a space different from the controls: the optionset)

**So the idea was to "wrap" the sets visually somehow**. 

First idea was a tab-like approach: each tab has own values, own controls, so that would be clearer. However, a tab is small, and many values can be set via an optionset. It was unclear how a 100pixel length tab can be made to carry the right, unique and identifying information for (re) finding the right tab. Nevertheless, thats what it would look like: http://imgur.com/QuVVNbL)

A rather simple solution would be to provide the GUI for controlling the values in a pop up. Thats how SPSS is/was doing it. It is clear what does belong to what, but it is not very elegant. (http://imgur.com/fabT823).

A better solution which combines the display of several values, gives easy access to editing them and provide a recognizable grouping could be the use of an "accordion" control. It would look like this: http://imgur.com/52pOvCr

It combines several advantages: 
* It provides a clear structure
* enough space in the accordion’s title to show several values (for recognizing/identifying)
* it is clear which set of elements is selected (visually grouped in the accordion boxes) 
* the sets can be deleted directly (no select row, than delete). 
* The accordion is a standard control and not something unusual I made up myself. 
* You can create any GUI inside the accordion(s), as it is "just" a container. (one would define the GUI only once; it would be repeated in all accordions of the "accordion-optionset")


In Regards to option-tables: I made some additional research and found that such controls are standards for attribute editing in IDEs like eclipse ("Table Cell Editor"); and that too-complex options could be represented in a pop up, as shown for the color selector. Mockup here:  http://imgur.com/HoUYTHB

So in summary: 
* GUI of dialogs apart from optionset might be improved using current controls.
* Optionset usability improvements may be:
  * NOT tabs :(
  * Popups like in SPSS (o.k. usability, versatile)
  * Accordions (good usability, versatile)


and as a different control as suggested by Thomas

* Tables (even better usability, less versatile) 

Kind Regards,
Jan