I would like to get some clarifications on having custom elements or custom
organisation of form elements. A simple example is having more than one
form element on a page. My thinking is that to implement this on ODK
Collect would require changes to ODK Collect. Is it possible to include
custom form engines? i.e extend/override the current form engine.
I also noticed the availability of ODK survey which is reliant on
javascript though is still uses the Xform standard. Would it be easier to
do such on ODK survey than ODK collect.
Thanks!
Correction: ODK Survey does not use XForms. It is entirely JSON /
javascript based. It has its own intermediate representation (formDef.json)
and its own XLSX form design syntax incompatible with the tools used for
ODK Collect.
ODK Collect only allows rendering of the predefined set of widgets, either
one per page, or multiple per page, in a vertical scrolling region. For
extensions, we support launching of external apps to present more complex
visuals. If a widget is of general use, and contributed under an Apache 2
license, we will incorporate it into the main code tree.
···
-----
You should definitely look at ODK Survey. It is exactly intended for
easy-to-use yet highly-customized form layout (this will become even easier
later this spring).
I would like to get some clarifications on having custom elements or
custom organisation of form elements. A simple example is having more than
one form element on a page. My thinking is that to implement this on ODK
Collect would require changes to ODK Collect. Is it possible to include
custom form engines? i.e extend/override the current form engine.
I also noticed the availability of ODK survey which is reliant on
javascript though is still uses the Xform standard. Would it be easier to
do such on ODK survey than ODK collect.
Thanks!