WWW::Mechanize and its Subclasses

Hi all!

I recently forked a http://search.cpan.org/dist/Test-WWW-Mechanize-Catalyst/ 
which is a Test::WWW::Mechanize sub-class (which in turn is a WWW::Mechanize 
sub-class) to create http://search.cpan.org/dist/Test-WWW-Mechanize-Mojo/ , 
which I needed to test a Mojolicious app. Now, I later on sub-classed it in my 
project to add some support for:

http://search.cpan.org/dist/HTML-TreeBuilder-LibXML/ 

See:

http://community.livejournal.com/shlomif_tech/47160.html

Now, I've been wondering:

1. Why doesn't WWW::Mechanize has XPath / TreeBuilder functionality in the 
core class? This way every sub-class can have all this functionality, some of 
it is really needed by many people.

2. Suppose I want to inherit from two WWW::Mech classes - will it work? I see 
there's http://search.cpan.org/dist/WWW-Mechanize-Pluggable/ , but it uses 
Module::Pluggable, so if I create a ::Plugin::Test::Mojo, then all the scripts 
using WWW-Mech-Pluggable will be forced to use it, which is not desirable 
(because my Mojo sub-class over-rides the HTTP transport to transfer the 
requests to Mojo).

------------------

What do you think about these issues?

Regards,

	Shlomi Fish

-- 
-----------------------------------------------------------------
Shlomi Fish       http://www.shlomifish.org/
"The Human Hacking Field Guide" - http://shlom.in/hhfg

Deletionists delete Wikipedia articles that they consider lame.
Chuck Norris deletes deletionists whom he considers lame.

Please reply to list if it's a mailing list post - http://shlom.in/reply .