Separate auto-fill from next button

[j-ro]

Would be great if the autofilling of information was separate from the next button in the bookmarklet. This would allow you to check your work and submit the form to see if you got an unexpected errors without having to start over if you do.

So, the workflow would look like:

1. go to form page, click bookmarklet, choose rep
2. choose form from dropdown in bookmarklet
3. choose fields matching with inputs in bookmarklet
4. click autofill in bookmarklet to autofill default values in form
5. click submit on the actual form to see if it goes through
6. if yes, click next on the bookmarklet (if no, fix your work and click autofill again to test until it does)
7. click next form (and repeat) or finished

[drinks]

I can look into holding the current set of steps in some sort of quarantine and committing them in a separate step, sounds doable. Do other folks agree this would be beneficial?—
Dan Drinkard

On Fri, Apr 11, 2014 at 11:57 AM, Jason Rosenbaum
[email protected] wrote:

Would be great if the autofilling of information was separate from the next button in the bookmarklet. This would allow you to check your work and submit the form to see if you got an unexpected errors without having to start over if you do.
So, the workflow would look like:

1. go to form page, click bookmarklet, choose rep
2. choose form from dropdown in bookmarklet
3. choose fields matching with inputs in bookmarklet
4. click autofill in bookmarklet to autofill default values in form
5. click submit on the actual form to see if it goes through
6. if yes, click next on the bookmarklet (if no, fix your work and click autofill again to test until it does)

7. click next form (and repeat) or finished

Reply to this email directly or view it on GitHub:
#618

[gcosta]

Yes, sometimes I missed a single required field and had to start all over
again.

On Fri, Apr 11, 2014 at 1:08 PM, Dan Drinkard [email protected]:

I can look into holding the current set of steps in some sort of
quarantine and committing them in a separate step, sounds doable. Do other
folks agree this would be beneficial?--
Dan Drinkard

On Fri, Apr 11, 2014 at 11:57 AM, Jason Rosenbaum
[email protected] wrote:

Would be great if the autofilling of information was separate from the
next button in the bookmarklet. This would allow you to check your work and
submit the form to see if you got an unexpected errors without having to
start over if you do.
So, the workflow would look like:

1. go to form page, click bookmarklet, choose rep
2. choose form from dropdown in bookmarklet
3. choose fields matching with inputs in bookmarklet
4. click autofill in bookmarklet to autofill default values in form
5. click submit on the actual form to see if it goes through
6. if yes, click next on the bookmarklet (if no, fix your work and click
   autofill again to test until it does)

7. click next form (and repeat) or finished

Reply to this email directly or view it on GitHub:
#618

Reply to this email directly or view it on GitHubhttps://github.com//issues/618#issuecomment-40220762
.

[j-ro]

@drinks -- quarantine sounds good, though the way I proposed, you might not even need that, right? As in, the autofill will make the yaml and fill with defaults, and if the user presses autofill again, it makes new yaml to replace the old and fills. So no real extra memory needed, just a bit of rejiggering of the buttons.

Of course, a real working back/forward feature set would be great, but we can probably get away with something easier.

[contactcongress]

Well, the quarantine has to do with the actual implementation. Each form generates an arbitrary number of instructions so there's no real way to go back a step; as it could mean 10 steps or 2 in the corresponding json/yaml data.—
Dan Drinkard

On Fri, Apr 11, 2014 at 1:27 PM, Jason Rosenbaum [email protected]
wrote:

@drinks -- quarantine sounds good, though the way I proposed, you might not even need that, right? As in, the autofill will make the yaml and fill with defaults, and if the user presses autofill again, it makes new yaml to replace the old and fills. So no real extra memory needed, just a bit of rejiggering of the buttons.

Of course, a real working back/forward feature set would be great, but we can probably get away with something easier.

Reply to this email directly or view it on GitHub:
#618 (comment)

[j-ro]

ah, yeah, I see what you mean -- quarantine it is!