I 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...
Show HN: garlic.js - don't let your users lose their form data
21–30 of 109 posts
Re: Show HN: garlic.js - don't let your users lose their form data
#22Is 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
#23Good job!
Re: Show HN: garlic.js - don't let your users lose their form data
#24Is 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
#25Earlier quoted context omitted.
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 irresponsib…
Re: Show HN: garlic.js - don't let your users lose their form data
#26I 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'll definitely re-work on both the code and the doc. I've read that there is a kind of localStorage portage for IE8- that I'll look into.
Currently, if the browser does not support localStorage, the plugin auto-disable.
Best
Re: Show HN: garlic.js - don't let your users lose their form data
#27Re: Show HN: garlic.js - don't let your users lose their form data
#28I 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…
Re: Show HN: garlic.js - don't let your users lose their form data
#29Is 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
Keep you API open and flexible for the UX designer to choose what's best when. Also, if it's showing local data do something simple, like give the field a class of "garlic-data". That way the UX designer can choose the best way to differentiate it for their use case.