Should be called: JavaScript (& a chapter on AJAX)
This is my first QSG book. I assume the layout is "feature" of the series, if so this will be my last.
Bottom line first: the title is a lie, this is a book about javascript with a chapter on AJAX; this book has good content, but the presentation will drive you insane while you read it.
Layout:
The book has a good concept but doesn't execute it well. Each page is divided into two columns, the example code is in one column, the text describing that code is in the other. This really is a great concept. It's used in analytic copies of a number of Shakespeare's plays and works well there. It works because they are conscientious about pagination, include line references, and use facing pages not columns.
Columns are a problem because each line has about three words before wrapping. The dot syntax of javascript is particularly hard to read with such short lines.
The pagination / line reference is really the biggest problem in the QSG's execution. They let the text and code flow through the columns across pages without much attention. This means you are constantly flipping forwards and backwards to see the code as you read. Without line references the flipping is not just annoying it's really more of a search.
They make two attempts to address the pagination problem: first, the code being talked about is highlighted in red; second, they reprint the code block being talked about in the text column. Neither of these is helpful. Half of the code ends up being highlighted red - at most you can scan the red blocks to figure out what that code is an example of, and what is just there to support the example. If they are going to reprint the code anyway why not just go over to a normal layout? My suggestion: use facing pages for the next edition!
AJAX:
This is not a book on AJAX. This is an introduction to javascript that includes a buzz word in its title to jump off the shelf at people. It's not even an introduction to javascript from an AJAX prospective. In fact AJAX isn't covered well in the book. For example there is very little discussion of how to navigate returned XML using javascript. AJAX is mentioned in the intro and then 'taught' in chapters 15 and 16. (Chapter 16 is just a discussion of available libraries!) You can't give AJAX top billing and then devote 10% of the actual book to it.
So why 2 stars?
I was looking for a book that assumed very little or no knowledge of javascript. I was hoping for something that would address canonical javascripting, best practices, and a bit theory behind the topics being covered. I'm self taught and wanted to see how things should be done instead of how they can be done. This book would be a darn good intro for a beginner. The theory and best practices parts were not explicitly addressed as often as I would have liked; however, they were demonstrated and covered at times.
4 star content, less 1 for layout, less 1 for title.
JavaScript & AJAX
The book arrived quickly. I is new quality. I intend to increase my knowledge of DOM, JavaScrip anf AJAX.
Interesting collection of examples, not good for learning
I've been learning JavaScript off and on, with some success, for three months. In doing so, I've skimmed about a half-dozen books and tried the following three, so far, "graded" below:
Learning JavaScript (Powers B-)
VQS JavaScript and Ajax (Negrino & Smith C+)
O'Reilly JavaScript Pocket Reference (Flanagan B)
It's hard to find good books on this because the subject matter is new and the books are often dashed off quickly. VQS JavaScript and Ajax is essentially a collection of well-explained examples of well-organized code. It's written more to fill pages than flesh out the subject, however. The explanations are unnecessarily wordy and the broader coverage of concepts, context and how to, you would want to include in a teaching book are missing.
Strangest of all perhaps is the author's choice of leaving out how html talks to Javascript or the details of how they link. Since JavaScript's purpose is to interact with html and pass things back and forth, it's sort of like doing marriage counseling and only focusing on what the woman's thinking to herself. Unfortunately, they're not the only authors that make this oversight.
The VQS format is great and they do a good job of using color to highlight the portions of code they're referring to. The is a good, annotated collection of code examples. It's something I've found to be only marginally helpful in getting started.
All Examples - Not too Much Explanation
I'm an experienced procedural php, xhtml and css developer with litter foundational knowledge about javascript. I purchased this book to fill that gap and was a little disappointed. It's not a bad book but it assumes a lot and has little instructional flow. The book scrolls though one example after another without much explanation for the actual language constructs behind javascript.
The author states that this book is not for beginners and I don't consider myself to be one, however, I'd advise anyone looking to buy this book to have a solid understanding of object oriented programming principals before they do so.
Overall it's not a bad book for a certain audience but it lacks foundational, and in my opinion vital, information about javascript.
Not the best learning tool
This book gives some nice examples of usable code for a few common uses but doesnt give a very good explanation of what is being done and why. if you have great programming experience and a excellent knowledge of the DOM this book would be good way to get some javascript going, but for the average person looking to learn how javascript works and apply it in other ways than those shown in the book you are better off elsewhere.
(17 reviews)
