Front End Development Guidelines
taitems.tumblr.com
Front End Development Guidelines
1–10 of 51 posts
Re: Front End Development Guidelines
#2Re: Front End Development Guidelines
#3Re: Front End Development Guidelines
#4Re: Front End Development Guidelines
#5Why do you believe camelCaseIsBetter and more readable then using_underscores_in_variables ? While you're entitled to your opinion, calling one "good" and the other "bad" is a bit overboard.
Re: Front End Development Guidelines
#6Why do you believe camelCaseIsBetter and more readable then using_underscores_in_variables ? While you're entitled to your opinion, calling one "good" and the other "bad" is a bit overboard.
EDIT: The other response is more accurate.
Re: Front End Development Guidelines
#7Why do you believe camelCaseIsBetter and more readable then using_underscores_in_variables ? While you're entitled to your opinion, calling one "good" and the other "bad" is a bit overboard.
Re: Front End Development Guidelines
#8This example snippet actually generates a Javascript error (at least, in IE9):
var foo = null;
// foo is null, but bar is undefined as it has not been declared
if (foo == null && bar == null) {
// still got in here
}
It will work if bar is declared but has value undefined, but not if bar is completely undeclared as shown.Re: Front End Development Guidelines
#91. This is the web. Users will resize the window, copy and paste, click a button five times, turn off JavaScript, and arrive from every possible combination of browser, operating system, and language. You will maintain an appropriate fear of any trick so complicated that you don't know what it will do under all of those circumstances.
2. The user is always right. Even when they run unpatched IE7 with JavaScript and CSS on but images hidden.
Then a few pointers I would like to add:
- Think twice before binding to every instance of an event. Are you looking for a keydown, a mouse move, or a scroll? Throttle your function to make sure it runs only ten times a second, or whatever is appropriate. Ironically, the faster browsers and JS environments become, the slower your pages will be if you calculate something on all 1000 scroll events per second.
- For heaven's sake try to avoid absolutely positioning your whole interface. But if you do, you better try it in every browser and resize it real fast to see if it works.
Re: Front End Development Guidelines
#10A deep link for those that want to skip my pre-amble: http://taitems.github.com/Front-End-Development-Guidelines/
THIS is why I hang out here. :) Kudos..