31–40 of 109 posts
> 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.
I 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.
1.1 Markdown 1.1.1 http:// attacklab.net/showdown/
1.2 DBs 1.2.1 http://jazzrecord.org
1.3 Unit tests 1.3.1 http://jsunittest.com/
1.4 Documentation 1.4.1 http://www.naturaldocs.org/ 1.4.2 http://fitzgen.github.com/pycco/
1.5 Visual 1.5.1 http://lab.hakim.se/kort/
1.6 localStorage 1.6.1 Redis inspired, at twilio https://github.com/twilio/BankersBox 1.6.2 Amplify.store http://amplifyjs.com/api/store/ 1.6.3 Persistent form data http://guillaumepotier.github.com/Garlic.js/
I'll probably end up posting the list (or the mind map that forms it) on my blog sooner or later (probably as soon as I hit 30 or when I finish my current Javascript RTE project)
Just a heads up, the of your page is still "Bootstrap".
You passed.
Don't want to be that guy, but what's different from http://simsalabim.github.com/sisyphus/ ?
> 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.
> 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.
Earlier quoted context omitted.
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.
And there's your answer: The "cost" of depending on jQuery is small since so many things depend on it that most potential users probably already pull it in.
Earlier quoted context omitted.
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.
The source is here:
https://github.com/guillaumepotier/Garlic.js/blob/master/gar...
The code is pretty much idiomatic jQuery js following most of their style rules, layout rules and standard constructs so it's obviously been written as a jQuery extension. He must know jQuery well, hence why not use it?
As for why, well I spotted a bit of sizzle, jQuery.data and the event framework in one pass of a small code base. Given the nature of the library I can even guess what they're all for without reading the code.
Quite a lot more than the inevitable each that is also in there.
Earlier quoted context omitted.
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.
Don't want to be that guy, but what's different from http://simsalabim.github.com/sisyphus/ ?