I would be interested in seeing links to the bugs that you've filed (please feel free to link them in a reply to this post).
much more of the DOM is implemented in IE than it is in Mozilla
Unless you're referring to nonstandard MSIE extensions to the DOM, you're just plain wrong here.
Off the top of my head, I can think of some DOM modules that have been correctly implemented in Mozilla but are not available at all in MSIE :
DOM Level 2 Events
DOM Level 2 Range API
There are other aspects of the W3C DOM that are either unimplemented or misimplemented in recent versions of MSIE, but these two figure prominently for me (as I recently completed a project that used client-side JS and these DOM modules).
Every time that I have to work on a contract that includes some client-side development, I'm grateful for Mozilla's close adherence to the W3C Recommendations and loathe MSIE more and more for their consistently poor conformance and, often useless, extensions. In MSIE's nonstandard version of events, for example, one can get a handle on only the element node within which an event was fired (using the srcElement), but not on the actual text node.
Please, please check your facts before spreading outright falsehoods here.
I haven't downloaded it yet (I wasn't even aware that it existed until you mentioned it), but I found a download for a prefs toolbar at xulplanet. While I was looking for it, I also stumbled across David Illsley's useragent toolbar, which is pretty neat-o (and useful if you're tired of getting redirected by sites because you're using Moz or simply *not* using MSIE).
Thanks for the hint about the prefs toolbar. Otherwise I'd have never found it.
O'Reilly book vs Wrox book w/re to XPath
on
XML in a Nutshell
·
· Score: 1
I've had the Wrox book (Kay's "XSLT : Programmer's Reference") for a while and am reading the O'Reilly book now (literally, as in it's sitting here on my desk).
As chromatic said, the O'Reilly book includes a chapter on XPath and an XPath reference as an appendix, which is great. Additionally, XPath functions are covered (along with XSLT functions) in an "XSLT and XPath Functions Reference" appendix. While "XSLT : Programmer's Reference" is well-written and very useful (my copy is dog-eared), the absence of any separate discussion of XPath in Kay's book is, IMO, a significant flaw.
Kay tells readers near the outset that his book is written as though XSLT and XPath were one language. Since XPath acts as a sort of "sub-language" in an XSLT stylesheet, I can understand why he chose to cover the material in this way, but... I still would have preferred to see a separate introductory discussion of XPath somewhere near the beginning of the book. XPath isn't rocket science, but covering XPath concepts as they arise in examples muddles things quite a bit. If you've read pretty far into the book and are wondering how/why a given XPath expression was written in a certain way, you can't easily "flip back" to the section on XPath to answer your question because the information that you need is scattered throughout the book.
Right now, I'm about halfway through Tidwell's "XSLT" (the O'Reilly book). Based on my impressions so far, I would definitely recommend it. Back to my book.
Slashdot Mirror
I would be interested in seeing links to the bugs that you've filed (please feel free to link them in a reply to this post).
much more of the DOM is implemented in IE than it is in Mozilla
Unless you're referring to nonstandard MSIE extensions to the DOM, you're just plain wrong here.
Off the top of my head, I can think of some DOM modules that have been correctly implemented in Mozilla but are not available at all in MSIE :
There are other aspects of the W3C DOM that are either unimplemented or misimplemented in recent versions of MSIE, but these two figure prominently for me (as I recently completed a project that used client-side JS and these DOM modules).
Every time that I have to work on a contract that includes some client-side development, I'm grateful for Mozilla's close adherence to the W3C Recommendations and loathe MSIE more and more for their consistently poor conformance and, often useless, extensions. In MSIE's nonstandard version of events, for example, one can get a handle on only the element node within which an event was fired (using the srcElement), but not on the actual text node.
Please, please check your facts before spreading outright falsehoods here.
Speaking of database calls, why is there zero abstraction in PHP? why do I have to find and replace every function call to change databases.
Have you heard of Pear DB?
What is PEAR?
Good Luck.
There's an upcoming book, if you don't mind waiting a few months : "Creating Applications with Mozilla"
I haven't downloaded it yet (I wasn't even aware that it existed until you mentioned it), but I found a download for a prefs toolbar at xulplanet. While I was looking for it, I also stumbled across David Illsley's useragent toolbar, which is pretty neat-o (and useful if you're tired of getting redirected by sites because you're using Moz or simply *not* using MSIE). Thanks for the hint about the prefs toolbar. Otherwise I'd have never found it.
I've had the Wrox book (Kay's "XSLT : Programmer's Reference") for a while and am reading the O'Reilly book now (literally, as in it's sitting here on my desk).
... I still would have preferred to see a separate introductory discussion of XPath somewhere near the beginning of the book. XPath isn't rocket science, but covering XPath concepts as they arise in examples muddles things quite a bit. If you've read pretty far into the book and are wondering how/why a given XPath expression was written in a certain way, you can't easily "flip back" to the section on XPath to answer your question because the information that you need is scattered throughout the book.
As chromatic said, the O'Reilly book includes a chapter on XPath and an XPath reference as an appendix, which is great. Additionally, XPath functions are covered (along with XSLT functions) in an "XSLT and XPath Functions Reference" appendix. While "XSLT : Programmer's Reference" is well-written and very useful (my copy is dog-eared), the absence of any separate discussion of XPath in Kay's book is, IMO, a significant flaw.
Kay tells readers near the outset that his book is written as though XSLT and XPath were one language. Since XPath acts as a sort of "sub-language" in an XSLT stylesheet, I can understand why he chose to cover the material in this way, but
Right now, I'm about halfway through Tidwell's "XSLT" (the O'Reilly book). Based on my impressions so far, I would definitely recommend it. Back to my book.
Good link.
Thanks for posting this.