in reply to Passing and recieving params
in thread Passing and recieving params

i have a load of other modules to call from within the BlastTool.cgi script.

So what's the problem? The BlastTool module (formerly BlastTool.cgi) can still load all the modules it wants.

I was just trying to do this to try and learn how to execute another script really so i know personally what i am doing in the long run.

What we're seeing is "I want to wash my cat, so can you teach me how to neuter a cat? I know what I am doing in the long run." This communication problem is making it rather hard to help.

Replies are listed 'Best First'.
Re: Passing and recieving params
by MonkPaul (Friar) on Jul 15, 2005 at 17:12 UTC
    Right, i will start again and take on board what you said.

    Im going to leave the BlastTool.cgi as the first port of call, then just split up the modules.

    What in effect i need to do, as the finished article, is to wrap the software so that other java applications can input their params and get output back. But still have the capability to produce output to a web browser

    Another question then: If i have input from both command line and web page, can i get the input the same way or do i have to use an if statement eg. 

      $html = new CGI;  # create a new instance of CGI 
  $seq = $html->param('Sequence_input');
  
  if($seq eq "")
  {
    GetOptions( "sequence=s" => \$seq);
  }

    [download]

    monkPaul.

[reply]
[d/l]
      The following would be more appropriate: 
      my $seq;
...

if (defined($ENV{GATEWAY_INTERFACE})) {
   # We were called via CGI.
   my $cgi = new CGI;
   $seq = $cgi->param('Sequence_input');
   ...
}
else
{  
   GetOptions(
      "sequence=s" => \$seq,
      ...
   );
}

      [download]
[reply]
[d/l]

In Section Seekers of Perl Wisdom