On 2005-03-19, Andy Lester <[EMAIL PROTECTED]> wrote:
>
> login: { # block to define
> how to log in
> url m|https?://james.bond.edu.au/.*| or die "there is nothing to
> log in here"
> <form> and fill uid $username # fill out the
> login form (there is
> and fill pwd $password # only one there)
> and click login
> url m|^https://| or die "not using HTTPS"
> # now we are using
> SSL, good
> }
This looks very cool. However, I think this will be most successful with
non-programmers. It reminds me of AppleScript.
The beautiful thing about WWW::Mechanize is that the target users are
Perl programmers, and it's programmed in Perl.
So if something doesn't work like I expect, I can look at the guts to
understand, and maybe fix it myself.
I think if I was using weezl and it didn't work like I expected, I'd be
less inclined to diving in and see why the weezl wasn't being parse as I
expected.
I think the last time I tried a language written in Perl was the
Minivend/Interchange tag language, and it was a bad experience for me.
I kept running into things I could already do easily in Perl, but I had
to re-learn them in this more abstracted language where the ideas were
hardere to implement.
I see advantages to having more consice and abstract web-browsing
language like this, but I don't expect it to supersede the Mechanize
for a lot of things.
Mark
--
http://mark.stosberg.com/
