Closed panterz closed 8 years ago
seems to me some of these (e.g. GPS timeout fallback location) relate more to application level configuration.
So the big question is if we should go for a json file that will include all these elements and the html form will be rendered with fields that are coming from this json file or we can just create a survey.json > that will have the path of the html form.
It seems that the less files we have the better in order to avoid any synchronization and parsing problems. As far as cobweb is concerned, the move from html to json will enable us to:
In any case the html5 should be fairly easy to generate from json using a template (or even string substitution).
We have done this. There's a survey.json. I need to add it on the wiki.
COBWEB has given some few extra requirements. Some extra elements should be predefined inside the form in order the user to download them when he/she downloads the form.
So the big question is if we should go for a json file that will include all these elements and the html form will be rendered with fields that are coming from this json file or we can just create a survey.json that will have the path of the html form.