Open GoogleCodeExporter opened 9 years ago
We will happily add your resource files to the main code base, so you will not
have to maintain your own copy of ODK Collect unless you are doing other
customizations.
The new functionality in ODK Collect 1.3 to save and restore configuration
settings to/from a file will likely address the issue with setting up your
phones with the proper URLs (or you can continue to maintain your own code tree
with that customization).
There is no solution for the conflict when trying to run two versions of ODK
Collect on the same device. Providers must be unique. The solution would be to
change the package name for your copy of ODK Collect. I believe most groups do
not do that, but instead have a reference copy of ODK Collect running on one
device, and their customized versions running on a different device.
Original comment by mitchellsundt@gmail.com
on 17 Apr 2013 at 6:07
It's possible to modify the ODK ContentProviders to be Authority agnostic. In
this scheme an implementing application would supply an Authority to ODK's
ContentProviders.
See some relevant discussion on StackOverflow:
http://stackoverflow.com/questions/10790919/android-having-provider-authority-in
-the-app-project/10791144#10791144
Original comment by davidpbr...@gmail.com
on 18 Sep 2014 at 6:22
Original issue reported on code.google.com by
mbd.r...@gmail.com
on 4 Apr 2013 at 11:56