#31 more functional local submit page

[Gordon Mohr]

The temporary local page constructed to submit data,
which when all works properly immediately does a
web-form submit, could be improved in a number of ways:

- better explain/display what's being submitted
- offer 'inline'/javascript pre-lookup: preview of
whether it'll be new submission
- offer 'lookup only' option
- offer 'force anonymous' option
- offer auto-submit/hold-for-submit-click toggle
- each of the above can be a persistent choice using
local cookies

maybe even:
- have edittable fields, where appropriate
- have option to express confidence in extracted values
- have option to choose between existing website values
and local values
- have rating/comment/tag areas

[Gordon Mohr]

Logged In: YES
user_id=144912

Or even: the page comes from our server, then merges the
local data in, so we can continually update capabilities.

For example, submit could send to
"http://bitzi.com/submit#PATH_TO_LOCAL_JSON". Since PATH is
in URI fragment, it's not sent over wire. Submit page
returned would include local JSON for display/review/edit/etc.

Or even, for the paranoid who don't want to take the chance
our server-side path will take their local path/metadata
without explicit permission, initial send could be to
bare-bones local filesystem submit page:

"file:C:\\tmp\\submit_generic.html#PATH_TO_JSON"

OR "file:\\tmp\\submit_custom.html"

Only if the user chooses to 'upgrade' to server-side version
-- a preference that could remain sticky via a local cookie
-- does the merge-into-server-provided-page occur.