UGG!! I posted this response 6 days ago via my GMail account, Robert,
forgetting about the Base64 GMail issue. It seems it never made it
through to the other side!
On 2/5/07, Robert Koberg <rob@xxxxxxxxxx> wrote:
I think you are missing the point. It is not that it /can/ be done. It
is,
can it be done very *fast*. Native XPath over HTML usually is going to
be
the fastest.
Right, but is this available now? My point wasn't "Here's the answer...
Hooray! We can all go home now..." and instead "Oh, I see in the title of
the entry "CSS Query" -- Dean Edward's has one of those... I wonder if I
can fool Robert into believing that this is a native, cross-platform
tool. Let's find out..."
Apparently not. ;-) :D
So far the fastest cross browser seem to be the very new
dojo.query and this:
http://www.jackslocum.com/blog/2007/01/11/domquery-css-selector-basic-xpath-implementation-with-benchmarks/
Cool! Need to obviously read more than just the title of the entry this
next go round (as well as Jack Slocum's linked about.
Thanks for the info, Robert! And re: "Does anyone know if HTML XPath is
in the works for IE?"
Not a clue. There's the previous mentioned projects that would work if
WPF/e supports enough of the .NET FCL, but beyond this, not a clue.
That said, I've heard rumors that there's and alpha of IE.v.Next();
floating around, so it seems obvious that MSFT has no plans to let Moz/Fx
get even further ahead than they already are (Opera is so far ahead at the
moment, I doubt even IE.v.Next() + 1; will catch up, but shooting for the
stars is usually not the best approach, obviously ;) -- what this will
equate to, I'm not sure, but the fact they are actively pushing forward in
this space I believe suggests there's at least some hope that some of
these luxuries (such as E4X and XPath of HTML :D) will make it into the
mix.
--
/M:D
M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354