PS: Neither www.packtub.com nor the link in your signature open in IE 6.0. They give a "Security Warning. Do you want to download the file?"
[ August 28, 2008: Message edited by: Shikhar Madhok ] [ August 28, 2008: Message edited by: Shikhar Madhok ]
He who asks a question is a fool for five minutes; he who does not ask a question remains a fool forever - Chinese proverb
I posted a sort of overview of the contents of the book in this topic, hope you find it interesting.
Target audience? Let me see.
Based on previous JS experience:
people new to JS can start from scratch and learn the language. The discussions of the very basics are not too lengthy, but the plethora of examples will hopefully both challenge beginners and give them material to experiment with. If you're totally new to JS it's going to be a great discovery working through the examples and trying out stuff
people with copy-paste JS experience or just scattered non-systematic JS knowledge will have a chance to properly learn/relearn the language and become much better front-end developers and Web 2.0 cool kids
experienced developers will benefit from the advanced topics: closures, prototypes, inheritance, patterns, privacy, lexical scope, namespaces, callbacks...
Based on OO experience:
people with no OO experience will be presented with the OO concepts in general and see how they apply to JS, also how JS may differ from the classical languages
people with classical OO experience (OO based on the concept of classes) will definitely find a whole new and interesting world full of prototypal and functional surprises and will become better programmers with a broader view of the craft
I mentioned somewhere in the other posts about job interviews. Those have been an inspiration for writing the book too. I hope people who read the book will ace their front-end interview when asked (happens every time) "is JS OO? How do you do inheritance?". Or "how does the prototype work". Or "write me something that accepts a callback function and traverses the DOM tree invoking the callback on every node". We've been moving towards more fat-client approach in the past 4(?) years and I think client-side skills are increasingly important for every web dev.