Moving Mechanize to Nokogiri

ruby-talk
1

Hey guys,
I'm on the second iteration of an app I'm writing to scrape some data
from iStock and right now, I'm trying to force Mechanize to use
Nokogiri. I've gotten away with not having to for a while, but as I keep
adding to this app, it's inevitable.

This is what I thought worked (http://pastie.org/393471); namely, drop
the WWW::Mechanize.html_parser = Nokogiri::HTML inside the constructor.
But if I do that, it thinks all my Nokogiri functions don't exist (ie
it's still using hpricot).

Any clues?

···

--
Posted via http://www.ruby-forum.com/.

2

You know, I just realized that these error messages probably mean that
though the parser is Nokogiri, Mechanize pages cannot yet be treated
like Nokogiri objects.

Here are the bread crumbs I'm following:
- http://wiki.github.com/tenderlove/mechanize
- http://mechanize.rubyforge.org/mechanize/ (down at the bottom but
apparently the transition from hpricot is not yet implemented, even
though it says so)

Aaron Patterson Sat, 01 Nov 2008 10:41:39 PDT

"@PhoeniX: Yes, it will be integrated with WWW::Mechanize. I am working
on the Hpricot deprecation roadmap now. I hope Nokogiri will be
integrated with Mechanize by version 1.0 (possibly around January, I’m
not sure)."

- http://tenderlovemaking.com/2008/10/30/nokogiri-is-released/

···

--
Posted via http://www.ruby-forum.com/.

3

wait

···

On Feb 18, 2009, at 16:05 , Patrick L. wrote:

Any clues?

4

Regardless, I'm still not sure how to deal with the situation I pastied
above. Thanks.

···

--
Posted via http://www.ruby-forum.com/.