|
|
20 of 21 people found the following review helpful:
2.0 out of 5 stars
Extremely frustrating, like most Mozilla documentation, December 3, 2002
It's doubtful that, on its own, Creating Applications with Mozilla would enable a developer -- even with a reasonable knowledge of JavaScript, HTML, CSS and C++ -- to do anything interesting with Mozilla. It certainly won't teach you how to create templates, package applications, or even use JSLib (which should be simple!), let alone write XBL or manipulate RDF files.To be realistic, however, this book is often more handy than using Mozilla documentation online, and it has the usual high quality O'Reilly binding, paper, type design and layout. Buy it if someone else is paying or if you do a lot of Mozilla programming. In a nutshell, the main problems I had with the book are as follows. 1. Technical writing should be judged in adversity -- how well it handles the hard stuff -- and on that count, this book fails miserably. When the going gets tough, the explanations become impenetrable and seem to be "preaching to the choir", assuming a deep knowledge of Mozilla programming. Even relatively simple concepts,such as the chrome URL, are poorly explained, and much of the sample code and technical reference material is, unnecessarily complex. 2. Much of the material is limited and incomplete: there are odd gaps in explanations, unenlightening overview sections (such as the description of using Perl with Mozilla), methods and properties listed with limited information (or no information) about their implementation, and incomplete references (such as the list of Mozilla CSS extensions). Crucial information (you can't manipulate datasources unless working via a chrome URL, for example) is often missing or buried. 3.There are numerous typos: misspellings, incorrect punctuation and errors in illustrations (at least three in figure 7-2 on page 181). 4. Code samples have errors and inconsistencies. 5. Much of the code and reference material is out of date (and was obsolete even before the print version was published). 6. The code examples are unfocused (there's too much emphasis on context) and don't always work (and didn't work online). 7. The index is often unhelpful and incomplete, without good conceptual indexing. Mozilla programming is highly promising and, for the most part, not all that difficult once you know how, but finding accurate information about it is a tantalising process of trial and error. You have to rely on guesswork, intuition, word of mouth, limited or obsolete and inaccurate documentation, and the help of a very few (though extremely helpful) insiders available via the Mozilla newsgroups. Given that the project has been around for a few years now, I think that's unacceptable: I'd hate to see Mozilla wind up as a good technology that died for lack of decent documentation.
|