I'm using hpricot 0.8, and everything's working for me...
as to why not Nokogiri, mostly because it's already written in Hpricot and I
don't know the Nokogiri APIs. If you want to take a crack at rewriting, go
for it.
On Sat, Nov 7, 2009 at 9:17 PM, Joe Van Dyk <joevan...@gmail.com> wrote:
On Sat, Nov 7, 2009 at 9:27 PM, Nathan Weizenbaum <nex...@gmail.com> wrote:
> I'm using hpricot 0.8, and everything's working for me...
> as to why not Nokogiri, mostly because it's already written in Hpricot and
> I don't know the Nokogiri APIs. If you want to take a crack at rewriting, go
> for it.
> On Sat, Nov 7, 2009 at 9:17 PM, Joe Van Dyk <joevan...@gmail.com> wrote:
>> I seemed to have the most success with hpricot version 0.6. Using
>> hpricot 0.8 made a lot of tests fail.
Apparently Hpricot 0.8.2 breaks a lot of stuff... I've pushed compatibility
fixes to stable and master. They'll be released as part of 2.2.13, probably
some time today or tomorrow.
On Sat, Nov 7, 2009 at 10:14 PM, Chris Eppstein <ch...@eppsteins.net> wrote:
> I just finished porting our app from Hpricot to Nokogiri... I took notes
> and plan to write a blog post soon.
> -chris
> On Sat, Nov 7, 2009 at 9:27 PM, Nathan Weizenbaum <nex...@gmail.com>wrote:
>> I'm using hpricot 0.8, and everything's working for me...
>> as to why not Nokogiri, mostly because it's already written in Hpricot and
>> I don't know the Nokogiri APIs. If you want to take a crack at rewriting, go
>> for it.
>> On Sat, Nov 7, 2009 at 9:17 PM, Joe Van Dyk <joevan...@gmail.com> wrote:
>>> I seemed to have the most success with hpricot version 0.6. Using
>>> hpricot 0.8 made a lot of tests fail.
On Sun, Nov 8, 2009 at 06:27, Nathan Weizenbaum <nex...@gmail.com> wrote:
> as to why not Nokogiri, mostly because it's already written in Hpricot and > I don't know the Nokogiri APIs
Why port to Nokogiri? We are not using any of its extra features, nor we need speed. Hpricot is a great parser and I've seen it resolve a messy HTML document with loads of SCRIPT tags much better than Nokogiri.
If it isn't broken, don't change it. And if the code is incompatible with new Hpricot, just load the old one (v0.6.x) via the `gem` function.
|
