-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for answers given as a range #38
Comments
Reported by
|
Reported by
|
I like this idea, would this be a select_multiple with an appearance option for "range". humm or would that make sense, because when it is stored as a select_multiple which may not make sense due to the way aggregate stores select_multiple. Which data type are you thinking for this? |
@yanokwa or @lognaturel how are you feeling about this? |
I don't understand the use case well enough to know how this would best be addressed. I would tend to address a range either with two questions (what is the min, what is the max) or with a text field with a regex constraint (number dash number). I think that the original poster may have meant a number picker instead of a slider? If you have an example of this kind of question in use or a UI sketch, that would help possibly move this forward. |
I've sent an email to Emily to see if she can clarify. I agree with @lognaturel that you can do this with two questions (max-min) or even a question that asks the number and then another question that asks what the +/- is. @jnordling Is there a use-case that you are thinking of? What would you expect the UI to look like? |
I got a response from Emily!
|
Either of those interfaces would be nice and it's true that they'd be better than separate controls. I think that with either interface, something new would need to be introduced at the ODK XForms spec level. To make matters a little more confusing, W3C XForms does include a range control described here but what it does is show a slider of a certain range for a user to select a single value. Looks like @spatialdude and @MartijnR have already had some discussion about supporting it at XLSForm/pyxform#79. So we'd have to make sure that whatever we decide on for this control type doesn't cause confusion with that other one. Also, I don't think it's possible for a control to provide two values so either the range would have to be represented as a single value (string like "X-Y" for example) or the widget would need to be represented as two separate controls in the form. One wacky idea would be to have a group appearance that can combine two @MartijnR I'd be interested on some initial high-level feedback on whether you think this is a good thing to support and then if so I can file a issue in the XForms spec repo. |
Yes, let's discuss capturing a range as a spec addition and see if there is a nice way to do this. Hopefully something that already exists or that builds upon a range control that captures a single value. |
Closing pending spec addition. |
Thursday Jul 09, 2015 at 17:38 GMT
Originally opened as getodk/getodk#187 (3 comment(s))
Originally reported on Google Code with ID 186
Reported by
Emily.Kumpel
on 2011-02-17 17:50:51The text was updated successfully, but these errors were encountered: