Carl you are exactly right and now that I think about it the behavior
(sorta) makes sense. Thanks about the tip of the 'back' button that does
seem to work (as a work around) but because the keyboard is covering up the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the keyboard if it
sees only text inputs on a page but it would be better if it didn't. And
practically it doesn't save any time because it would pop it up when you
select a text input box anyway. And if it wasn't there you would see all the
fields that it hides when it pops up. Is it possible to have a 'hidden'
input box, for example a select input, that isn't visible (or take space)
then the keyboard would not automatically pop up. (At least I've found where
I mix input flavors on a page it doesn't pop up.)
-steve-
···
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung wrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to be that
you don't have enough inputs (text or other) to over-fill a screen so
Android doesn't think it should scroll. Then, when one of the top inputs is
selected the keyboard covers the bottom. If you have more inputs than fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up, the keyboard
should get dismissed and reveal your hidden text inputs. Then you should be
able to select the input and it will get moved above the soft-keyboard when
it pops up. I tested both of the above with Swype on my phone and it worked
as expected.
I think I remember reading something about manually handling screen size
changes (like when the keyboard pops ups), so I'll look into it and see if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts steve@roberts.org wrote:
I had no problem with 1.1.7 installing and the old forms worked just
fine. However I am having problems with multiple text inputs on one page.
If I have more than 2 then I can't scroll down to the ones covered by the
(swype) on-screen keyboard. I can't dismiss the keyboard and scroll
either. I do notice on other pages that have a mix of input types it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine or install
it on your local machine. So yes, you can create another instance and
operate it in parallel.
For Collect, it will override your existing version. It won't delete
your data, though. Your forms will be re-detected automatically. Your
saved data will still be on the sdcard, but the new version won't be able to
read it (from this version on, upgrading shouldn't cause this problem,
though).
I'll let Waylon or Mitch comment about the status of programatic access
to aggregate data and the tool to migrate data from a .9x instance to a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install the
betas in parallel with my existing instances - or will they over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is this
available?
I understand there was planned to be a new method of accessing data
held under Aggregate programatically - are details of this interface
available?
Many Thanks
Kirby
--
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
--
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
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a textbox is the
first or only input on a page. For all other widget types (as the first or
only) the keyboard is hidden. This was a highly requested feature
originally when we only supported a single question per screen to minimize
'clicks'.
I just checked in a fix that makes the field scrollable when the
soft-keyboard pops up automatically. Now it's the exact same behavior as a
screen with no text-inputs and too many elements to fit on the screen. That
is, it shows the scroll bar to indicate there are more fields.
-Carl
···
On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts wrote:
Carl you are exactly right and now that I think about it the behavior
(sorta) makes sense. Thanks about the tip of the 'back' button that does
seem to work (as a work around) but because the keyboard is covering up the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the keyboard if it
sees only text inputs on a page but it would be better if it didn't. And
practically it doesn't save any time because it would pop it up when you
select a text input box anyway. And if it wasn't there you would see all the
fields that it hides when it pops up. Is it possible to have a 'hidden'
input box, for example a select input, that isn't visible (or take space)
then the keyboard would not automatically pop up. (At least I've found where
I mix input flavors on a page it doesn't pop up.)
-steve-
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to be that
you don't have enough inputs (text or other) to over-fill a screen so
Android doesn't think it should scroll. Then, when one of the top inputs is
selected the keyboard covers the bottom. If you have more inputs than fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up, the
keyboard should get dismissed and reveal your hidden text inputs. Then you
should be able to select the input and it will get moved above the
soft-keyboard when it pops up. I tested both of the above with Swype on my
phone and it worked as expected.
I think I remember reading something about manually handling screen size
changes (like when the keyboard pops ups), so I'll look into it and see if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts steve@roberts.org wrote:
I had no problem with 1.1.7 installing and the old forms worked just
fine. However I am having problems with multiple text inputs on one page.
If I have more than 2 then I can't scroll down to the ones covered by the
(swype) on-screen keyboard. I can't dismiss the keyboard and scroll
either. I do notice on other pages that have a mix of input types it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine or
install it on your local machine. So yes, you can create another instance
and operate it in parallel.
For Collect, it will override your existing version. It won't delete
your data, though. Your forms will be re-detected automatically. Your
saved data will still be on the sdcard, but the new version won't be able to
read it (from this version on, upgrading shouldn't cause this problem,
though).
I'll let Waylon or Mitch comment about the status of programatic access
to aggregate data and the tool to migrate data from a .9x instance to a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install the
betas in parallel with my existing instances - or will they over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is this
available?
I understand there was planned to be a new method of accessing data
held under Aggregate programatically - are details of this interface
available?
Many Thanks
Kirby
--
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
--
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
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
Carl,
Thanks for the quick response and fix. Does that mean I just re-download
the beta and that fixes it?
Speaking of minimizing clicks... Is there a way that once a form is "Save
Form and Exit" that it can loop back to the start of the next instance of
that form. Otherwise you got to 'click' several times just to get to the
start of the form entry.
Thanks again.
-steve-
···
On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung wrote:
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a textbox is the
first or only input on a page. For all other widget types (as the first or
only) the keyboard is hidden. This was a highly requested feature
originally when we only supported a single question per screen to minimize
'clicks'.
I just checked in a fix that makes the field scrollable when the
soft-keyboard pops up automatically. Now it's the exact same behavior as a
screen with no text-inputs and too many elements to fit on the screen. That
is, it shows the scroll bar to indicate there are more fields.
-Carl
On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts steve@roberts.org wrote:
Carl you are exactly right and now that I think about it the behavior
(sorta) makes sense. Thanks about the tip of the 'back' button that does
seem to work (as a work around) but because the keyboard is covering up the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the keyboard if
it sees only text inputs on a page but it would be better if it didn't. And
practically it doesn't save any time because it would pop it up when you
select a text input box anyway. And if it wasn't there you would see all the
fields that it hides when it pops up. Is it possible to have a 'hidden'
input box, for example a select input, that isn't visible (or take space)
then the keyboard would not automatically pop up. (At least I've found where
I mix input flavors on a page it doesn't pop up.)
-steve-
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to be that
you don't have enough inputs (text or other) to over-fill a screen so
Android doesn't think it should scroll. Then, when one of the top inputs is
selected the keyboard covers the bottom. If you have more inputs than fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up, the
keyboard should get dismissed and reveal your hidden text inputs. Then you
should be able to select the input and it will get moved above the
soft-keyboard when it pops up. I tested both of the above with Swype on my
phone and it worked as expected.
I think I remember reading something about manually handling screen size
changes (like when the keyboard pops ups), so I'll look into it and see if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts steve@roberts.orgwrote:
I had no problem with 1.1.7 installing and the old forms worked just
fine. However I am having problems with multiple text inputs on one page.
If I have more than 2 then I can't scroll down to the ones covered by the
(swype) on-screen keyboard. I can't dismiss the keyboard and scroll
either. I do notice on other pages that have a mix of input types it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine or
install it on your local machine. So yes, you can create another instance
and operate it in parallel.
For Collect, it will override your existing version. It won't delete
your data, though. Your forms will be re-detected automatically. Your
saved data will still be on the sdcard, but the new version won't be able to
read it (from this version on, upgrading shouldn't cause this problem,
though).
I'll let Waylon or Mitch comment about the status of programatic access
to aggregate data and the tool to migrate data from a .9x instance to a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install the
betas in parallel with my existing instances - or will they over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is this
available?
I understand there was planned to be a new method of accessing data
held under Aggregate programatically - are details of this interface
available?
Many Thanks
Kirby
--
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
--
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
--
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
steve,
the fix will be in the next beta release, so you'll have to wait for
that. there is no way to loop back to the start of the next instance.
you might look into repeats (or custom code) if you want that kind of
functionality.
yaw
···
On 06/10/2011, Steve Roberts wrote:
> Carl,
>
> Thanks for the quick response and fix. Does that mean I just re-download
> the beta and that fixes it?
>
> Speaking of minimizing clicks... Is there a way that once a form is "Save
> Form and Exit" that it can loop back to the start of the next instance of
> that form. Otherwise you got to 'click' several times just to get to the
> start of the form entry.
>
> Thanks again.
>
> -steve-
>
> On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung wrote:
>
>> Hey Steve,
>> The behavior of Collect is to pop up a soft keyboard if a textbox is the
>> first or only input on a page. For all other widget types (as the first
>> or
>> only) the keyboard is hidden. This was a highly requested feature
>> originally when we only supported a single question per screen to minimize
>> 'clicks'.
>>
>> I just checked in a fix that makes the field scrollable when the
>> soft-keyboard pops up automatically. Now it's the exact same behavior as
>> a
>> screen with no text-inputs and too many elements to fit on the screen.
>> That
>> is, it shows the scroll bar to indicate there are more fields.
>> -Carl
>>
>>
>>
>> On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts wrote:
>>
>>> Carl you are exactly right and now that I think about it the behavior
>>> (sorta) makes sense. Thanks about the tip of the 'back' button that does
>>> seem to work (as a work around) but because the keyboard is covering up
>>> the
>>> inputs under it it is not obvious that there are more inputs.
>>>
>>> I know Collect thinks its doing us a favor by popping up the keyboard if
>>> it sees only text inputs on a page but it would be better if it didn't.
>>> And
>>> practically it doesn't save any time because it would pop it up when you
>>> select a text input box anyway. And if it wasn't there you would see all
>>> the
>>> fields that it hides when it pops up. Is it possible to have a 'hidden'
>>> input box, for example a select input, that isn't visible (or take space)
>>> then the keyboard would not automatically pop up. (At least I've found
>>> where
>>> I mix input flavors on a page it doesn't pop up.)
>>>
>>> -steve-
>>>
>>> On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung wrote:
>>>
>>>> Hey Steve,
>>>> My guess is you've got 3 or 4 text inputs? The problem seems to be that
>>>> you don't have enough inputs (text or other) to over-fill a screen so
>>>> Android doesn't think it should scroll. Then, when one of the top
>>>> inputs is
>>>> selected the keyboard covers the bottom. If you have more inputs than
>>>> fit
>>>> on a screen, the scrolling still works above the keyboard.
>>>>
>>>> However, if you hit the 'back' button when the keyboard is up, the
>>>> keyboard should get dismissed and reveal your hidden text inputs. Then
>>>> you
>>>> should be able to select the input and it will get moved above the
>>>> soft-keyboard when it pops up. I tested both of the above with Swype on
>>>> my
>>>> phone and it worked as expected.
>>>>
>>>> I think I remember reading something about manually handling screen size
>>>> changes (like when the keyboard pops ups), so I'll look into it and see
>>>> if I
>>>> can force enable the scrolling.
>>>> -Carl
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts wrote:
>>>>
>>>>> I had no problem with 1.1.7 installing and the old forms worked just
>>>>> fine. However I am having problems with multiple text inputs on one
>>>>> page.
>>>>> If I have more than 2 then I can't scroll down to the ones covered by
>>>>> the
>>>>> (swype) on-screen keyboard. I can't dismiss the keyboard and scroll
>>>>> either. I do notice on other pages that have a mix of input types it
>>>>> doesn't seem to be a problem.
>>>>> -steve-
>>>>>
>>>>> On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung wrote:
>>>>>
>>>>>> Hey Kirby,
>>>>>> For Aggregate, you can install up to 10 instances on appengine or
>>>>>> install it on your local machine. So yes, you can create another
>>>>>> instance
>>>>>> and operate it in parallel.
>>>>>>
>>>>>> For Collect, it will override your existing version. It won't delete
>>>>>> your data, though. Your forms will be re-detected automatically.
>>>>>> Your
>>>>>> saved data will still be on the sdcard, but the new version won't be
>>>>>> able to
>>>>>> read it (from this version on, upgrading shouldn't cause this problem,
>>>>>> though).
>>>>>>
>>>>>> I'll let Waylon or Mitch comment about the status of programatic
>>>>>> access
>>>>>> to aggregate data and the tool to migrate data from a .9x instance to
>>>>>> a 1.0
>>>>>> -Carl
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames wrote:
>>>>>>
>>>>>>> Carl,
>>>>>>>
>>>>>>> Thanks for the advice on 'new/updated' features.
>>>>>>>
>>>>>>> Another coupled of questions ...
>>>>>>>
>>>>>>> I've got an exsting Collect/Aggregate instance. Can I install the
>>>>>>> betas in parallel with my existing instances - or will they
>>>>>>> over-write
>>>>>>> my existing versions and data?
>>>>>>>
>>>>>>> I'd naturally like to try out the betas without compromising existing
>>>>>>> data (i.e. data I've collected already).
>>>>>>>
>>>>>>> I believe there was planned to be some migration tool - is this
>>>>>>> available?
>>>>>>>
>>>>>>> I understand there was planned to be a new method of accessing data
>>>>>>> held under Aggregate programatically - are details of this interface
>>>>>>> available?
>>>>>>>
>>>>>>> Many Thanks
>>>>>>>
>>>>>>>
>>>>>>> Kirby
>>>>>>>
>>>>>>> --
>>>>>>> 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
>>>>>>
>>>>>
>>>>> --
>>>>> 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
>>>>
>>>
>>> --
>>> 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
>>
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
Thanks Yaw,
I wasn't aware of 'repeats' and showing my ignorance when I (just now) found
the documentation (http://code.dimagi.com/JavaRosa/wiki/xform) and it is
pretty much Greek to me.
It says:
"We also support the tag, which allows repeating a question or set
of questions an arbitrary number of times. The nodeset attribute of the
specifies the instance node to be parameterized -- that is, it is
this exact node (and all its children) which is duplicated each time a new
repetition is created. Our implementation of is pretty standard,
but it diverges in several ways.
In pure xforms, 'create new repetition' and 'delete repetition' actions are
initiated manually by the user, who does so using special controls
created explicitly for this purpose. JavaRosa provides these actions
automatically as part of the form entry UI. For example, the user will be
prompted when necessary if they want to create a new repetition, and when
they are inside a , the 'delete' option is available under a menu.
These s are unnecessary, and will be ignored if present."
I couldn't make heads or tails out of the examples. Does this mean that I
could put the whole form in a 'repeat' and then somehow at the end of the
form put a button or something asking if I wanted to repeat the questions
then go back to the start if answered yes?
Thanks.
-steve-
···
On Sat, Jun 11, 2011 at 2:43 AM, Yaw Anokwa wrote:
steve,
the fix will be in the next beta release, so you'll have to wait for
that. there is no way to loop back to the start of the next instance.
you might look into repeats (or custom code) if you want that kind of
functionality.
yaw
On 06/10/2011, Steve Roberts steve@roberts.org wrote:
Carl,
Thanks for the quick response and fix. Does that mean I just re-download
the beta and that fixes it?
Speaking of minimizing clicks... Is there a way that once a form is "Save
Form and Exit" that it can loop back to the start of the next instance of
that form. Otherwise you got to 'click' several times just to get to the
start of the form entry.
Thanks again.
-steve-
On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung <carlhartung@gmail.com wrote:
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a textbox is the
first or only input on a page. For all other widget types (as the first
or
only) the keyboard is hidden. This was a highly requested feature
originally when we only supported a single question per screen to
minimize
'clicks'.
I just checked in a fix that makes the field scrollable when the
soft-keyboard pops up automatically. Now it's the exact same behavior
as
a
screen with no text-inputs and too many elements to fit on the screen.
That
is, it shows the scroll bar to indicate there are more fields.
-Carl
On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts steve@roberts.org wrote:
Carl you are exactly right and now that I think about it the behavior
(sorta) makes sense. Thanks about the tip of the 'back' button that
does
seem to work (as a work around) but because the keyboard is covering up
the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the keyboard
if
it sees only text inputs on a page but it would be better if it didn't.
And
practically it doesn't save any time because it would pop it up when
you
select a text input box anyway. And if it wasn't there you would see
all
the
fields that it hides when it pops up. Is it possible to have a
'hidden'
input box, for example a select input, that isn't visible (or take
space)
then the keyboard would not automatically pop up. (At least I've found
where
I mix input flavors on a page it doesn't pop up.)
-steve-
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to be
that
you don't have enough inputs (text or other) to over-fill a screen so
Android doesn't think it should scroll. Then, when one of the top
inputs is
selected the keyboard covers the bottom. If you have more inputs than
fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up, the
keyboard should get dismissed and reveal your hidden text inputs.
Then
you
should be able to select the input and it will get moved above the
soft-keyboard when it pops up. I tested both of the above with Swype
on
my
phone and it worked as expected.
I think I remember reading something about manually handling screen
size
changes (like when the keyboard pops ups), so I'll look into it and
see
if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts <steve@roberts.org wrote:
I had no problem with 1.1.7 installing and the old forms worked just
fine. However I am having problems with multiple text inputs on one
page.
If I have more than 2 then I can't scroll down to the ones covered by
the
(swype) on-screen keyboard. I can't dismiss the keyboard and scroll
either. I do notice on other pages that have a mix of input types it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine or
install it on your local machine. So yes, you can create another
instance
and operate it in parallel.
For Collect, it will override your existing version. It won't
delete
your data, though. Your forms will be re-detected automatically.
Your
saved data will still be on the sdcard, but the new version won't be
able to
read it (from this version on, upgrading shouldn't cause this
problem,
though).
I'll let Waylon or Mitch comment about the status of programatic
access
to aggregate data and the tool to migrate data from a .9x instance
to
a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install the
betas in parallel with my existing instances - or will they
over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising
existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is this
available?
I understand there was planned to be a new method of accessing data
held under Aggregate programatically - are details of this
interface
available?
Many Thanks
Kirby
--
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
--
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
--
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
--
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
steve,
yes. you can put questions inside a repeat and at the end of all the questions, it will ask you if you want to create another repeat. say yes, and it will.
take a look at the household forms (http://code.google.com/p/opendatakit/source/browse/Household+Survey.xml?repo=forms#201) and you'll see a hopefully clear example of how repeats are used.
you can put default data in your repeats and also refer to data within the repeat. so if you enter a child's name in the repeat from the form above, you can use the text of that name when asking about that child's favorite color.
note that there is a jr:template tag that goes into the instance. if you want the form to ask you at the beginning of the repeat about creating a new repeat, keep the template in. if you want to bypass that dialog, remove it. the template thing is confusing, but that's what we have to work with.
anyway. best way to see this in action is to try it out.
yaw
···
On Jun 11, 2011, at 6:16 PM, Steve Roberts wrote:
Thanks Yaw,
I wasn't aware of 'repeats' and showing my ignorance when I (just now) found the documentation (http://code.dimagi.com/JavaRosa/wiki/xform) and it is pretty much Greek to me.
It says:
"We also support the tag, which allows repeating a question or set of questions an arbitrary number of times. The nodeset attribute of the specifies the instance node to be parameterized -- that is, it is this exact node (and all its children) which is duplicated each time a new repetition is created. Our implementation of is pretty standard, but it diverges in several ways.
In pure xforms, 'create new repetition' and 'delete repetition' actions are initiated manually by the user, who does so using special controls created explicitly for this purpose. JavaRosa provides these actions automatically as part of the form entry UI. For example, the user will be prompted when necessary if they want to create a new repetition, and when they are inside a , the 'delete' option is available under a menu. These s are unnecessary, and will be ignored if present."
I couldn't make heads or tails out of the examples. Does this mean that I could put the whole form in a 'repeat' and then somehow at the end of the form put a button or something asking if I wanted to repeat the questions then go back to the start if answered yes?
Thanks.
-steve-
On Sat, Jun 11, 2011 at 2:43 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
the fix will be in the next beta release, so you'll have to wait for
that. there is no way to loop back to the start of the next instance.
you might look into repeats (or custom code) if you want that kind of
functionality.
yaw
On 06/10/2011, Steve Roberts steve@roberts.org wrote:
Carl,
Thanks for the quick response and fix. Does that mean I just re-download
the beta and that fixes it?
Speaking of minimizing clicks... Is there a way that once a form is "Save
Form and Exit" that it can loop back to the start of the next instance of
that form. Otherwise you got to 'click' several times just to get to the
start of the form entry.
Thanks again.
-steve-
On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a textbox is the
first or only input on a page. For all other widget types (as the first
or
only) the keyboard is hidden. This was a highly requested feature
originally when we only supported a single question per screen to minimize
'clicks'.
I just checked in a fix that makes the field scrollable when the
soft-keyboard pops up automatically. Now it's the exact same behavior as
a
screen with no text-inputs and too many elements to fit on the screen.
That
is, it shows the scroll bar to indicate there are more fields.
-Carl
On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts steve@roberts.org wrote:
Carl you are exactly right and now that I think about it the behavior
(sorta) makes sense. Thanks about the tip of the 'back' button that does
seem to work (as a work around) but because the keyboard is covering up
the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the keyboard if
it sees only text inputs on a page but it would be better if it didn't.
And
practically it doesn't save any time because it would pop it up when you
select a text input box anyway. And if it wasn't there you would see all
the
fields that it hides when it pops up. Is it possible to have a 'hidden'
input box, for example a select input, that isn't visible (or take space)
then the keyboard would not automatically pop up. (At least I've found
where
I mix input flavors on a page it doesn't pop up.)
-steve-
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to be that
you don't have enough inputs (text or other) to over-fill a screen so
Android doesn't think it should scroll. Then, when one of the top
inputs is
selected the keyboard covers the bottom. If you have more inputs than
fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up, the
keyboard should get dismissed and reveal your hidden text inputs. Then
you
should be able to select the input and it will get moved above the
soft-keyboard when it pops up. I tested both of the above with Swype on
my
phone and it worked as expected.
I think I remember reading something about manually handling screen size
changes (like when the keyboard pops ups), so I'll look into it and see
if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts steve@roberts.orgwrote:
I had no problem with 1.1.7 installing and the old forms worked just
fine. However I am having problems with multiple text inputs on one
page.
If I have more than 2 then I can't scroll down to the ones covered by
the
(swype) on-screen keyboard. I can't dismiss the keyboard and scroll
either. I do notice on other pages that have a mix of input types it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine or
install it on your local machine. So yes, you can create another
instance
and operate it in parallel.
For Collect, it will override your existing version. It won't delete
your data, though. Your forms will be re-detected automatically.
Your
saved data will still be on the sdcard, but the new version won't be
able to
read it (from this version on, upgrading shouldn't cause this problem,
though).
I'll let Waylon or Mitch comment about the status of programatic
access
to aggregate data and the tool to migrate data from a .9x instance to
a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install the
betas in parallel with my existing instances - or will they
over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is this
available?
I understand there was planned to be a new method of accessing data
held under Aggregate programatically - are details of this interface
available?
Many Thanks
Kirby
--
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
--
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
--
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
--
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
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
Yaw,
Thanks. That is helpful. Later today (After the UW graduation 
I'll
play with it.
As an editorial it does seem like it might be useful to have an option to
submit the current form and start the next. (maybe a menu option) I suppose
if walking between homes/huts between forms its not a big deal to start
fresh for each entry but if you are sitting annotating fish going through a
fish ladder you could be 'clicking' more clicks getting to the form than
entering the data. (Big Fish, Small Fish)
(But as they say "beggars can't be choosers" 
Thanks guys for all you do.
-steve-
···
On Sat, Jun 11, 2011 at 8:30 AM, Yaw Anokwa wrote:
steve,
yes. you can put questions inside a repeat and at the end of all the
questions, it will ask you if you want to create another repeat. say yes,
and it will.
take a look at the household forms (
http://code.google.com/p/opendatakit/source/browse/Household+Survey.xml?repo=forms#201)
and you'll see a hopefully clear example of how repeats are used.
you can put default data in your repeats and also refer to data within the
repeat. so if you enter a child's name in the repeat from the form above,
you can use the text of that name when asking about that child's favorite
color.
note that there is a jr:template tag that goes into the instance. if you
want the form to ask you at the beginning of the repeat about creating a new
repeat, keep the template in. if you want to bypass that dialog, remove it.
the template thing is confusing, but that's what we have to work with.
anyway. best way to see this in action is to try it out.
yaw
On Jun 11, 2011, at 6:16 PM, Steve Roberts wrote:
Thanks Yaw,
I wasn't aware of 'repeats' and showing my ignorance when I (just now)
found the documentation (http://code.dimagi.com/JavaRosa/wiki/xform) and
it is pretty much Greek to me.
It says:
"We also support the tag, which allows repeating a question or
set of questions an arbitrary number of times. The nodeset attribute of the
specifies the instance node to be parameterized -- that is, it is
this exact node (and all its children) which is duplicated each time a new
repetition is created. Our implementation of is pretty standard,
but it diverges in several ways.
In pure xforms, 'create new repetition' and 'delete repetition' actions
are initiated manually by the user, who does so using special
controls created explicitly for this purpose. JavaRosa provides these
actions automatically as part of the form entry UI. For example, the user
will be prompted when necessary if they want to create a new repetition, and
when they are inside a , the 'delete' option is available under a
menu. These s are unnecessary, and will be ignored if present."
I couldn't make heads or tails out of the examples. Does this mean that
I could put the whole form in a 'repeat' and then somehow at the end of the
form put a button or something asking if I wanted to repeat the questions
then go back to the start if answered yes?
Thanks.
-steve-
On Sat, Jun 11, 2011 at 2:43 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
the fix will be in the next beta release, so you'll have to wait for
that. there is no way to loop back to the start of the next instance.
you might look into repeats (or custom code) if you want that kind of
functionality.
yaw
On 06/10/2011, Steve Roberts steve@roberts.org wrote:
Carl,
Thanks for the quick response and fix. Does that mean I just
re-download
the beta and that fixes it?
Speaking of minimizing clicks... Is there a way that once a form is
"Save
Form and Exit" that it can loop back to the start of the next instance
of
that form. Otherwise you got to 'click' several times just to get to
the
start of the form entry.
Thanks again.
-steve-
On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung <carlhartung@gmail.com wrote:
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a textbox is
the
first or only input on a page. For all other widget types (as the
first
or
only) the keyboard is hidden. This was a highly requested feature
originally when we only supported a single question per screen to
minimize
'clicks'.
I just checked in a fix that makes the field scrollable when the
soft-keyboard pops up automatically. Now it's the exact same behavior
as
a
screen with no text-inputs and too many elements to fit on the screen.
That
is, it shows the scroll bar to indicate there are more fields.
-Carl
On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts steve@roberts.org wrote:
Carl you are exactly right and now that I think about it the behavior
(sorta) makes sense. Thanks about the tip of the 'back' button that
does
seem to work (as a work around) but because the keyboard is covering
up
the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the keyboard
if
it sees only text inputs on a page but it would be better if it
didn't.
And
practically it doesn't save any time because it would pop it up when
you
select a text input box anyway. And if it wasn't there you would see
all
the
fields that it hides when it pops up. Is it possible to have a
'hidden'
input box, for example a select input, that isn't visible (or take
space)
then the keyboard would not automatically pop up. (At least I've
found
where
I mix input flavors on a page it doesn't pop up.)
-steve-
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to be
that
you don't have enough inputs (text or other) to over-fill a screen
so
Android doesn't think it should scroll. Then, when one of the top
inputs is
selected the keyboard covers the bottom. If you have more inputs
than
fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up, the
keyboard should get dismissed and reveal your hidden text inputs.
Then
you
should be able to select the input and it will get moved above the
soft-keyboard when it pops up. I tested both of the above with
Swype on
my
phone and it worked as expected.
I think I remember reading something about manually handling screen
size
changes (like when the keyboard pops ups), so I'll look into it and
see
if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts <steve@roberts.org wrote:
I had no problem with 1.1.7 installing and the old forms worked
just
fine. However I am having problems with multiple text inputs on
one
page.
If I have more than 2 then I can't scroll down to the ones covered
by
the
(swype) on-screen keyboard. I can't dismiss the keyboard and
scroll
either. I do notice on other pages that have a mix of input types
it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine or
install it on your local machine. So yes, you can create another
instance
and operate it in parallel.
For Collect, it will override your existing version. It won't
delete
your data, though. Your forms will be re-detected automatically.
Your
saved data will still be on the sdcard, but the new version won't
be
able to
read it (from this version on, upgrading shouldn't cause this
problem,
though).
I'll let Waylon or Mitch comment about the status of programatic
access
to aggregate data and the tool to migrate data from a .9x instance
to
a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install the
betas in parallel with my existing instances - or will they
over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising
existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is this
available?
I understand there was planned to be a new method of accessing
data
held under Aggregate programatically - are details of this
interface
available?
Many Thanks
Kirby
--
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
--
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
--
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
--
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
--
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
As another option, 1.1.7 will let you create a desktop shortcut to a
specific form. Just long press on the desktop to create a shortcut. Using
the shortcut will start you in a specific form and saving/exiting will take
you back to the desktop.
···
On Sat, Jun 11, 2011 at 8:50 AM, Steve Roberts wrote:
Yaw,
Thanks. That is helpful. Later today (After the UW graduation I'll
play with it.
As an editorial it does seem like it might be useful to have an option to
submit the current form and start the next. (maybe a menu option) I suppose
if walking between homes/huts between forms its not a big deal to start
fresh for each entry but if you are sitting annotating fish going through a
fish ladder you could be 'clicking' more clicks getting to the form than
entering the data. (Big Fish, Small Fish)
(But as they say "beggars can't be choosers"
Thanks guys for all you do.
-steve-
On Sat, Jun 11, 2011 at 8:30 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
yes. you can put questions inside a repeat and at the end of all the
questions, it will ask you if you want to create another repeat. say yes,
and it will.
take a look at the household forms (
http://code.google.com/p/opendatakit/source/browse/Household+Survey.xml?repo=forms#201)
and you'll see a hopefully clear example of how repeats are used.
you can put default data in your repeats and also refer to data within the
repeat. so if you enter a child's name in the repeat from the form above,
you can use the text of that name when asking about that child's favorite
color.
note that there is a jr:template tag that goes into the instance. if you
want the form to ask you at the beginning of the repeat about creating a new
repeat, keep the template in. if you want to bypass that dialog, remove it.
the template thing is confusing, but that's what we have to work with.
anyway. best way to see this in action is to try it out.
yaw
On Jun 11, 2011, at 6:16 PM, Steve Roberts wrote:
Thanks Yaw,
I wasn't aware of 'repeats' and showing my ignorance when I (just now)
found the documentation (http://code.dimagi.com/JavaRosa/wiki/xform) and
it is pretty much Greek to me.
It says:
"We also support the tag, which allows repeating a question or
set of questions an arbitrary number of times. The nodeset attribute of the
specifies the instance node to be parameterized -- that is, it is
this exact node (and all its children) which is duplicated each time a new
repetition is created. Our implementation of is pretty standard,
but it diverges in several ways.
In pure xforms, 'create new repetition' and 'delete repetition' actions
are initiated manually by the user, who does so using special
controls created explicitly for this purpose. JavaRosa provides these
actions automatically as part of the form entry UI. For example, the user
will be prompted when necessary if they want to create a new repetition, and
when they are inside a , the 'delete' option is available under a
menu. These s are unnecessary, and will be ignored if present."
I couldn't make heads or tails out of the examples. Does this mean that
I could put the whole form in a 'repeat' and then somehow at the end of the
form put a button or something asking if I wanted to repeat the questions
then go back to the start if answered yes?
Thanks.
-steve-
On Sat, Jun 11, 2011 at 2:43 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
the fix will be in the next beta release, so you'll have to wait for
that. there is no way to loop back to the start of the next instance.
you might look into repeats (or custom code) if you want that kind of
functionality.
yaw
On 06/10/2011, Steve Roberts steve@roberts.org wrote:
Carl,
Thanks for the quick response and fix. Does that mean I just
re-download
the beta and that fixes it?
Speaking of minimizing clicks... Is there a way that once a form is
"Save
Form and Exit" that it can loop back to the start of the next instance
of
that form. Otherwise you got to 'click' several times just to get to
the
start of the form entry.
Thanks again.
-steve-
On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung <carlhartung@gmail.com wrote:
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a textbox is
the
first or only input on a page. For all other widget types (as the
first
or
only) the keyboard is hidden. This was a highly requested feature
originally when we only supported a single question per screen to
minimize
'clicks'.
I just checked in a fix that makes the field scrollable when the
soft-keyboard pops up automatically. Now it's the exact same
behavior as
a
screen with no text-inputs and too many elements to fit on the
screen.
That
is, it shows the scroll bar to indicate there are more fields.
-Carl
On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts steve@roberts.org wrote:
Carl you are exactly right and now that I think about it the
behavior
(sorta) makes sense. Thanks about the tip of the 'back' button that
does
seem to work (as a work around) but because the keyboard is covering
up
the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the
keyboard if
it sees only text inputs on a page but it would be better if it
didn't.
And
practically it doesn't save any time because it would pop it up when
you
select a text input box anyway. And if it wasn't there you would see
all
the
fields that it hides when it pops up. Is it possible to have a
'hidden'
input box, for example a select input, that isn't visible (or take
space)
then the keyboard would not automatically pop up. (At least I've
found
where
I mix input flavors on a page it doesn't pop up.)
-steve-
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to be
that
you don't have enough inputs (text or other) to over-fill a screen
so
Android doesn't think it should scroll. Then, when one of the top
inputs is
selected the keyboard covers the bottom. If you have more inputs
than
fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up, the
keyboard should get dismissed and reveal your hidden text inputs.
Then
you
should be able to select the input and it will get moved above the
soft-keyboard when it pops up. I tested both of the above with
Swype on
my
phone and it worked as expected.
I think I remember reading something about manually handling screen
size
changes (like when the keyboard pops ups), so I'll look into it and
see
if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts <steve@roberts.org wrote:
I had no problem with 1.1.7 installing and the old forms worked
just
fine. However I am having problems with multiple text inputs on
one
page.
If I have more than 2 then I can't scroll down to the ones covered
by
the
(swype) on-screen keyboard. I can't dismiss the keyboard and
scroll
either. I do notice on other pages that have a mix of input types
it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine or
install it on your local machine. So yes, you can create another
instance
and operate it in parallel.
For Collect, it will override your existing version. It won't
delete
your data, though. Your forms will be re-detected automatically.
Your
saved data will still be on the sdcard, but the new version won't
be
able to
read it (from this version on, upgrading shouldn't cause this
problem,
though).
I'll let Waylon or Mitch comment about the status of programatic
access
to aggregate data and the tool to migrate data from a .9x
instance to
a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install
the
betas in parallel with my existing instances - or will they
over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising
existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is this
available?
I understand there was planned to be a new method of accessing
data
held under Aggregate programatically - are details of this
interface
available?
Many Thanks
Kirby
--
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
--
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
--
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
--
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
--
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
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
hmmmm.. I'm having trouble figuring out what you mean. I assume the form
you want the shortcut to needs to be open or selected or something. Can you
give me a few more details on creating the shortcut?
-steve-
-- Painfully slowly typed on my htc EVO --
···
On Sat, Jun 11, 2011 at 10:05 AM, Carl Hartung wrote:
As another option, 1.1.7 will let you create a desktop shortcut to a
specific form. Just long press on the desktop to create a shortcut. Using
the shortcut will start you in a specific form and saving/exiting will take
you back to the desktop.
On Sat, Jun 11, 2011 at 8:50 AM, Steve Roberts steve@roberts.org wrote:
Yaw,
Thanks. That is helpful. Later today (After the UW graduation I'll
play with it.
As an editorial it does seem like it might be useful to have an option to
submit the current form and start the next. (maybe a menu option) I suppose
if walking between homes/huts between forms its not a big deal to start
fresh for each entry but if you are sitting annotating fish going through a
fish ladder you could be 'clicking' more clicks getting to the form than
entering the data. (Big Fish, Small Fish)
(But as they say "beggars can't be choosers"
Thanks guys for all you do.
-steve-
On Sat, Jun 11, 2011 at 8:30 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
yes. you can put questions inside a repeat and at the end of all the
questions, it will ask you if you want to create another repeat. say yes,
and it will.
take a look at the household forms (
http://code.google.com/p/opendatakit/source/browse/Household+Survey.xml?repo=forms#201)
and you'll see a hopefully clear example of how repeats are used.
you can put default data in your repeats and also refer to data within
the repeat. so if you enter a child's name in the repeat from the form
above, you can use the text of that name when asking about that child's
favorite color.
note that there is a jr:template tag that goes into the instance. if you
want the form to ask you at the beginning of the repeat about creating a new
repeat, keep the template in. if you want to bypass that dialog, remove it.
the template thing is confusing, but that's what we have to work with.
anyway. best way to see this in action is to try it out.
yaw
On Jun 11, 2011, at 6:16 PM, Steve Roberts wrote:
Thanks Yaw,
I wasn't aware of 'repeats' and showing my ignorance when I (just now)
found the documentation (http://code.dimagi.com/JavaRosa/wiki/xform) and
it is pretty much Greek to me.
It says:
"We also support the tag, which allows repeating a question or
set of questions an arbitrary number of times. The nodeset attribute of the
specifies the instance node to be parameterized -- that is, it is
this exact node (and all its children) which is duplicated each time a new
repetition is created. Our implementation of is pretty standard,
but it diverges in several ways.
In pure xforms, 'create new repetition' and 'delete repetition' actions
are initiated manually by the user, who does so using special
controls created explicitly for this purpose. JavaRosa provides these
actions automatically as part of the form entry UI. For example, the user
will be prompted when necessary if they want to create a new repetition, and
when they are inside a , the 'delete' option is available under a
menu. These s are unnecessary, and will be ignored if present."
I couldn't make heads or tails out of the examples. Does this mean
that I could put the whole form in a 'repeat' and then somehow at the end of
the form put a button or something asking if I wanted to repeat the
questions then go back to the start if answered yes?
Thanks.
-steve-
On Sat, Jun 11, 2011 at 2:43 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
the fix will be in the next beta release, so you'll have to wait for
that. there is no way to loop back to the start of the next instance.
you might look into repeats (or custom code) if you want that kind of
functionality.
yaw
On 06/10/2011, Steve Roberts steve@roberts.org wrote:
Carl,
Thanks for the quick response and fix. Does that mean I just
re-download
the beta and that fixes it?
Speaking of minimizing clicks... Is there a way that once a form is
"Save
Form and Exit" that it can loop back to the start of the next
instance of
that form. Otherwise you got to 'click' several times just to get to
the
start of the form entry.
Thanks again.
-steve-
On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung < carlhartung@gmail.com>wrote:
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a textbox is
the
first or only input on a page. For all other widget types (as the
first
or
only) the keyboard is hidden. This was a highly requested feature
originally when we only supported a single question per screen to
minimize
'clicks'.
I just checked in a fix that makes the field scrollable when the
soft-keyboard pops up automatically. Now it's the exact same
behavior as
a
screen with no text-inputs and too many elements to fit on the
screen.
That
is, it shows the scroll bar to indicate there are more fields.
-Carl
On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts steve@roberts.org wrote:
Carl you are exactly right and now that I think about it the
behavior
(sorta) makes sense. Thanks about the tip of the 'back' button that
does
seem to work (as a work around) but because the keyboard is
covering up
the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the
keyboard if
it sees only text inputs on a page but it would be better if it
didn't.
And
practically it doesn't save any time because it would pop it up
when you
select a text input box anyway. And if it wasn't there you would
see all
the
fields that it hides when it pops up. Is it possible to have a
'hidden'
input box, for example a select input, that isn't visible (or take
space)
then the keyboard would not automatically pop up. (At least I've
found
where
I mix input flavors on a page it doesn't pop up.)
-steve-
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to
be that
you don't have enough inputs (text or other) to over-fill a screen
so
Android doesn't think it should scroll. Then, when one of the top
inputs is
selected the keyboard covers the bottom. If you have more inputs
than
fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up, the
keyboard should get dismissed and reveal your hidden text inputs.
Then
you
should be able to select the input and it will get moved above the
soft-keyboard when it pops up. I tested both of the above with
Swype on
my
phone and it worked as expected.
I think I remember reading something about manually handling
screen size
changes (like when the keyboard pops ups), so I'll look into it
and see
if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts <steve@roberts.org wrote:
I had no problem with 1.1.7 installing and the old forms worked
just
fine. However I am having problems with multiple text inputs on
one
page.
If I have more than 2 then I can't scroll down to the ones
covered by
the
(swype) on-screen keyboard. I can't dismiss the keyboard and
scroll
either. I do notice on other pages that have a mix of input
types it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine
or
install it on your local machine. So yes, you can create
another
instance
and operate it in parallel.
For Collect, it will override your existing version. It won't
delete
your data, though. Your forms will be re-detected
automatically.
Your
saved data will still be on the sdcard, but the new version
won't be
able to
read it (from this version on, upgrading shouldn't cause this
problem,
though).
I'll let Waylon or Mitch comment about the status of programatic
access
to aggregate data and the tool to migrate data from a .9x
instance to
a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install
the
betas in parallel with my existing instances - or will they
over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising
existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is this
available?
I understand there was planned to be a new method of accessing
data
held under Aggregate programatically - are details of this
interface
available?
Many Thanks
Kirby
--
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
--
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
--
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
--
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
--
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
--
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
Sure thing. First, make sure that the form appears in ODK's list when you
press 'start new form'.
Then:
press the phone's home button to get to your desktop/home screen ->
press-and-hold on any blank space until a menu appears -> shortcut -> ODK
Form -> [whatever form you want]
···
On Sat, Jun 11, 2011 at 11:35 AM, Steve Roberts wrote:
hmmmm.. I'm having trouble figuring out what you mean. I assume the form
you want the shortcut to needs to be open or selected or something. Can you
give me a few more details on creating the shortcut?
-steve-
-- Painfully slowly typed on my htc EVO --
On Sat, Jun 11, 2011 at 10:05 AM, Carl Hartung carlhartung@gmail.comwrote:
As another option, 1.1.7 will let you create a desktop shortcut to a
specific form. Just long press on the desktop to create a shortcut. Using
the shortcut will start you in a specific form and saving/exiting will take
you back to the desktop.
On Sat, Jun 11, 2011 at 8:50 AM, Steve Roberts steve@roberts.org wrote:
Yaw,
Thanks. That is helpful. Later today (After the UW graduation I'll
play with it.
As an editorial it does seem like it might be useful to have an option to
submit the current form and start the next. (maybe a menu option) I suppose
if walking between homes/huts between forms its not a big deal to start
fresh for each entry but if you are sitting annotating fish going through a
fish ladder you could be 'clicking' more clicks getting to the form than
entering the data. (Big Fish, Small Fish)
(But as they say "beggars can't be choosers"
Thanks guys for all you do.
-steve-
On Sat, Jun 11, 2011 at 8:30 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
yes. you can put questions inside a repeat and at the end of all the
questions, it will ask you if you want to create another repeat. say yes,
and it will.
take a look at the household forms (
http://code.google.com/p/opendatakit/source/browse/Household+Survey.xml?repo=forms#201)
and you'll see a hopefully clear example of how repeats are used.
you can put default data in your repeats and also refer to data within
the repeat. so if you enter a child's name in the repeat from the form
above, you can use the text of that name when asking about that child's
favorite color.
note that there is a jr:template tag that goes into the instance. if you
want the form to ask you at the beginning of the repeat about creating a new
repeat, keep the template in. if you want to bypass that dialog, remove it.
the template thing is confusing, but that's what we have to work with.
anyway. best way to see this in action is to try it out.
yaw
On Jun 11, 2011, at 6:16 PM, Steve Roberts wrote:
Thanks Yaw,
I wasn't aware of 'repeats' and showing my ignorance when I (just now)
found the documentation (http://code.dimagi.com/JavaRosa/wiki/xform)
and it is pretty much Greek to me.
It says:
"We also support the tag, which allows repeating a question
or set of questions an arbitrary number of times. The nodeset attribute of
the specifies the instance node to be parameterized -- that is, it
is this exact node (and all its children) which is duplicated each time a
new repetition is created. Our implementation of is pretty
standard, but it diverges in several ways.
In pure xforms, 'create new repetition' and 'delete repetition'
actions are initiated manually by the user, who does so using special
controls created explicitly for this purpose. JavaRosa provides
these actions automatically as part of the form entry UI. For example, the
user will be prompted when necessary if they want to create a new
repetition, and when they are inside a , the 'delete' option is
available under a menu. These s are unnecessary, and will be
ignored if present."
I couldn't make heads or tails out of the examples. Does this mean
that I could put the whole form in a 'repeat' and then somehow at the end of
the form put a button or something asking if I wanted to repeat the
questions then go back to the start if answered yes?
Thanks.
-steve-
On Sat, Jun 11, 2011 at 2:43 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
the fix will be in the next beta release, so you'll have to wait for
that. there is no way to loop back to the start of the next instance.
you might look into repeats (or custom code) if you want that kind of
functionality.
yaw
On 06/10/2011, Steve Roberts steve@roberts.org wrote:
Carl,
Thanks for the quick response and fix. Does that mean I just
re-download
the beta and that fixes it?
Speaking of minimizing clicks... Is there a way that once a form is
"Save
Form and Exit" that it can loop back to the start of the next
instance of
that form. Otherwise you got to 'click' several times just to get
to the
start of the form entry.
Thanks again.
-steve-
On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung < carlhartung@gmail.com>wrote:
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a textbox
is the
first or only input on a page. For all other widget types (as the
first
or
only) the keyboard is hidden. This was a highly requested feature
originally when we only supported a single question per screen to
minimize
'clicks'.
I just checked in a fix that makes the field scrollable when the
soft-keyboard pops up automatically. Now it's the exact same
behavior as
a
screen with no text-inputs and too many elements to fit on the
screen.
That
is, it shows the scroll bar to indicate there are more fields.
-Carl
On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts steve@roberts.org wrote:
Carl you are exactly right and now that I think about it the
behavior
(sorta) makes sense. Thanks about the tip of the 'back' button
that does
seem to work (as a work around) but because the keyboard is
covering up
the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the
keyboard if
it sees only text inputs on a page but it would be better if it
didn't.
And
practically it doesn't save any time because it would pop it up
when you
select a text input box anyway. And if it wasn't there you would
see all
the
fields that it hides when it pops up. Is it possible to have a
'hidden'
input box, for example a select input, that isn't visible (or take
space)
then the keyboard would not automatically pop up. (At least I've
found
where
I mix input flavors on a page it doesn't pop up.)
-steve-
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to
be that
you don't have enough inputs (text or other) to over-fill a
screen so
Android doesn't think it should scroll. Then, when one of the
top
inputs is
selected the keyboard covers the bottom. If you have more inputs
than
fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up,
the
keyboard should get dismissed and reveal your hidden text inputs.
Then
you
should be able to select the input and it will get moved above
the
soft-keyboard when it pops up. I tested both of the above with
Swype on
my
phone and it worked as expected.
I think I remember reading something about manually handling
screen size
changes (like when the keyboard pops ups), so I'll look into it
and see
if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts < steve@roberts.org>wrote:
I had no problem with 1.1.7 installing and the old forms worked
just
fine. However I am having problems with multiple text inputs on
one
page.
If I have more than 2 then I can't scroll down to the ones
covered by
the
(swype) on-screen keyboard. I can't dismiss the keyboard and
scroll
either. I do notice on other pages that have a mix of input
types it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine
or
install it on your local machine. So yes, you can create
another
instance
and operate it in parallel.
For Collect, it will override your existing version. It won't
delete
your data, though. Your forms will be re-detected
automatically.
Your
saved data will still be on the sdcard, but the new version
won't be
able to
read it (from this version on, upgrading shouldn't cause this
problem,
though).
I'll let Waylon or Mitch comment about the status of
programatic
access
to aggregate data and the tool to migrate data from a .9x
instance to
a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install
the
betas in parallel with my existing instances - or will they
over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising
existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is
this
available?
I understand there was planned to be a new method of accessing
data
held under Aggregate programatically - are details of this
interface
available?
Many Thanks
Kirby
--
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
--
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
--
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
--
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
--
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
--
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
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
Excellent!
-steve-
-- Painfully slowly typed on my htc EVO --
···
On Sat, Jun 11, 2011 at 11:46 AM, Carl Hartung wrote:
Sure thing. First, make sure that the form appears in ODK's list when you
press 'start new form'.
Then:
press the phone's home button to get to your desktop/home screen ->
press-and-hold on any blank space until a menu appears -> shortcut -> ODK
Form -> [whatever form you want]
On Sat, Jun 11, 2011 at 11:35 AM, Steve Roberts steve@roberts.org wrote:
hmmmm.. I'm having trouble figuring out what you mean. I assume the form
you want the shortcut to needs to be open or selected or something. Can you
give me a few more details on creating the shortcut?
-steve-
-- Painfully slowly typed on my htc EVO --
On Sat, Jun 11, 2011 at 10:05 AM, Carl Hartung carlhartung@gmail.comwrote:
As another option, 1.1.7 will let you create a desktop shortcut to a
specific form. Just long press on the desktop to create a shortcut. Using
the shortcut will start you in a specific form and saving/exiting will take
you back to the desktop.
On Sat, Jun 11, 2011 at 8:50 AM, Steve Roberts steve@roberts.orgwrote:
Yaw,
Thanks. That is helpful. Later today (After the UW graduation
I'll play with it.
As an editorial it does seem like it might be useful to have an option
to submit the current form and start the next. (maybe a menu option) I
suppose if walking between homes/huts between forms its not a big deal to
start fresh for each entry but if you are sitting annotating fish going
through a fish ladder you could be 'clicking' more clicks getting to the
form than entering the data. (Big Fish, Small Fish)
(But as they say "beggars can't be choosers"
Thanks guys for all you do.
-steve-
On Sat, Jun 11, 2011 at 8:30 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
yes. you can put questions inside a repeat and at the end of all the
questions, it will ask you if you want to create another repeat. say yes,
and it will.
take a look at the household forms (
http://code.google.com/p/opendatakit/source/browse/Household+Survey.xml?repo=forms#201)
and you'll see a hopefully clear example of how repeats are used.
you can put default data in your repeats and also refer to data within
the repeat. so if you enter a child's name in the repeat from the form
above, you can use the text of that name when asking about that child's
favorite color.
note that there is a jr:template tag that goes into the instance. if
you want the form to ask you at the beginning of the repeat about creating a
new repeat, keep the template in. if you want to bypass that dialog, remove
it. the template thing is confusing, but that's what we have to work with.
anyway. best way to see this in action is to try it out.
yaw
On Jun 11, 2011, at 6:16 PM, Steve Roberts wrote:
Thanks Yaw,
I wasn't aware of 'repeats' and showing my ignorance when I (just
now) found the documentation (
http://code.dimagi.com/JavaRosa/wiki/xform) and it is pretty much
Greek to me.
It says:
"We also support the tag, which allows repeating a question
or set of questions an arbitrary number of times. The nodeset attribute of
the specifies the instance node to be parameterized -- that is, it
is this exact node (and all its children) which is duplicated each time a
new repetition is created. Our implementation of is pretty
standard, but it diverges in several ways.
In pure xforms, 'create new repetition' and 'delete repetition'
actions are initiated manually by the user, who does so using special
controls created explicitly for this purpose. JavaRosa provides
these actions automatically as part of the form entry UI. For example, the
user will be prompted when necessary if they want to create a new
repetition, and when they are inside a , the 'delete' option is
available under a menu. These s are unnecessary, and will be
ignored if present."
I couldn't make heads or tails out of the examples. Does this mean
that I could put the whole form in a 'repeat' and then somehow at the end of
the form put a button or something asking if I wanted to repeat the
questions then go back to the start if answered yes?
Thanks.
-steve-
On Sat, Jun 11, 2011 at 2:43 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
the fix will be in the next beta release, so you'll have to wait for
that. there is no way to loop back to the start of the next instance.
you might look into repeats (or custom code) if you want that kind of
functionality.
yaw
On 06/10/2011, Steve Roberts steve@roberts.org wrote:
Carl,
Thanks for the quick response and fix. Does that mean I just
re-download
the beta and that fixes it?
Speaking of minimizing clicks... Is there a way that once a form is
"Save
Form and Exit" that it can loop back to the start of the next
instance of
that form. Otherwise you got to 'click' several times just to get
to the
start of the form entry.
Thanks again.
-steve-
On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung < carlhartung@gmail.com>wrote:
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a textbox
is the
first or only input on a page. For all other widget types (as the
first
or
only) the keyboard is hidden. This was a highly requested feature
originally when we only supported a single question per screen to
minimize
'clicks'.
I just checked in a fix that makes the field scrollable when the
soft-keyboard pops up automatically. Now it's the exact same
behavior as
a
screen with no text-inputs and too many elements to fit on the
screen.
That
is, it shows the scroll bar to indicate there are more fields.
-Carl
On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts steve@roberts.org wrote:
Carl you are exactly right and now that I think about it the
behavior
(sorta) makes sense. Thanks about the tip of the 'back' button
that does
seem to work (as a work around) but because the keyboard is
covering up
the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the
keyboard if
it sees only text inputs on a page but it would be better if it
didn't.
And
practically it doesn't save any time because it would pop it up
when you
select a text input box anyway. And if it wasn't there you would
see all
the
fields that it hides when it pops up. Is it possible to have a
'hidden'
input box, for example a select input, that isn't visible (or
take space)
then the keyboard would not automatically pop up. (At least I've
found
where
I mix input flavors on a page it doesn't pop up.)
-steve-
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to
be that
you don't have enough inputs (text or other) to over-fill a
screen so
Android doesn't think it should scroll. Then, when one of the
top
inputs is
selected the keyboard covers the bottom. If you have more
inputs than
fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up,
the
keyboard should get dismissed and reveal your hidden text
inputs. Then
you
should be able to select the input and it will get moved above
the
soft-keyboard when it pops up. I tested both of the above with
Swype on
my
phone and it worked as expected.
I think I remember reading something about manually handling
screen size
changes (like when the keyboard pops ups), so I'll look into it
and see
if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts < steve@roberts.org>wrote:
I had no problem with 1.1.7 installing and the old forms worked
just
fine. However I am having problems with multiple text inputs
on one
page.
If I have more than 2 then I can't scroll down to the ones
covered by
the
(swype) on-screen keyboard. I can't dismiss the keyboard and
scroll
either. I do notice on other pages that have a mix of input
types it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine
or
install it on your local machine. So yes, you can create
another
instance
and operate it in parallel.
For Collect, it will override your existing version. It won't
delete
your data, though. Your forms will be re-detected
automatically.
Your
saved data will still be on the sdcard, but the new version
won't be
able to
read it (from this version on, upgrading shouldn't cause this
problem,
though).
I'll let Waylon or Mitch comment about the status of
programatic
access
to aggregate data and the tool to migrate data from a .9x
instance to
a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install
the
betas in parallel with my existing instances - or will they
over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising
existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is
this
available?
I understand there was planned to be a new method of
accessing data
held under Aggregate programatically - are details of this
interface
available?
Many Thanks
Kirby
--
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
--
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
--
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
--
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
--
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
--
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
--
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
Hmmm. My Evo broke and I replaced it and am reinstalling my apps. I just
installed 1.1.7 Beta 2. It works and my forms on my sd card seemed to all be
happy. However I can't make a shortcut. I start odk, bring up the form I
want, press home and bring up the short-cut list and odk is not on it. I
have the latest android update for 2.3.3. (I don't do this often. In fact
have only done it for odk. Am I missing a step?) Thanks. -steve-
···
On Sat, Jun 11, 2011 at 11:46 AM, Carl Hartung wrote:
Sure thing. First, make sure that the form appears in ODK's list when you
press 'start new form'.
Then:
press the phone's home button to get to your desktop/home screen ->
press-and-hold on any blank space until a menu appears -> shortcut -> ODK
Form -> [whatever form you want]
On Sat, Jun 11, 2011 at 11:35 AM, Steve Roberts steve@roberts.org wrote:
hmmmm.. I'm having trouble figuring out what you mean. I assume the form
you want the shortcut to needs to be open or selected or something. Can you
give me a few more details on creating the shortcut?
-steve-
-- Painfully slowly typed on my htc EVO --
On Sat, Jun 11, 2011 at 10:05 AM, Carl Hartung carlhartung@gmail.comwrote:
As another option, 1.1.7 will let you create a desktop shortcut to a
specific form. Just long press on the desktop to create a shortcut. Using
the shortcut will start you in a specific form and saving/exiting will take
you back to the desktop.
On Sat, Jun 11, 2011 at 8:50 AM, Steve Roberts steve@roberts.orgwrote:
Yaw,
Thanks. That is helpful. Later today (After the UW graduation
I'll play with it.
As an editorial it does seem like it might be useful to have an option
to submit the current form and start the next. (maybe a menu option) I
suppose if walking between homes/huts between forms its not a big deal to
start fresh for each entry but if you are sitting annotating fish going
through a fish ladder you could be 'clicking' more clicks getting to the
form than entering the data. (Big Fish, Small Fish)
(But as they say "beggars can't be choosers"
Thanks guys for all you do.
-steve-
On Sat, Jun 11, 2011 at 8:30 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
yes. you can put questions inside a repeat and at the end of all the
questions, it will ask you if you want to create another repeat. say yes,
and it will.
take a look at the household forms (
http://code.google.com/p/opendatakit/source/browse/Household+Survey.xml?repo=forms#201)
and you'll see a hopefully clear example of how repeats are used.
you can put default data in your repeats and also refer to data within
the repeat. so if you enter a child's name in the repeat from the form
above, you can use the text of that name when asking about that child's
favorite color.
note that there is a jr:template tag that goes into the instance. if
you want the form to ask you at the beginning of the repeat about creating a
new repeat, keep the template in. if you want to bypass that dialog, remove
it. the template thing is confusing, but that's what we have to work with.
anyway. best way to see this in action is to try it out.
yaw
On Jun 11, 2011, at 6:16 PM, Steve Roberts wrote:
Thanks Yaw,
I wasn't aware of 'repeats' and showing my ignorance when I (just
now) found the documentation (
http://code.dimagi.com/JavaRosa/wiki/xform) and it is pretty much
Greek to me.
It says:
"We also support the tag, which allows repeating a question
or set of questions an arbitrary number of times. The nodeset attribute of
the specifies the instance node to be parameterized -- that is, it
is this exact node (and all its children) which is duplicated each time a
new repetition is created. Our implementation of is pretty
standard, but it diverges in several ways.
In pure xforms, 'create new repetition' and 'delete repetition'
actions are initiated manually by the user, who does so using special
controls created explicitly for this purpose. JavaRosa provides
these actions automatically as part of the form entry UI. For example, the
user will be prompted when necessary if they want to create a new
repetition, and when they are inside a , the 'delete' option is
available under a menu. These s are unnecessary, and will be
ignored if present."
I couldn't make heads or tails out of the examples. Does this mean
that I could put the whole form in a 'repeat' and then somehow at the end of
the form put a button or something asking if I wanted to repeat the
questions then go back to the start if answered yes?
Thanks.
-steve-
On Sat, Jun 11, 2011 at 2:43 AM, Yaw Anokwa yanokwa@gmail.com wrote:
steve,
the fix will be in the next beta release, so you'll have to wait for
that. there is no way to loop back to the start of the next instance.
you might look into repeats (or custom code) if you want that kind of
functionality.
yaw
On 06/10/2011, Steve Roberts steve@roberts.org wrote:
Carl,
Thanks for the quick response and fix. Does that mean I just
re-download
the beta and that fixes it?
Speaking of minimizing clicks... Is there a way that once a form is
"Save
Form and Exit" that it can loop back to the start of the next
instance of
that form. Otherwise you got to 'click' several times just to get
to the
start of the form entry.
Thanks again.
-steve-
On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung < carlhartung@gmail.com>wrote:
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a textbox
is the
first or only input on a page. For all other widget types (as the
first
or
only) the keyboard is hidden. This was a highly requested feature
originally when we only supported a single question per screen to
minimize
'clicks'.
I just checked in a fix that makes the field scrollable when the
soft-keyboard pops up automatically. Now it's the exact same
behavior as
a
screen with no text-inputs and too many elements to fit on the
screen.
That
is, it shows the scroll bar to indicate there are more fields.
-Carl
On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts steve@roberts.org wrote:
Carl you are exactly right and now that I think about it the
behavior
(sorta) makes sense. Thanks about the tip of the 'back' button
that does
seem to work (as a work around) but because the keyboard is
covering up
the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the
keyboard if
it sees only text inputs on a page but it would be better if it
didn't.
And
practically it doesn't save any time because it would pop it up
when you
select a text input box anyway. And if it wasn't there you would
see all
the
fields that it hides when it pops up. Is it possible to have a
'hidden'
input box, for example a select input, that isn't visible (or
take space)
then the keyboard would not automatically pop up. (At least I've
found
where
I mix input flavors on a page it doesn't pop up.)
-steve-
On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung carlhartung@gmail.comwrote:
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems to
be that
you don't have enough inputs (text or other) to over-fill a
screen so
Android doesn't think it should scroll. Then, when one of the
top
inputs is
selected the keyboard covers the bottom. If you have more
inputs than
fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is up,
the
keyboard should get dismissed and reveal your hidden text
inputs. Then
you
should be able to select the input and it will get moved above
the
soft-keyboard when it pops up. I tested both of the above with
Swype on
my
phone and it worked as expected.
I think I remember reading something about manually handling
screen size
changes (like when the keyboard pops ups), so I'll look into it
and see
if I
can force enable the scrolling.
-Carl
On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts < steve@roberts.org>wrote:
I had no problem with 1.1.7 installing and the old forms worked
just
fine. However I am having problems with multiple text inputs
on one
page.
If I have more than 2 then I can't scroll down to the ones
covered by
the
(swype) on-screen keyboard. I can't dismiss the keyboard and
scroll
either. I do notice on other pages that have a mix of input
types it
doesn't seem to be a problem.
-steve-
On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung carlhartung@gmail.comwrote:
Hey Kirby,
For Aggregate, you can install up to 10 instances on appengine
or
install it on your local machine. So yes, you can create
another
instance
and operate it in parallel.
For Collect, it will override your existing version. It won't
delete
your data, though. Your forms will be re-detected
automatically.
Your
saved data will still be on the sdcard, but the new version
won't be
able to
read it (from this version on, upgrading shouldn't cause this
problem,
though).
I'll let Waylon or Mitch comment about the status of
programatic
access
to aggregate data and the tool to migrate data from a .9x
instance to
a 1.0
-Carl
On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames kirby.james@gmail.comwrote:
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I install
the
betas in parallel with my existing instances - or will they
over-write
my existing versions and data?
I'd naturally like to try out the betas without compromising
existing
data (i.e. data I've collected already).
I believe there was planned to be some migration tool - is
this
available?
I understand there was planned to be a new method of
accessing data
held under Aggregate programatically - are details of this
interface
available?
Many Thanks
Kirby
--
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
--
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
--
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
--
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
--
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
--
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
--
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
can't duplicate it on my phone, but sounds like a bug somewhere. i've filed
it at http://code.google.com/p/opendatakit/issues/detail?id=264.
···
On Sat, Jul 16, 2011 at 10:15, Steve Roberts wrote:
> Hmmm. My Evo broke and I replaced it and am reinstalling my apps. I just
> installed 1.1.7 Beta 2. It works and my forms on my sd card seemed to all be
> happy. However I can't make a shortcut. I start odk, bring up the form I
> want, press home and bring up the short-cut list and odk is not on it. I
> have the latest android update for 2.3.3. (I don't do this often. In fact
> have only done it for odk. Am I missing a step?) Thanks. -steve-
>
> On Sat, Jun 11, 2011 at 11:46 AM, Carl Hartung wrote:
>>
>> Sure thing. First, make sure that the form appears in ODK's list when you
>> press 'start new form'.
>> Then:
>> press the phone's home button to get to your desktop/home screen ->
>> press-and-hold on any blank space until a menu appears -> shortcut -> ODK
>> Form -> [whatever form you want]
>>
>>
>>
>> On Sat, Jun 11, 2011 at 11:35 AM, Steve Roberts wrote:
>>>
>>> hmmmm.. I'm having trouble figuring out what you mean. I assume the form
>>> you want the shortcut to needs to be open or selected or something. Can you
>>> give me a few more details on creating the shortcut?
>>>
>>> -steve-
>>>
>>> -- Painfully slowly typed on my htc EVO --
>>>
>>> On Sat, Jun 11, 2011 at 10:05 AM, Carl Hartung wrote:
>>>>
>>>> As another option, 1.1.7 will let you create a desktop shortcut to a
>>>> specific form. Just long press on the desktop to create a shortcut. Using
>>>> the shortcut will start you in a specific form and saving/exiting will take
>>>> you back to the desktop.
>>>>
>>>>
>>>> On Sat, Jun 11, 2011 at 8:50 AM, Steve Roberts wrote:
>>>>>
>>>>> Yaw,
>>>>>
>>>>> Thanks. That is helpful. Later today (After the UW graduation ;-)
>>>>> I'll play with it.
>>>>>
>>>>> As an editorial it does seem like it might be useful to have an option
>>>>> to submit the current form and start the next. (maybe a menu option) I
>>>>> suppose if walking between homes/huts between forms its not a big deal to
>>>>> start fresh for each entry but if you are sitting annotating fish going
>>>>> through a fish ladder you could be 'clicking' more clicks getting to the
>>>>> form than entering the data. (Big Fish, Small Fish)
>>>>>
>>>>> (But as they say "beggars can't be choosers" :-)
>>>>>
>>>>> Thanks guys for all you do.
>>>>>
>>>>> -steve-
>>>>>
>>>>> On Sat, Jun 11, 2011 at 8:30 AM, Yaw Anokwa wrote:
>>>>>>
>>>>>> steve,
>>>>>>
>>>>>> yes. you can put questions inside a repeat and at the end of all the
>>>>>> questions, it will ask you if you want to create another repeat. say yes,
>>>>>> and it will.
>>>>>>
>>>>>> take a look at the household forms
>>>>>> (http://code.google.com/p/opendatakit/source/browse/Household+Survey.xml?repo=forms#201)
>>>>>> and you'll see a hopefully clear example of how repeats are used.
>>>>>>
>>>>>> you can put default data in your repeats and also refer to data within
>>>>>> the repeat. so if you enter a child's name in the repeat from the form
>>>>>> above, you can use the text of that name when asking about that child's
>>>>>> favorite color.
>>>>>>
>>>>>> note that there is a jr:template tag that goes into the instance. if
>>>>>> you want the form to ask you at the beginning of the repeat about creating a
>>>>>> new repeat, keep the template in. if you want to bypass that dialog, remove
>>>>>> it. the template thing is confusing, but that's what we have to work with.
>>>>>>
>>>>>> anyway. best way to see this in action is to try it out.
>>>>>>
>>>>>> yaw
>>>>>>
>>>>>> On Jun 11, 2011, at 6:16 PM, Steve Roberts wrote:
>>>>>>
>>>>>> > Thanks Yaw,
>>>>>> >
>>>>>> > I wasn't aware of 'repeats' and showing my ignorance when I (just
>>>>>> > now) found the documentation (http://code.dimagi.com/JavaRosa/wiki/xform)
>>>>>> > and it is pretty much Greek to me.
>>>>>> >
>>>>>> > It says:
>>>>>> > "We also support the tag, which allows repeating a question
>>>>>> > or set of questions an arbitrary number of times. The nodeset attribute of
>>>>>> > the specifies the instance node to be parameterized -- that is, it
>>>>>> > is this exact node (and all its children) which is duplicated each time a
>>>>>> > new repetition is created. Our implementation of is pretty
>>>>>> > standard, but it diverges in several ways.
>>>>>> >
>>>>>> > In pure xforms, 'create new repetition' and 'delete repetition'
>>>>>> > actions are initiated manually by the user, who does so using special
>>>>>> > controls created explicitly for this purpose. JavaRosa provides
>>>>>> > these actions automatically as part of the form entry UI. For example, the
>>>>>> > user will be prompted when necessary if they want to create a new
>>>>>> > repetition, and when they are inside a , the 'delete' option is
>>>>>> > available under a menu. These s are unnecessary, and will be
>>>>>> > ignored if present."
>>>>>> >
>>>>>> > I couldn't make heads or tails out of the examples. Does this mean
>>>>>> > that I could put the whole form in a 'repeat' and then somehow at the end of
>>>>>> > the form put a button or something asking if I wanted to repeat the
>>>>>> > questions then go back to the start if answered yes?
>>>>>> >
>>>>>> > Thanks.
>>>>>> >
>>>>>> > -steve-
>>>>>> >
>>>>>> > On Sat, Jun 11, 2011 at 2:43 AM, Yaw Anokwa wrote:
>>>>>> > steve,
>>>>>> >
>>>>>> > the fix will be in the next beta release, so you'll have to wait for
>>>>>> > that. there is no way to loop back to the start of the next
>>>>>> > instance.
>>>>>> > you might look into repeats (or custom code) if you want that kind
>>>>>> > of
>>>>>> > functionality.
>>>>>> >
>>>>>> > yaw
>>>>>> >
>>>>>> > On 06/10/2011, Steve Roberts wrote:
>>>>>> > > Carl,
>>>>>> > >
>>>>>> > > Thanks for the quick response and fix. Does that mean I just
>>>>>> > > re-download
>>>>>> > > the beta and that fixes it?
>>>>>> > >
>>>>>> > > Speaking of minimizing clicks... Is there a way that once a form
>>>>>> > > is "Save
>>>>>> > > Form and Exit" that it can loop back to the start of the next
>>>>>> > > instance of
>>>>>> > > that form. Otherwise you got to 'click' several times just to get
>>>>>> > > to the
>>>>>> > > start of the form entry.
>>>>>> > >
>>>>>> > > Thanks again.
>>>>>> > >
>>>>>> > > -steve-
>>>>>> > >
>>>>>> > > On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung wrote:
>>>>>> > >
>>>>>> > >> Hey Steve,
>>>>>> > >> The behavior of Collect is to pop up a soft keyboard if a textbox
>>>>>> > >> is the
>>>>>> > >> first or only input on a page. For all other widget types (as
>>>>>> > >> the first
>>>>>> > >> or
>>>>>> > >> only) the keyboard is hidden. This was a highly requested
>>>>>> > >> feature
>>>>>> > >> originally when we only supported a single question per screen to
>>>>>> > >> minimize
>>>>>> > >> 'clicks'.
>>>>>> > >>
>>>>>> > >> I just checked in a fix that makes the field scrollable when the
>>>>>> > >> soft-keyboard pops up automatically. Now it's the exact same
>>>>>> > >> behavior as
>>>>>> > >> a
>>>>>> > >> screen with no text-inputs and too many elements to fit on the
>>>>>> > >> screen.
>>>>>> > >> That
>>>>>> > >> is, it shows the scroll bar to indicate there are more fields.
>>>>>> > >> -Carl
>>>>>> > >>
>>>>>> > >>
>>>>>> > >>
>>>>>> > >> On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts wrote:
>>>>>> > >>
>>>>>> > >>> Carl you are exactly right and now that I think about it the
>>>>>> > >>> behavior
>>>>>> > >>> (sorta) makes sense. Thanks about the tip of the 'back' button
>>>>>> > >>> that does
>>>>>> > >>> seem to work (as a work around) but because the keyboard is
>>>>>> > >>> covering up
>>>>>> > >>> the
>>>>>> > >>> inputs under it it is not obvious that there are more inputs.
>>>>>> > >>>
>>>>>> > >>> I know Collect thinks its doing us a favor by popping up the
>>>>>> > >>> keyboard if
>>>>>> > >>> it sees only text inputs on a page but it would be better if it
>>>>>> > >>> didn't.
>>>>>> > >>> And
>>>>>> > >>> practically it doesn't save any time because it would pop it up
>>>>>> > >>> when you
>>>>>> > >>> select a text input box anyway. And if it wasn't there you would
>>>>>> > >>> see all
>>>>>> > >>> the
>>>>>> > >>> fields that it hides when it pops up. Is it possible to have a
>>>>>> > >>> 'hidden'
>>>>>> > >>> input box, for example a select input, that isn't visible (or
>>>>>> > >>> take space)
>>>>>> > >>> then the keyboard would not automatically pop up. (At least I've
>>>>>> > >>> found
>>>>>> > >>> where
>>>>>> > >>> I mix input flavors on a page it doesn't pop up.)
>>>>>> > >>>
>>>>>> > >>> -steve-
>>>>>> > >>>
>>>>>> > >>> On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung wrote:
>>>>>> > >>>
>>>>>> > >>>> Hey Steve,
>>>>>> > >>>> My guess is you've got 3 or 4 text inputs? The problem seems
>>>>>> > >>>> to be that
>>>>>> > >>>> you don't have enough inputs (text or other) to over-fill a
>>>>>> > >>>> screen so
>>>>>> > >>>> Android doesn't think it should scroll. Then, when one of the
>>>>>> > >>>> top
>>>>>> > >>>> inputs is
>>>>>> > >>>> selected the keyboard covers the bottom. If you have more
>>>>>> > >>>> inputs than
>>>>>> > >>>> fit
>>>>>> > >>>> on a screen, the scrolling still works above the keyboard.
>>>>>> > >>>>
>>>>>> > >>>> However, if you hit the 'back' button when the keyboard is up,
>>>>>> > >>>> the
>>>>>> > >>>> keyboard should get dismissed and reveal your hidden text
>>>>>> > >>>> inputs. Then
>>>>>> > >>>> you
>>>>>> > >>>> should be able to select the input and it will get moved above
>>>>>> > >>>> the
>>>>>> > >>>> soft-keyboard when it pops up. I tested both of the above with
>>>>>> > >>>> Swype on
>>>>>> > >>>> my
>>>>>> > >>>> phone and it worked as expected.
>>>>>> > >>>>
>>>>>> > >>>> I think I remember reading something about manually handling
>>>>>> > >>>> screen size
>>>>>> > >>>> changes (like when the keyboard pops ups), so I'll look into it
>>>>>> > >>>> and see
>>>>>> > >>>> if I
>>>>>> > >>>> can force enable the scrolling.
>>>>>> > >>>> -Carl
>>>>>> > >>>>
>>>>>> > >>>>
>>>>>> > >>>>
>>>>>> > >>>>
>>>>>> > >>>> On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts wrote:
>>>>>> > >>>>
>>>>>> > >>>>> I had no problem with 1.1.7 installing and the old forms
>>>>>> > >>>>> worked just
>>>>>> > >>>>> fine. However I am having problems with multiple text inputs
>>>>>> > >>>>> on one
>>>>>> > >>>>> page.
>>>>>> > >>>>> If I have more than 2 then I can't scroll down to the ones
>>>>>> > >>>>> covered by
>>>>>> > >>>>> the
>>>>>> > >>>>> (swype) on-screen keyboard. I can't dismiss the keyboard and
>>>>>> > >>>>> scroll
>>>>>> > >>>>> either. I do notice on other pages that have a mix of input
>>>>>> > >>>>> types it
>>>>>> > >>>>> doesn't seem to be a problem.
>>>>>> > >>>>> -steve-
>>>>>> > >>>>>
>>>>>> > >>>>> On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung wrote:
>>>>>> > >>>>>
>>>>>> > >>>>>> Hey Kirby,
>>>>>> > >>>>>> For Aggregate, you can install up to 10 instances on
>>>>>> > >>>>>> appengine or
>>>>>> > >>>>>> install it on your local machine. So yes, you can create
>>>>>> > >>>>>> another
>>>>>> > >>>>>> instance
>>>>>> > >>>>>> and operate it in parallel.
>>>>>> > >>>>>>
>>>>>> > >>>>>> For Collect, it will override your existing version. It
>>>>>> > >>>>>> won't delete
>>>>>> > >>>>>> your data, though. Your forms will be re-detected
>>>>>> > >>>>>> automatically.
>>>>>> > >>>>>> Your
>>>>>> > >>>>>> saved data will still be on the sdcard, but the new version
>>>>>> > >>>>>> won't be
>>>>>> > >>>>>> able to
>>>>>> > >>>>>> read it (from this version on, upgrading shouldn't cause this
>>>>>> > >>>>>> problem,
>>>>>> > >>>>>> though).
>>>>>> > >>>>>>
>>>>>> > >>>>>> I'll let Waylon or Mitch comment about the status of
>>>>>> > >>>>>> programatic
>>>>>> > >>>>>> access
>>>>>> > >>>>>> to aggregate data and the tool to migrate data from a .9x
>>>>>> > >>>>>> instance to
>>>>>> > >>>>>> a 1.0
>>>>>> > >>>>>> -Carl
>>>>>> > >>>>>>
>>>>>> > >>>>>>
>>>>>> > >>>>>>
>>>>>> > >>>>>> On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames wrote:
>>>>>> > >>>>>>
>>>>>> > >>>>>>> Carl,
>>>>>> > >>>>>>>
>>>>>> > >>>>>>> Thanks for the advice on 'new/updated' features.
>>>>>> > >>>>>>>
>>>>>> > >>>>>>> Another coupled of questions ...
>>>>>> > >>>>>>>
>>>>>> > >>>>>>> I've got an exsting Collect/Aggregate instance. Can I
>>>>>> > >>>>>>> install the
>>>>>> > >>>>>>> betas in parallel with my existing instances - or will they
>>>>>> > >>>>>>> over-write
>>>>>> > >>>>>>> my existing versions and data?
>>>>>> > >>>>>>>
>>>>>> > >>>>>>> I'd naturally like to try out the betas without compromising
>>>>>> > >>>>>>> existing
>>>>>> > >>>>>>> data (i.e. data I've collected already).
>>>>>> > >>>>>>>
>>>>>> > >>>>>>> I believe there was planned to be some migration tool - is
>>>>>> > >>>>>>> this
>>>>>> > >>>>>>> available?
>>>>>> > >>>>>>>
>>>>>> > >>>>>>> I understand there was planned to be a new method of
>>>>>> > >>>>>>> accessing data
>>>>>> > >>>>>>> held under Aggregate programatically - are details of this
>>>>>> > >>>>>>> interface
>>>>>> > >>>>>>> available?
>>>>>> > >>>>>>>
>>>>>> > >>>>>>> Many Thanks
>>>>>> > >>>>>>>
>>>>>> > >>>>>>>
>>>>>> > >>>>>>> Kirby
>>>>>> > >>>>>>>
>>>>>> > >>>>>>> --
>>>>>> > >>>>>>> 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
>>>>>> > >>>>>>
>>>>>> > >>>>>
>>>>>> > >>>>> --
>>>>>> > >>>>> 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
>>>>>> > >>>>
>>>>>> > >>>
>>>>>> > >>> --
>>>>>> > >>> 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
>>>>>> > >>
>>>>>> > >
>>>>>> > > --
>>>>>> > > 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
>>>>>> >
>>>>>> >
>>>>>> > --
>>>>>> > 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
>>>>>
>>>>> --
>>>>> 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
>>>
>>> --
>>> 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
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
I didn't have any problem before when Carl showed me how it was done. Hope I
can figure it out as saves a lot of clicks for a single form
-steve-
-- Painfully slowly typed on my htc EVO --
can't duplicate it on my phone, but sounds like a bug somewhere. i've
filed
it at http://code.google.com/p/opendatakit/issues/detail?id=264.
Hmmm. My Evo broke and I replaced it and am reinstalling my apps. I
just
installed 1.1.7 Beta 2. It works and my forms on my sd card seemed to all
be
happy. However I can't make a shortcut. I start odk, bring up the form
I
want, press home and bring up the short-cut list and odk is not on it. I
have the latest android update for 2.3.3. (I don't do this often. In
fact
have only done it for odk. Am I missing a step?) Thanks. -steve-
Sure thing. First, make sure that the form appears in ODK's list when
you
press 'start new form'.
Then:
press the phone's home button to get to your desktop/home screen ->
press-and-hold on any blank space until a menu appears -> shortcut ->
ODK
Form -> [whatever form you want]
hmmmm.. I'm having trouble figuring out what you mean. I assume the
form
you want the shortcut to needs to be open or selected or something.
Can you
give me a few more details on creating the shortcut?
-steve-
-- Painfully slowly typed on my htc EVO --
As another option, 1.1.7 will let you create a desktop shortcut to a
specific form. Just long press on the desktop to create a shortcut.
Using
the shortcut will start you in a specific form and saving/exiting will
take
you back to the desktop.
Yaw,
Thanks. That is helpful. Later today (After the UW graduation
I'll play with it.
As an editorial it does seem like it might be useful to have an
option
to submit the current form and start the next. (maybe a menu option)
I
suppose if walking between homes/huts between forms its not a big
deal to
start fresh for each entry but if you are sitting annotating fish
going
through a fish ladder you could be 'clicking' more clicks getting to
the
form than entering the data. (Big Fish, Small Fish)
(But as they say "beggars can't be choosers"
Thanks guys for all you do.
-steve-
steve,
yes. you can put questions inside a repeat and at the end of all the
questions, it will ask you if you want to create another repeat. say
yes,
and it will.
take a look at the household forms
(
http://code.google.com/p/opendatakit/source/browse/Household+Survey.xml?repo=forms#201
)
and you'll see a hopefully clear example of how repeats are used.
you can put default data in your repeats and also refer to data
within
the repeat. so if you enter a child's name in the repeat from the
form
above, you can use the text of that name when asking about that
child's
favorite color.
note that there is a jr:template tag that goes into the instance. if
you want the form to ask you at the beginning of the repeat about
creating a
new repeat, keep the template in. if you want to bypass that dialog,
remove
it. the template thing is confusing, but that's what we have to work
with.
anyway. best way to see this in action is to try it out.
yaw
Thanks Yaw,
I wasn't aware of 'repeats' and showing my ignorance when I (just
now) found the documentation (
http://code.dimagi.com/JavaRosa/wiki/xform)
and it is pretty much Greek to me.
It says:
"We also support the tag, which allows repeating a
question
or set of questions an arbitrary number of times. The nodeset
attribute of
the specifies the instance node to be parameterized --
that is, it
is this exact node (and all its children) which is duplicated each
time a
new repetition is created. Our implementation of is
pretty
standard, but it diverges in several ways.
In pure xforms, 'create new repetition' and 'delete repetition'
actions are initiated manually by the user, who does so using
special
controls created explicitly for this purpose. JavaRosa
provides
these actions automatically as part of the form entry UI. For
example, the
user will be prompted when necessary if they want to create a new
repetition, and when they are inside a , the 'delete'
option is
available under a menu. These s are unnecessary, and will
be
ignored if present."
I couldn't make heads or tails out of the examples. Does this
mean
that I could put the whole form in a 'repeat' and then somehow at
the end of
the form put a button or something asking if I wanted to repeat
the
questions then go back to the start if answered yes?
Thanks.
-steve-
steve,
the fix will be in the next beta release, so you'll have to wait
for
that. there is no way to loop back to the start of the next
instance.
you might look into repeats (or custom code) if you want that kind
of
functionality.
yaw
Carl,
Thanks for the quick response and fix. Does that mean I just
re-download
the beta and that fixes it?
Speaking of minimizing clicks... Is there a way that once a form
is "Save
Form and Exit" that it can loop back to the start of the next
instance of
that form. Otherwise you got to 'click' several times just to
get
to the
start of the form entry.
Thanks again.
-steve-
Hey Steve,
The behavior of Collect is to pop up a soft keyboard if a
textbox
is the
first or only input on a page. For all other widget types (as
the first
or
only) the keyboard is hidden. This was a highly requested
feature
originally when we only supported a single question per screen
to
minimize
'clicks'.
I just checked in a fix that makes the field scrollable when
the
soft-keyboard pops up automatically. Now it's the exact same
behavior as
a
screen with no text-inputs and too many elements to fit on the
screen.
That
is, it shows the scroll bar to indicate there are more fields.
-Carl
Carl you are exactly right and now that I think about it the
behavior
(sorta) makes sense. Thanks about the tip of the 'back' button
that does
seem to work (as a work around) but because the keyboard is
covering up
the
inputs under it it is not obvious that there are more inputs.
I know Collect thinks its doing us a favor by popping up the
keyboard if
it sees only text inputs on a page but it would be better if
it
didn't.
And
practically it doesn't save any time because it would pop it
up
when you
select a text input box anyway. And if it wasn't there you
would
see all
the
fields that it hides when it pops up. Is it possible to have
a
'hidden'
input box, for example a select input, that isn't visible (or
take space)
then the keyboard would not automatically pop up. (At least
I've
found
where
I mix input flavors on a page it doesn't pop up.)
-steve-
Hey Steve,
My guess is you've got 3 or 4 text inputs? The problem seems
to be that
you don't have enough inputs (text or other) to over-fill a
screen so
Android doesn't think it should scroll. Then, when one of
the
top
inputs is
selected the keyboard covers the bottom. If you have more
inputs than
fit
on a screen, the scrolling still works above the keyboard.
However, if you hit the 'back' button when the keyboard is
up,
the
keyboard should get dismissed and reveal your hidden text
inputs. Then
you
should be able to select the input and it will get moved
above
the
soft-keyboard when it pops up. I tested both of the above
with
Swype on
my
phone and it worked as expected.
I think I remember reading something about manually handling
screen size
changes (like when the keyboard pops ups), so I'll look into
it
and see
if I
can force enable the scrolling.
-Carl
I had no problem with 1.1.7 installing and the old forms
worked just
fine. However I am having problems with multiple text
inputs
on one
page.
If I have more than 2 then I can't scroll down to the ones
covered by
the
(swype) on-screen keyboard. I can't dismiss the keyboard
and
scroll
either. I do notice on other pages that have a mix of input
types it
doesn't seem to be a problem.
-steve-
Hey Kirby,
For Aggregate, you can install up to 10 instances on
appengine or
install it on your local machine. So yes, you can create
another
instance
and operate it in parallel.
For Collect, it will override your existing version. It
won't delete
your data, though. Your forms will be re-detected
automatically.
Your
saved data will still be on the sdcard, but the new version
won't be
able to
read it (from this version on, upgrading shouldn't cause
this
problem,
though).
I'll let Waylon or Mitch comment about the status of
programatic
access
to aggregate data and the tool to migrate data from a .9x
instance to
a 1.0
-Carl
Carl,
Thanks for the advice on 'new/updated' features.
Another coupled of questions ...
I've got an exsting Collect/Aggregate instance. Can I
install the
betas in parallel with my existing instances - or will
they
over-write
my existing versions and data?
I'd naturally like to try out the betas without
compromising
···
On Jul 16, 2011 1:34 PM, "Yaw Anokwa" wrote:
> On Sat, Jul 16, 2011 at 10:15, Steve Roberts wrote:
>> On Sat, Jun 11, 2011 at 11:46 AM, Carl Hartung wrote:
>>> On Sat, Jun 11, 2011 at 11:35 AM, Steve Roberts wrote:
>>>> On Sat, Jun 11, 2011 at 10:05 AM, Carl Hartung wrote:
>>>>> On Sat, Jun 11, 2011 at 8:50 AM, Steve Roberts wrote:
>>>>>> On Sat, Jun 11, 2011 at 8:30 AM, Yaw Anokwa wrote:
>>>>>>> On Jun 11, 2011, at 6:16 PM, Steve Roberts wrote:
>>>>>>> > On Sat, Jun 11, 2011 at 2:43 AM, Yaw Anokwa wrote:
>>>>>>> > On 06/10/2011, Steve Roberts wrote:
>>>>>>> > > On Fri, Jun 10, 2011 at 11:49 AM, Carl Hartung wrote:
>>>>>>> > >> On Wed, Jun 8, 2011 at 1:11 PM, Steve Roberts < steve@roberts.org> wrote:
>>>>>>> > >>> On Wed, Jun 8, 2011 at 12:52 PM, Carl Hartung wrote:
>>>>>>> > >>>> On Wed, Jun 8, 2011 at 11:13 AM, Steve Roberts wrote:
>>>>>>> > >>>>> On Wed, Jun 8, 2011 at 11:03 AM, Carl Hartung wrote:
>>>>>>> > >>>>>> On Wed, Jun 8, 2011 at 8:22 AM, KirbyJames wrote:
>>>>>>> > >>>>>>> existing
>>>>>>> > >>>>>>> data (i.e. data I've collected already).
>>>>>>> > >>>>>>>
>>>>>>> > >>>>>>> I believe there was planned to be some migration tool - is
>>>>>>> > >>>>>>> this
>>>>>>> > >>>>>>> available?
>>>>>>> > >>>>>>>
>>>>>>> > >>>>>>> I understand there was planned to be a new method of
>>>>>>> > >>>>>>> accessing data
>>>>>>> > >>>>>>> held under Aggregate programatically - are details of this
>>>>>>> > >>>>>>> interface
>>>>>>> > >>>>>>> available?
>>>>>>> > >>>>>>>
>>>>>>> > >>>>>>> Many Thanks
>>>>>>> > >>>>>>>
>>>>>>> > >>>>>>>
>>>>>>> > >>>>>>> Kirby
>>>>>>> > >>>>>>>
>>>>>>> > >>>>>>> --
>>>>>>> > >>>>>>> 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
>>>>>>> > >>>>>>
>>>>>>> > >>>>>
>>>>>>> > >>>>> --
>>>>>>> > >>>>> 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
>>>>>>> > >>>>
>>>>>>> > >>>
>>>>>>> > >>> --
>>>>>>> > >>> 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
>>>>>>> > >>
>>>>>>> > >
>>>>>>> > > --
>>>>>>> > > 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
>>>>>>> >
>>>>>>> >
>>>>>>> > --
>>>>>>> > 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
>>>>>>
>>>>>> --
>>>>>> 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
>>>>
>>>> --
>>>> 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
>>
>> --
>> 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