search

thesentinelproject / threatwiki_node

Threatwiki - genocide risk tracking and visualization platform to help monitor communities at risk of genocide around the world
Other
63 stars 25 forks source link

Have a mechanism to be sure datapoint data is saved for the user if can't enter data in database due to a bug #35

Open jeromegv opened 12 years ago

jeromegv commented 11 years ago

I think this is a good user-friendly solution that we can implement easily: http://garlicjs.org/ I'm more afraid of them refreshing the page, leaving their browser or something like that, than an actual impossibility to save in the DB (they would most likely not be able to make it to the Create datapoint page if something was wrong with the DB). Let's wait a few weeks as it seems still very early stage in development

ghost commented 11 years ago

Awesome idea.

I haven't tested it yet, but the implementation sounds like a dream.

What would be uber-ideal, and perhaps something we could contribute to garlic.js would be a button overlay from it saying something like "export cache", which could allow a user to easily transfer their saved from the cache folder to their Desktop if they wanted.

Abhishek Bhatnagar

On Sat, Nov 10, 2012 at 5:18 PM, Jérôme Gagnon-Voyer < notifications@github.com> wrote:

I think this is a good user-friendly solution that we can implement easily: http://garlicjs.org/ I'm more afraid of them refreshing the page, leaving their browser or something like that, than an actual impossibility to save in the DB (they would most likely not be able to make it to the Create datapoint page if something was wrong with the DB). Let's wait a few weeks as it seems still very early stage in development

— Reply to this email directly or view it on GitHubhttps://github.com/thesentinelproject/threatwiki_node/issues/35#issuecomment-10262113.