Beginning JavaScript with DOM Scripting and Ajax
If you want to learn about JavaScript from scratch—what it is, what to use it for, and how to make it work with other technologies like CSS and HTML—you have picked up the right book. If you already have a considerable amount of experience with JavaScript, but want to bring your knowledge up to d...
Đã lưu trong:
| Tác giả chính: | |
|---|---|
| Định dạng: | Sách |
| Ngôn ngữ: | English |
| Được phát hành: |
Apress
2012
|
| Những chủ đề: | |
| Truy cập trực tuyến: | https://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/30766 |
| Các nhãn: |
Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
|
| Thư viện lưu trữ: | Thư viện Trường Đại học Đà Lạt |
|---|
| id |
oai:scholar.dlu.edu.vn:DLU123456789-30766 |
|---|---|
| record_format |
dspace |
| spelling |
oai:scholar.dlu.edu.vn:DLU123456789-307662014-01-20T06:43:40Z Beginning JavaScript with DOM Scripting and Ajax Heilmann, Christian Technologies If you want to learn about JavaScript from scratch—what it is, what to use it for, and how to make it work with other technologies like CSS and HTML—you have picked up the right book. If you already have a considerable amount of experience with JavaScript, but want to bring your knowledge up to date, you have also picked up the right book—a lot has changed in JavaScript development in recent years. When JavaScript first started being used for web development back in the mid-to-late 1990s (it was first supported in Netscape 2, back in 1996), it quickly became much maligned, for many reasons—browser support was mediocre at best, and at worst, you actually had different JavaScript functions being implemented in different ways by different browsers (Netscape 4 and Internet Explorer 4 were major culprits, at the height of the so-called browser wars). This led to developers having to write completely different versions of web sites or indulge in messy code forking, if they wanted to attempt to have cross-browser support. And that was the consciencious ones—JavaScript’s bad reputation was just as much the fault of the developers as the browser manufacturers. Developers back in those days tended to use JavaScript for all manner of flashy effects that looked cool, but caused all manner of problems in terms of usability and accessibility (the days of DHTML—another marketing buzzword back in the day, which referred to the application of JavaScript, CSS, and HTML to produce dynamic effects). Pages would break completely if JavaScript was unavailable for any reason or if the user was trying to use a screenreader. And a lot of web developers would copy and paste scripts into their web sites without understanding how they actually worked, causing more untold usability and code maintenance nightmares. 2012-05-31T09:18:57Z 2012-05-31T09:18:57Z 2006 Book 1-59059-680-3 https://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/30766 en application/pdf Apress |
| institution |
Thư viện Trường Đại học Đà Lạt |
| collection |
Thư viện số |
| language |
English |
| topic |
Technologies |
| spellingShingle |
Technologies Heilmann, Christian Beginning JavaScript with DOM Scripting and Ajax |
| description |
If you want to learn about JavaScript from scratch—what it is, what to use it for, and how to
make it work with other technologies like CSS and HTML—you have picked up the right book.
If you already have a considerable amount of experience with JavaScript, but want to bring your
knowledge up to date, you have also picked up the right book—a lot has changed in JavaScript
development in recent years.
When JavaScript first started being used for web development back in the mid-to-late
1990s (it was first supported in Netscape 2, back in 1996), it quickly became much maligned, for
many reasons—browser support was mediocre at best, and at worst, you actually had different
JavaScript functions being implemented in different ways by different browsers (Netscape 4
and Internet Explorer 4 were major culprits, at the height of the so-called browser wars). This
led to developers having to write completely different versions of web sites or indulge in messy
code forking, if they wanted to attempt to have cross-browser support.
And that was the consciencious ones—JavaScript’s bad reputation was just as much the
fault of the developers as the browser manufacturers. Developers back in those days tended to
use JavaScript for all manner of flashy effects that looked cool, but caused all manner of problems
in terms of usability and accessibility (the days of DHTML—another marketing buzzword
back in the day, which referred to the application of JavaScript, CSS, and HTML to produce
dynamic effects). Pages would break completely if JavaScript was unavailable for any reason or
if the user was trying to use a screenreader. And a lot of web developers would copy and paste
scripts into their web sites without understanding how they actually worked, causing more
untold usability and code maintenance nightmares. |
| format |
Book |
| author |
Heilmann, Christian |
| author_facet |
Heilmann, Christian |
| author_sort |
Heilmann, Christian |
| title |
Beginning JavaScript with DOM Scripting and Ajax |
| title_short |
Beginning JavaScript with DOM Scripting and Ajax |
| title_full |
Beginning JavaScript with DOM Scripting and Ajax |
| title_fullStr |
Beginning JavaScript with DOM Scripting and Ajax |
| title_full_unstemmed |
Beginning JavaScript with DOM Scripting and Ajax |
| title_sort |
beginning javascript with dom scripting and ajax |
| publisher |
Apress |
| publishDate |
2012 |
| url |
https://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/30766 |
| _version_ |
1819767404500090880 |