The admin mode functionality is possible because eHealth Nigeria contracted
with Nafundi to create and share it with the ODK Community.
Big thanks to Evelyn, Adam and the entire eHealth Nigeria team for this
fantastic contribution!
Translators:
With the addition of admin mode, there are 28 new strings to translate.
Since the automated online translation website has shut down, we need you
to do a more manual process:
click on the values-xx directory corresponding to the language code you
are using (e.g,., values-de for german)
select the 'strings.xml' file (right pane).
To the right of the displayed translations file, you will see a 'View
raw file' link. Click that.
Right-click, and choose 'View page source'
In that window, select-all, paste it into your favorite text editor,
save as 'strings.xml', and perform the translations (new strings are added
to the bottom of the file).
When done, please open an issue http://code.google.com/p/opendatakit/issues/list and use 'Attach a file' to
attach this updated strings.xml file to the issue. In the issue, please
state what language (values-xx) you are submitting.
I generally make private builds for the translator to verify the
translations; updated translations will be in the next maintenance release.
And if you want a language that has not yet been translated, follow the
above steps, beginning with values/strings.xml (the english-language
strings). In the issue you create, cite the iso-639-1 language code for
which you are providing a translation.
···
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
This is exciting news, and welcome functionality. It will help ease
the minds of our researchers.
I have one question. We have 10 - 20 tablets that we'll be using in
the field to collect data and would like to use this functionality to
restrict what our data collectors can do.
I'm not keen on having to handle each tablet to enable the
functionality, but I can add it to our setup workflow if necessary.
Is there any way that can automate this though? For example by
replicating the ODK Collect directory structure on external storage
from one device to another?
···
On Tue, Nov 27, 2012 at 6:39 AM, Mitch S wrote:
> ODK Collect 1.2.2 Revision 1021 is now available on the downloads page:
> http://code.google.com/p/opendatakit/downloads/list
>
> This is also being pushed to Google Play. See
> http://code.google.com/p/opendatakit/wiki/CollectReleaseNotes for details.
>
> Key changes:
>
> issue 28 - provide admin mode restrictions on some user preferences
> issue 715 - filipino translation
> issue 722 - georgian translation
>
> The admin mode functionality is possible because eHealth Nigeria contracted
> with Nafundi to create and share it with the ODK Community.
>
> Big thanks to Evelyn, Adam and the entire eHealth Nigeria team for this
> fantastic contribution!
>
> Translators:
>
> With the addition of admin mode, there are 28 new strings to translate.
> Since the automated online translation website has shut down, we need you to
> do a more manual process:
>
> 1) go to
> http://code.google.com/p/opendatakit/source/browse?repo=collect#hg%2Fres
> 2) click on the values-xx directory corresponding to the language code you
> are using (e.g,., values-de for german)
> 3) select the 'strings.xml' file (right pane).
> 4) To the right of the displayed translations file, you will see a 'View raw
> file' link. Click that.
> 5) Right-click, and choose 'View page source'
> 6) In that window, select-all, paste it into your favorite text editor, save
> as 'strings.xml', and perform the translations (new strings are added to the
> bottom of the file).
> 7) When done, please open an issue
> http://code.google.com/p/opendatakit/issues/list and use 'Attach a file' to
> attach this updated strings.xml file to the issue. In the issue, please
> state what language (values-xx) you are submitting.
>
> I generally make private builds for the translator to verify the
> translations; updated translations will be in the next maintenance release.
>
> And if you want a language that has not yet been translated, follow the
> above steps, beginning with values/strings.xml (the english-language
> strings). In the issue you create, cite the iso-639-1 language code for
> which you are providing a translation.
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitchellsundt@gmail.com
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
You can set whatever defaults you want if you are generating your own
build of Collect. Alternatively, you (or someone you hire) can code up
a feature to read defaults from a file on disk.
···
On Mon, Nov 26, 2012 at 5:22 PM, Corey Wallis wrote:
> Hi Mitch,
>
> This is exciting news, and welcome functionality. It will help ease
> the minds of our researchers.
>
> I have one question. We have 10 - 20 tablets that we'll be using in
> the field to collect data and would like to use this functionality to
> restrict what our data collectors can do.
>
> I'm not keen on having to handle each tablet to enable the
> functionality, but I can add it to our setup workflow if necessary.
>
> Is there any way that can automate this though? For example by
> replicating the ODK Collect directory structure on external storage
> from one device to another?
>
> Any thoughts will be welcome.
>
> With thanks.
>
> -Corey
>
> Senior Software Engineer - MaGDAA Project
> (http://magdaaproject.org)
>
> On Tue, Nov 27, 2012 at 6:39 AM, Mitch S wrote:
>> ODK Collect 1.2.2 Revision 1021 is now available on the downloads page:
>> http://code.google.com/p/opendatakit/downloads/list
>>
>> This is also being pushed to Google Play. See
>> http://code.google.com/p/opendatakit/wiki/CollectReleaseNotes for details.
>>
>> Key changes:
>>
>> issue 28 - provide admin mode restrictions on some user preferences
>> issue 715 - filipino translation
>> issue 722 - georgian translation
>>
>> The admin mode functionality is possible because eHealth Nigeria contracted
>> with Nafundi to create and share it with the ODK Community.
>>
>> Big thanks to Evelyn, Adam and the entire eHealth Nigeria team for this
>> fantastic contribution!
>>
>> Translators:
>>
>> With the addition of admin mode, there are 28 new strings to translate.
>> Since the automated online translation website has shut down, we need you to
>> do a more manual process:
>>
>> 1) go to
>> http://code.google.com/p/opendatakit/source/browse?repo=collect#hg%2Fres
>> 2) click on the values-xx directory corresponding to the language code you
>> are using (e.g,., values-de for german)
>> 3) select the 'strings.xml' file (right pane).
>> 4) To the right of the displayed translations file, you will see a 'View raw
>> file' link. Click that.
>> 5) Right-click, and choose 'View page source'
>> 6) In that window, select-all, paste it into your favorite text editor, save
>> as 'strings.xml', and perform the translations (new strings are added to the
>> bottom of the file).
>> 7) When done, please open an issue
>> http://code.google.com/p/opendatakit/issues/list and use 'Attach a file' to
>> attach this updated strings.xml file to the issue. In the issue, please
>> state what language (values-xx) you are submitting.
>>
>> I generally make private builds for the translator to verify the
>> translations; updated translations will be in the next maintenance release.
>>
>> And if you want a language that has not yet been translated, follow the
>> above steps, beginning with values/strings.xml (the english-language
>> strings). In the issue you create, cite the iso-639-1 language code for
>> which you are providing a translation.
>> --
>> Mitch Sundt
>> Software Engineer
>> University of Washington
>> mitchellsundt@gmail.com
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
···
On Mon, Nov 26, 2012 at 9:25 PM, Yaw Anokwa wrote:
You can set whatever defaults you want if you are generating your own
build of Collect. Alternatively, you (or someone you hire) can code up
a feature to read defaults from a file on disk.
This is exciting news, and welcome functionality. It will help ease
the minds of our researchers.
I have one question. We have 10 - 20 tablets that we'll be using in
the field to collect data and would like to use this functionality to
restrict what our data collectors can do.
I'm not keen on having to handle each tablet to enable the
functionality, but I can add it to our setup workflow if necessary.
Is there any way that can automate this though? For example by
replicating the ODK Collect directory structure on external storage
from one device to another?
issue 28 - provide admin mode restrictions on some user preferences
issue 715 - filipino translation
issue 722 - georgian translation
The admin mode functionality is possible because eHealth Nigeria
contracted
with Nafundi to create and share it with the ODK Community.
Big thanks to Evelyn, Adam and the entire eHealth Nigeria team for this
fantastic contribution!
Translators:
With the addition of admin mode, there are 28 new strings to translate.
Since the automated online translation website has shut down, we need
you to
do a more manual process:
click on the values-xx directory corresponding to the language code
you
are using (e.g,., values-de for german)
select the 'strings.xml' file (right pane).
To the right of the displayed translations file, you will see a
'View raw
file' link. Click that.
Right-click, and choose 'View page source'
In that window, select-all, paste it into your favorite text editor,
save
as 'strings.xml', and perform the translations (new strings are added
to the
bottom of the file).
When done, please open an issue http://code.google.com/p/opendatakit/issues/list and use 'Attach a
file' to
attach this updated strings.xml file to the issue. In the issue, please
state what language (values-xx) you are submitting.
I generally make private builds for the translator to verify the
translations; updated translations will be in the next maintenance
release.
And if you want a language that has not yet been translated, follow the
above steps, beginning with values/strings.xml (the english-language
strings). In the issue you create, cite the iso-639-1 language code for
which you are providing a translation.
"Like a camera I use the negative to develop..uDig"
"Success is the ability to go from one failure to another with no loss of
enthusiasm"
----------------------------------------------------------------------------------------------------------> OutSourceRox*
* Roxroy K. Bollers
GIS and IT Consultant
tel. 592.685.2737 ......................................................... Follow Us On Facebook http://www.facebook.com/OutSourceRox
Google+ https://plus.google.com/114064153117817313312 Web http://twitinternational.com/outsourcerox.htm
These configuration settings are using the Android Preferences mechanism,
so they are specific to an individual phone.
If anyone wants to sponsor a developer to write code to contribute back to
the main branch, as Yaw suggests, one solution is to have the app look for
a configuration file upon start-up, apply those configuration settings,
then remove the file. The file would then need to be copied to a known
location during set-up.
During downloads from Google Play, an optional "expansion file" is copied
to one such location, and that might be the best spot to look for this
file. I don't think it is possible, but if two apks with the same id can
co-exist in app store but have different publishers and different
"expansion file" attachments, it would be very slick to enable different
teams to package the configuration file (and custom splash screen, initial
form set, or set of forms to request, etc.) into a zip as the "expansion
file" and simply use the vanilla ODK apk to create their own individual
Google Play deployments. This would allow extensive customization without
any need to recompile the Java code, and would be a huge win if it were
possible.
Mitch
···
On Mon, Nov 26, 2012 at 6:35 PM, Roxroy Bollers wrote:
You can set whatever defaults you want if you are generating your own
build of Collect. Alternatively, you (or someone you hire) can code up
a feature to read defaults from a file on disk.
This is exciting news, and welcome functionality. It will help ease
the minds of our researchers.
I have one question. We have 10 - 20 tablets that we'll be using in
the field to collect data and would like to use this functionality to
restrict what our data collectors can do.
I'm not keen on having to handle each tablet to enable the
functionality, but I can add it to our setup workflow if necessary.
Is there any way that can automate this though? For example by
replicating the ODK Collect directory structure on external storage
from one device to another?
issue 28 - provide admin mode restrictions on some user preferences
issue 715 - filipino translation
issue 722 - georgian translation
The admin mode functionality is possible because eHealth Nigeria
contracted
with Nafundi to create and share it with the ODK Community.
Big thanks to Evelyn, Adam and the entire eHealth Nigeria team for this
fantastic contribution!
Translators:
With the addition of admin mode, there are 28 new strings to translate.
Since the automated online translation website has shut down, we need
you to
do a more manual process:
click on the values-xx directory corresponding to the language code
you
are using (e.g,., values-de for german)
select the 'strings.xml' file (right pane).
To the right of the displayed translations file, you will see a
'View raw
file' link. Click that.
Right-click, and choose 'View page source'
In that window, select-all, paste it into your favorite text
editor, save
as 'strings.xml', and perform the translations (new strings are added
to the
bottom of the file).
When done, please open an issue http://code.google.com/p/opendatakit/issues/list and use 'Attach a
file' to
attach this updated strings.xml file to the issue. In the issue,
please
state what language (values-xx) you are submitting.
I generally make private builds for the translator to verify the
translations; updated translations will be in the next maintenance
release.
And if you want a language that has not yet been translated, follow the
above steps, beginning with values/strings.xml (the english-language
strings). In the issue you create, cite the iso-639-1 language code for
which you are providing a translation.