Slashdot Mirror
Dynamic HTML: The Definitive Reference (2nd Ed.)
Goodman has tackled a complex subject. With changing standards and even quicker changing browser compatibility it can be a nightmare trying to get a dynamic web site working across disparate browsers and operating systems. A guide that tells you exact syntax and exact compatibility can be invaluable, but is only as good as the research behind it, an area where I cannot fault Goodman.
This volume covers XHTML, CSS and DOM with a large smidgeon of JavaScript. It's not an easy book to get into and consume in large chunks as it does little hand holding but as I was prepared to knuckle down and work at the topics (with much help from various web sites such as CSS Zen Garden) I found it perfect for me. Goodman has recently released JavaScript & DHTML Cookbook which I have found to be a marvelous volume to assist the process of understanding these technologies, though I am still looking for a good, up to date tutorial on CSS (recommendations welcome).
The target audience would be best summed up as those who have done a fair amount of HTML hand coding and some work in dynamic HTML. The book also adds that you should have "the basics of client-side scripting in JavaScript" and I would agree, when I first acquired this book my JavaScript skills were exceptionally primitive (mainly at the 'plug in example' stage) and found the latter sections of this book heavy going and not much help; now that I am a better JavaScript programmer I find these parts much easier to understand and use.
The book is divided into four parts, 'Applying Dynamic HTML,' 'Dynamic HTML Reference,' 'Cross References,' and 'Appendixes'. I found the first part particularly helpful when converting my old site across to a more dynamic CSS-based site as it helps with various strategies for making sure your content works across browsers and various methods for making sure that visitors with older browsers and search engines can still retrieve valid pages. Goodman's approach of increasing complexity through this part also suited a movement from a straight HTML site to one using XHTML and CSS. This is also where Goodman's writing can shine: it's an excellent guide to all the technologies and acronym soup. The appendices are marvelous, from 'A,' a list of colour names with their RGB value, through a list of character entities to a 50-page list of all HTML tags, their attributes and if they are supported in the two HTML 4 and three XHTML 1 standards.
The reference parts are well structured with extensive notes on browser support and which particular standard (DOM 1, DOM 2, CSS 1, CSS 2, or none) the tag or attribute comes from. For example, in the DOM section the reference gives you the object name, which versions of Navigator and Explorer support it, the DOM version (if any), a short explanation, then an object reference example, list of properties, methods and event handlers. For each of the properties it gives an example, the type and if it is read-only or read/write. For methods it gives the return value and parameters. This sort of attention to fine detail is taken throughout the book. You end up with a book 1343 pages long and a 51 page index. Goodman mentions in his preface that the book now encompasses 'more than 15,000 unique instances of properties, methods and event handlers,' a figure I'd believe.
O'Reilly have their usual page for this book that includes a sample chapter in PDF, the Index, Table of Contents and an Errata page. There are few Errata and only one in the code examples. Speaking of examples, you can download the complete set of code examples from the book.
There is also a page at O'Reilly for the author, Danny Goodman with links to some excellent articles and book excerpts on dynamic HTML and JavaScript.I found this a hard book to review, as are most references. The questions I asked were: one, Does the book cover all the material?; two, Is it correct?; three, Is it easy to find the entry you want? and four, Are the entries laid out in an easy to understand manner? In these criteria this volume rates well, with the added bonus of some good material in the first section for understanding the nuances of dynamic HTML in a multiple browser, multiple operating system world.
If you are doing a lot of work in dynamic HTML then this book is probably an essential. While I don't consult it every time I start working on HTML when I run into trouble it is the first place I turn to make sure my syntax and browser compatibility are straight. This book ain't cheap, and it ain't small but I'd recommend it for your desk if you're working with web sites.
You can purchase the Dynamic HTML: The Definitive Reference (2nd Ed.) from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
This one is a great addition to the book shelf,, you all know how to do certain things in HTML/DHTML but this book clarifies nicely why you are actually doing it. Also, it introduces nice DOM concepts which WYSIWYG web designers might not have come across before
There is no god
When will Opera actually support the meatier parts of DHTML?
A year ago. The more important question is when MSIE will do the same. My new site currently looks like shit in MSIE even though I even made a separate CSS that did widths differently and forced alpha transparency on the logo.
Is this a sigs-optional kind of place? 'Cause I am totally down with that if you know what I mean.
My first one is all dog-eared and out of date, but it still sits on my shelf and I occasionally refer back to it. Great book for learning and as a reference.
Sadly, the only book I ever use these days is the Dynamic HTML Reference and SDK from Micro$oft (basically the same info you can get for free from msdn). If you're only supporting IE and just need a quick reference, that book is the bomb. Oh, am I not supposed to use the word bomb anymore? It is the bawm.
I don't have a signature.
IMO "Dynamic HTML" is a vague term which is usually used by people who do not know about the subject. However, not letting that put me off, I think that this book might be useful to a professional web hacker; although they might be better off with the individual O'Reilly books on the different subjects (e.g.: DOM, CSS, HTML, XHTML, ECMAScript) (or just tree-killed standards (while learning techniques by example on the good ol' WWW or in tutorials) for those of us that can understand standards &c or cannot afford the books).
I looked at the first edition of this book in a shop and considered buying it, but decided against it due to its high price, the fact that I did not like the style (unlike most of the publisher's books which are IMO written excelently), and, mainly, my conclusion that HTML & XHTML: The Definitive Guide would be best for everyday design (as it has a little on other technologies (which are secondary to (X)HTML itself), and I can find about the details of these when I need them), though I'm not a professional.
I bought HTML & XHTML: The Defintive Guide, 5th Ed and it was a good read (as O'Reilly books always are), although I was a little dissapointed with a few aspects: quite a few mistakes (not just typos or such like, but the authors not actually understanding (X)HTML and giving false information in contradiction to the W3C standards), the attitude the authors took of saying "you should do foo but here is how to do bar instead", and the lack of many real-world tips, tricks and tutorials (the kind of stuff that you cannot get from the W3C). However, I found that much of the content (like extensions to HTML, browsers and history) was useful to some extent. The HTML & XHTML book is probably a good book for non-professionals and those who do not want to shell out for Dynamic HTML: The Definitive Reference , but still want a book. Maybe, there is an argument that to learn something well, it is best not using a book.
I am considering buying the CSS guide (and just bought XML in a Nutshell which is very comprehensive (yet reasonably concise) and well written so I it recommend highly).
Joe Llywelyn Griffith Blakesley
[This post is in the public domain (copyright-free) unless otherwise stated]
... the 2nd edition is about twice the size as the old ones.
:/
.NET or J2EE, when all they really need is good 'ol CGI with a bell or a whistle here and there. I've seen trival applications being run on big-ass servers with Oracle, WebLogic, etc. out the wazoo, when only 0.005% of their capabilities are utilized. Additionally, even with all those CPUs and gigabytes of RAM, the application performance is terrible. I've also found it quite ironic that gigabytes of software are being installed and configured to run an application that is only a few tens of thousands of lines of code with a database of 50 objects.
Whatever happened to the WWW simplifying things?
The complexity of software development is certainly no less than it was ten or fifteen years ago...I think it has actually gone up significantly. The addition of hundreds of new buzzwords and embryonic toolsets has not helped at all.
In many cases, customers or managers strive for gigamegagigantic things like
Sigh.
Healthcare article at Kuro5hin
There is usually no direct connection between a topic and the animal the O'reilly folks put on the cover. If you look at the old "Ask Tim" articles you will find that somewhere he explains where the animal covers come from.
The basics of it is that 20 years ago for their first round of books they hired a designer who didn't know unix and she decided that "sed and awk" sounded like two birds. So she made a few covers in the style that they have been using ever since.
Erlang Developer and podcaster
We've pretty much given up on DHTML-driven apps - they are too hard to modify and maintain. Use some Javascript to do some form validation and light stuff like that, but at some point you really are better off just repainting the darn screen instead of delving into DOM madness trying to hide table rows and the like. Being a Microsoft shop, we've pushed hard to move to using .NET web forms, and we've been able to forget that we are writing for web browsers. =)
They're still errors. As for the tonne of errors, you get this in programming langauges too when one line causes the compiler to go out of whack and start flagging other lines as errors erronously. However it's still not much of an excuse to say "Hey, it's only one line causing the problem and it still compiles" when the compiler dumps 200k's worth of warnings to your terminal.
And lastly, you can't expect full compliance at all times from a page that sources HTML from elsewhere, such as advertisements which require ads be run without any modification to the markup provided, or contain other content that hasn't been vetted for compliance like story submissions.
Most advert code is standards complient because there isn't much to it. The story submissions at the most contain the A tag and possibly B and I'm at a loss to think of other tags which would be needed. Granted, it would be a difficult task to make the comments section validate because people can write comments in HTML.
But still, for a geek site that pushes for adherance of standard and open protocols and file formats (PNG over GIF, of which there are no PNG's on the front page at all - but a tonne of GIF's) it is a pretty poor show.
Avantslash - View Slashdot cleanly on your mobile phone.
Does it have an object->CSS cross reference yet? Although I use the 1st edition a lot, it lacks a way of quickly checking which css styles an element supports in which browsers.