Hi Mitch,
Thanks for your thorough response, I think I now have a clear picture of
where I need to go. Part of the requirements I am working on is the ability
to generate new forms definitions from an existing database table. I had
thought of generating an XFrom compatible xml file, but it looks like ODK
Survey goes from Excel into Json to generate a new form and there’s no
Xform involved. This being the case I could try to generate a formDef.json,
though it looks like a pretty complex object . Will this be the most
effective/practical way to go about this?
Thanks again for all your help,
Eric.
On 8 Oct 2014, at 6:27 pm, Mitch Sundt mitchellsundt@gmail.com wrote:
(1) the URL port (8000) is the same value as defined in the Gruntfile.js.
You would need to edit that to change to use a different port. There
shouldn't be anything on port 80 (the default port) unless you were using a
much earlier version of the tools? Or unless you have some sort of port
redirect set up on port 8000.
(2) ah, yes, the device dimension is not propagated to the next screen,
even though the selection is retained. You will need to select a different
dimension, then select the dimension you want. This is a bug.
(3) nearly everything is customizable. See the grid screen example.
We use handlebars ( http://handlebarsjs.com/ ) to generate the HTML. You
can customize these templates by copying and modifying them, and then
referring to the copy. If you do customize the templates, you can store
your customizations either under the 'assets' directory (e.g., create a
directory named 'assets/templates' and place them in there -- for changes
that would be shared across forms) or you can store them with your form
definition under the tables/tableid/forms/formid/ directory (e.g., in a
templates directory under that.
In the ApplicationDesigner, these directories are under the 'app'
directory.
The standard templates are in framework/survey/templates
To reference your customized template, create a column in your XLSX survey
sheet called 'templatePath' and then reference the file using a relative
path like:
../assets/templates/yourtemplate.handlebars
../tables/tableid/forms/formid/templates/yourtemplate.handlebars
W.r.t. customizations, we would like to move away from JQueryMobile and
toward Bootstrap. This would make page transitions ~1.5 seconds faster.
This would also enable us to do a more nuanced re-rendering of the screens.
No ETA on the change, but it is on our wish list.
(4) we use the WebSQL asynchronous API when developing the forms on the
desktop on Chrome. On the device, we remap this into a Java callback
interface into the ODK Survey APK. This eliminates any concern about this
interface going away in the Android Webkit, and it also enables us to
replace the database with an encrypted database at some point in the
future, should we see the need.
There have been plugins that had added WebSQL functionality in Firefox
(not sure any are active right now). If WebSQL is ever removed from Chrome,
we would likely switch to Firefox with a custom plugin that provides the
functionality that we use.
Mitch
On Wed, Oct 8, 2014 at 2:48 PM, eric.ramirez.sv@gmail.com wrote:
Hi,
Thanks for all the great work! I am using opendatakit.survey-js on
Fedora/Chrome, here are my comments:
- In Framework/index.html, the IFrame defaults to localhost:8000/...,
forms loeaded after I removed the port.
-My goal is to be able to create a form to be used on a tablet, when I
pick a tablet size on the "Device Dimension" menu, the change only works on
the form listing/main menu, it goes back into Droid size once I enter the
form. Is there a way to apply the size change to the entire form.
- Since I intend to use ODKSurvey on a Tablet, I am looking at ways to
fit more questions on each pages/views, even columns/menus if it were
possible. It looks like the form gets created after parsing the formDef.js
file, is there a way to edit the resulting form/html?
-Looking at your code I see that the project is using Web SQL which is
supported in Chrome but not in Firefox, I also hear that Web SQL has been
deprecated for a while now, I guess it would be nice to be able to debug on
different browsers but more importantly to know that the storage piece is
bound to an active project. Are there any plans to migrate to a more widely
supported storage?
Thanks in advance for your help and congrats again for a great piece of
software
Eric.
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to a topic in the
Google Groups "ODK Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/opendatakit-developers/GD0LJWHVmkk/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
