Skip to content
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

Form Design Workarounds and Tips #181

Closed
adammichaelwood opened this issue Sep 21, 2017 · 5 comments
Closed

Form Design Workarounds and Tips #181

adammichaelwood opened this issue Sep 21, 2017 · 5 comments

Comments

@adammichaelwood
Copy link
Contributor

https://opendatakit.org/help/form-design/workarounds/

This document needs to be brought into the current repo. Along the way, the information in it should be verified directly. Edits for clarity/typos/etc. should be done as well.

@mish24
Copy link
Contributor

mish24 commented Sep 21, 2017

@adammichaelwood Can I work on this? I'll test it along the way as well. But isn't a doc for XLSForm required for this?

@adammichaelwood
Copy link
Contributor Author

isn't a doc for XLSForm required for this?

I think our current thinking is that we don't want to duplicate the xlsform.org site's documentation, but rather point people to it.

It would probably be helpful to have an Intro to Form Design doc, that heads up the FORM DESIGN section, with links to the xlsform.org site.

That could start by pulling in the existing form design pge from opendatakit.org. (You could file an issue and work on it.... but make sure you're not sitting on too many claimed, open issues.)

@lognaturel
Copy link
Member

For the workaround described in the "repeat-groups are not respecting the jr:count setting after a change" section, the form from here should be included to illustrate the technique.

@mish24
Copy link
Contributor

mish24 commented Sep 28, 2017

@adammichaelwood I am done writing the base Form Design doc, so I'll start working for this now!
@opendatakit-bot claim.

@adammichaelwood
Copy link
Contributor Author

All of these items have either been taken care of, or new issues have been added to address them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

3 participants