Hacker News new | comments | show | ask | jobs | submit login

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

I wonder if you should have some sort of icon or text indicator (per field) that shows there is saved form data available, but don't populate until the user triggers it, or an option to restore all available form data in one click? There are situations where I want to clear a form so I'll refresh the page if a clear option isn't available. I guess the solution would be for everyone that uses garlic.js to make sure they have a clear option.

There are all sorts of use cases that might want one thing over the next (display server data vs local data for example).

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.

Could you add a version number to your script for this reason? It'll also make diff'ing much easier.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact