Added the <rank> form control, closes #104
#180
Conversation
|
@MartijnR This looks great. If you don't mind, I'd like to wait until there is a concrete implementation before merging. I've gotten the feedback that it's confusing to have things in the spec that don't exist anywhere and since this is coming really soon, I think it's easiest to merge once the feature is in somewhere. |
|
|
How's it going with the Collect widget? Enketo will have one (a rough one because of minimal funding) next week. Interesting challenge is the 'empty' state of the widget. Still trying to figure that out UI-wise. |
|
Great! It's ready on the Collect side as well but probably won't go out for another couple weeks. Clearing the value currently re-establishes the original order -- I couldn't come up with another reasonable option. When you say 'empty' state, do you mean you'd like an enumerator to be able to indicate that they have skipped the question? For that I'd tend to say the form creator should account for that by doing something like asking whether the enumerator has a preferred order and adjusting the relevance of the rank question based on that response. |
Yes, and in addition, the enumerator may also decide later to clear the value (the recorded ranked list). This would also make the "required" condition work normally. So my approach is to visually show an empty state of the widget (which means the value is ""). It may say "Click to start" or something. This way it will have all the functionality that other widgets have (in Enketo). In Enketo there will be no way to restore the original order, I think. Clicking reset will simply keep the order but clear the value and visually show the empty state. |
|
Hmm, we should probably coordinate on this. Do you have a rough sketch of the UI you have in mind? |
|
Yes, like this: No value in model (after reset, or after loading empty form):
Has value (and value updates automatically in model, when user changes order):
|
|
The same 'empty state' requirements could also be met with a 'Confirm' button, but I liked it less. |
|
We have implementations ready to ship and XLSForm support! |
No description provided.