Thanks for your first comments ;) This is a very very early alpha release. 1h of work in fact.. Please, feel free to contribute!
Show HN: garlic.js - don't let your users lose their form data
11–20 of 109 posts
Re: Show HN: garlic.js - don't let your users lose their form data
#12Is there a way to differentiate between data that's only saved using Garlic (local) vs data that's also been saved to the server? This could be a huge confusion for users if there isn't.
Yes, I'll need to work on that, if there is already server data. Maybe in a tooltip like, let the user choose which version he should use
Re: Show HN: garlic.js - don't let your users lose their form data
#13Huh, this is very nice. Congratulations!
Thanks :)
Re: Show HN: garlic.js - don't let your users lose their form data
#14Is there a way to differentiate between data that's only saved using Garlic (local) vs data that's also been saved to the server? This could be a huge confusion for users if there isn't.
I agree with this. Outside of explicitly signaling to users that they have a saved 'draft' of the form, and having them click a button on the page to restore their filled out fields from the draft, there aren't really very many sane implementations.
Some other issues: - doesn't work in IE - saved data doesn't expire - Storage keys aren't unique to the URL, so if two pages have the same exact layout, but different content, identical forms on the page will be filled out with stored information.
So it's a good concept, but I think that there are definitely some questions about user privacy, and that it needs to be paired with some extra UI cues that make it clear to the user that they're looking at draft information, and not something that's saved.
Re: Show HN: garlic.js - don't let your users lose their form data
#15I think the desire for this kind of project is very reasonably based, and it looks like you have done great work on most of the implementation. I have one gripe with it, though. It would be nice if the documentation mentioned that garlic.js requires an HTML5 browser with localStorage implemented. Remember, there are people who are still using Internet Explorer 6 and 7, and these browsers are incompatible [1]. This is…
For all intents and purposes, IE6 and IE7 are dead. They account for less than 1.5% of worldwide browsers [1]. At this point, seems okay to leave out.
[1] http://gs.statcounter.com/#browser_version_partially_combine...
Re: Show HN: garlic.js - don't let your users lose their form data
#16I just hope everyone gets to use it. I added it to my "great to have" Javascript libraries list. Good work!
Ruben, can you please share your "great to have" Javascript libraries list? It sounds promising.
Re: Show HN: garlic.js - don't let your users lose their form data
#17I think the desire for this kind of project is very reasonably based, and it looks like you have done great work on most of the implementation. I have one gripe with it, though. It would be nice if the documentation mentioned that garlic.js requires an HTML5 browser with localStorage implemented. Remember, there are people who are still using Internet Explorer 6 and 7, and these browsers are incompatible [1]. This is…
I disagree to a certain extent. I don't believe in catering to the possible 5% [1] market share that will not upgrade their browsers. Anything that strongly suggests people to upgrade is better, imo. I don't care for the entire notion of including everybody when it calls for more code bloat and makes the code more difficult to maintain or upgrade.
Re: Show HN: garlic.js - don't let your users lose their form data
#18I think the desire for this kind of project is very reasonably based, and it looks like you have done great work on most of the implementation. I have one gripe with it, though. It would be nice if the documentation mentioned that garlic.js requires an HTML5 browser with localStorage implemented. Remember, there are people who are still using Internet Explorer 6 and 7, and these browsers are incompatible [1]. This is…
For all intents and purposes, IE6 and IE7 are dead. They account for less than 1.5% of worldwide browsers [1]. At this point, seems okay to leave out. [1] http://gs.statcounter.com/#browser_version_partially_combine...
One of the sites I built recently has a ton of backbone.js dynamic loading.
I tried to test it in IE 6, and the browser just immediately crashes. Not like an alert box, just an instant shut down!
In the past I would have started the unpleasant task of figuring that out and fixing it up, or perhaps detecting and redirecting to a more lightweight page.
This time I said screw it - I'm done with IE 6! Call me irresponsible or lazy or whatever you want but I'm just done with IE 6 and it feels great!
By the way YouTube shows a giant warning on their page if you view it with IE 6, saying that it won't be supported in 6 months.
Re: Show HN: garlic.js - don't let your users lose their form data
#19I think the desire for this kind of project is very reasonably based, and it looks like you have done great work on most of the implementation. I have one gripe with it, though. It would be nice if the documentation mentioned that garlic.js requires an HTML5 browser with localStorage implemented. Remember, there are people who are still using Internet Explorer 6 and 7, and these browsers are incompatible [1]. This is…
It would also be nice if the documentation mentioned that it requires jQuery.
Hmm, what does jQuery provide that is so essential that someone decides to add a dependency this big for something so simple? It seems that everything requires jQuery these days, even when a 5-line for loop would do.
Re: Show HN: garlic.js - don't let your users lose their form data
#20> don't let your users lose their form data This is a huge problem, and is the reason I've had Lazarus installed for a few years now. https://addons.mozilla.org/en-us/firefox/addon/lazarus-form-... Apparently it exists for Chrome now, too.
Thinking about it, I'm mildly amazed that the browsers themselves didn't solve this problem back in 1996 or so.