I'm not sure what part of my advice you have problems with. I try to make the steps clear, so please tell me what step I didn't explain thoroughly enough:

Learn what your browser sends, then send that from Perl.

This is meant to tell you to investigate what data your browser sends to the remote webserver when you click a button. The intention behind is that the remote webserver cannot know whether there is a browser or a Perl script at the other side, so as long as your Perl script sends the same data as a browser, it will never find out.

For example, using the Live HTTP Headers extension.

This sentence is to show you a tool that can do the above.

Or learn Javascript and how it interacts with the HTML DOM, and what the click for a submit button does.

This sentence is intended to show you the other, more static, approach to scraping. Read (and understand) the Javascript and what it does, and directly replicate that from Perl.

Or just modify the code to find it out.

This sentence is to show you a variation on the more static approach. By modifying the Javascript code, you can also maybe find out what it does and what purpose it has.

Hi Corion - Sorry for the confusion but I was not able to understand the Live HTTP Headers articles.Probably because of the kind of experience I have.I didn't give the second one a try(learning Javascript).Tried the last one and modified the Javascript response i got but got stuck with the click.I would like to follow more on this

The Live HTTP Headers are a plug-in for Firefox, a web browser in common usage. They allow you to see what your browser sends, so that you can replicate that from Perl.

If you are automating websites using Javascript, some amount of Javascript knowledge is inevitable. I recommend you try to at least vaguely understand the Javscript that the pages use.

None of the solutions can shield you from understanding what goes on between the web browser and the webserver, so I recommend you start familiarizing yourself with that.

I find Firebug helpful when debugging JavaScript, it's not a substitute for learning JavaScript but it can help pinpoint problems.

WWW::Scripter::Plugin::JavaScript does indeed use JE, according to the WWW::Scripter::Plugin::JavaScript it's also an alpha release. Corions advice is to examine how your browser is sending, then just send the same response using Perl. Corion suggests using a tool to simplify this process. The other suggestions are still valid also.