Thanks, everyone, for your comments on generating xpaths. I now have preliminary module owner's approval from peterv to implement XPathGenerator in mozilla.org code. (I'll go to him for review as a condition of moa.)
Almost two years ago, I wrote a whimsical article about how not to add code to the tree. (I believe that was for serverpost.) This time, I think I'm following the right path, including an open API, and keeping other developers (sicking, mixedpuppy, timeless) specifically informed.
This also, by the way, marks two significant milestones for me. First, it is the first time I'll be writing a component for mozilla.org native code from scratch. I've filed patches before, many times. I've started spinoff projects a few times too. This time, it's going straight in to the core. That's a good feeling. Second, it's the first time I'll be attempting to write a XPCOM component in C++. As a JavaScript guy, that's going to be a test, but I won't fail it. I'll just keep trying until I get it right.
UPDATE: I need test cases! Please send me some. I'll pick the clearest and most comprehensive, and add them to the bug. (No, I'm not nearly ready to run the tests; I just need something to compare my results against.)
Posted by WeirdAl at January 19, 2006 3:37 PM