Fundamental JavaScript [In Control 2009]
by Aaron Gustafson on May 27, 2009
- 3,670 views
In this session, Aaron Gustafson introduces attendees to the client-side scripting language known as JavaScript. After being taken on a quick tour through the language’s features and syntax, atte
In this session, Aaron Gustafson introduces attendees to the client-side scripting language known as JavaScript. After being taken on a quick tour through the language’s features and syntax, attendees will be introduced through a series of examples to ways in which JavaScript can progressively enhance the user experience and really make their designs sing. This session also introduces attendees to several JavaScript libraries and demonstrate how to execute the same task in each.
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
Statistics
- Favorites
- 18
- Downloads
- 249
- Comments
- 0
- Embed Views
- Views on SlideShare
- 3,657
- Total Views
- 3,670




Graceful degradation would assume that my site should look roughly like this in all modern browsers and roughly like this [switch] in older browsers. It’s usable, but isn’t great. We can do better.
* some people drink a lot* some drink very littlewe need to anticipate and meet our customers’ needs in as seemless a way possible. They should never have to ask us for more water. That’s customer service.
Taking it a bit further...
We’ll touch on an example shortly.
Let me spin a yarn...
How many were doing JavaScript at the time? How many liked it? How many looked @ JavaScript and said “no way”?
I don’t blame you, it was spaghetti code. Code forking. Forked ourselves. Truth be told, however, our HTML was spaghetti too.
How many were doing JavaScript at the time? How many liked it? How many looked @ JavaScript and said “no way”?
I don’t blame you, it was spaghetti code. Code forking. Forked ourselves. Truth be told, however, our HTML was spaghetti too.
[slide] And there’s a balance there that PE helps with maintaining as it does put a focus on content.
[slide] And there’s a balance there that PE helps with maintaining as it does put a focus on content.
[slide] And there’s a balance there that PE helps with maintaining as it does put a focus on content.
Ajax is cool, but we should never lose sight of the fact that these are the two core technologies that drive the web. Without either, websites would cease to be.
Ajax is cool, but we should never lose sight of the fact that these are the two core technologies that drive the web. Without either, websites would cease to be.
Ajax is cool, but we should never lose sight of the fact that these are the two core technologies that drive the web. Without either, websites would cease to be.
This is one statement I always want you to keep in mind when you’re working with JavaScript. And here’s an example of why:
This is one statement I always want you to keep in mind when you’re working with JavaScript. And here’s an example of why:
Unfortunately you still see this all over the web... if I hear of any of you doing it, I will track you down.
I’d like you to think about your web work like the McDLT, where JavaScript and CSS are separated as much as humanly possible. Why? because it makes a lot of things easier.
I’d like you to think about your web work like the McDLT, where JavaScript and CSS are separated as much as humanly possible. Why? because it makes a lot of things easier.
I’d like you to think about your web work like the McDLT, where JavaScript and CSS are separated as much as humanly possible. Why? because it makes a lot of things easier.
That’s an accessibility issue
Your Javascript needs to be flexible to be maintainable. Just like the McDLT, JavaScript and CSS come together to create a tasty treat, but to be at their best, they need a little separation.
(Prototype has an element method like this)
Requires diligence in implementation to keep errors out.
Still requires implementation to be error-free.