You were right - I did just send it to him.
An annoying trait of the CGI::App list, I do it all the time. I've copied
the list back in.
any) and the next page. This 'next page' can follow any number of different
actions or even no action at all (in the case of a simple navigation). As
Any ideas as what am I doing wrong??
CGI::App does that for you. You want:
my $self = shift; #The CGI::App object;
my $q = $self-query; #The CGI query object.
$q now works as you would expect.
-
To unsubscribe, e-mail:
Here is the error what I am getting now. It's complaining about the call
method.
main::(test.cgi:36):my $q = $self-query; #The CGI query object.
DB1
Can't call method query without a package or object reference at test.cgi
line 36, IN chunk 27.
The script is as below:
snippage
I
Are any of you doing this? Do I have to turn each of this scripts into
mini CGI::Applications? I suppose this wouldn't be a huge deal, but it
would be nice to have another option. I'm not new to using, but
relatively new to creating, OOP code.
Can you make those methods into their own,
(sent to list -- Phil, if you want yours to the list, you might want to
resend. Have I mentioned lately I hate lists that don't reply-To by
default?)
Is anyone's web server really that strapped for disk space? This kind of
compression is great for operating systems and disk controllers but is
I am trying to put a graph in my application and I am getting the junk on
the web page insted of the image. I changed the header to image/png via
$q-header() method still its not working. Can anyone help me with this
problem. The code for the script is as below.
CGI::App takes over sending
I've bitten off a large project, and I'd love some advice.
I need to write survey creation and taking software analogous to Slices
[ http://www.electricvine.com/products/Overview.asp?ProductID=31 ] or
Pegasus [ http://www.websurveyor.com/prod_intro.asp ].
I'm claiming we're better off writing
First off: Is being able to change the run-mode as important as I suspect
it is? If not, no further changes are required.
It is important, within the current scope of relativity (i.e. Its good to
have if we have a cgiapp_prerun() method)
I'm inclined to use the return-value method, but
What about having $self-current_rm() as an object function instead of
passing it around into and out of sub-routines?
then you could get the rm:
my $rm = $self-current_rm();
and change the rm:
$self-current_rm( $rm );
I like this idea, but it could get more involved. I currently have
Yeah, you're off track. We're not talking about setup()...
Okay, I withdraw my complaints :)
2) Is discouraged, because 90% of soft-references should be hash elements?
That still leaves a healthy 10% for this and a few other usages.
I see the healthy 10% as areas that are controlled,
(/me cleans out the growing Cc: field and mutters [again] his
counter-culture preference regarding Reply-to and lists)
Use CGI::Session, this deals with session management and random IDs
But how would you use this to ensure a form hadn't been submitted twice,
in the case where a client could
Sounds cool, do you use cookies for that?
Nope, I have an irrational dislike of cookies. I just drop it in as a
hidden field to the form. Of course, this requires that your form be
generated dynamically as opposed to being flat HTML.
Of course, this still has a 1 in a (my pseudorandom
use CGI qw/:standard/;
Don't use this, CGI::App handles CGI for you. (you can get the CGI object
via $self-query())
I suspect param() is getting mangled somewhere along the line. Remove the
use CGI line and try again.
-
In the case where the form is being used to insert some data into a
database, here's an easy trick that I like to use:
In the form display run mode, select the next available unique ID for
the item that will be it's primay key. When you submit the form, you
simply have to check to see if
Postgres handles this gracefully with it's SEQUENCES feature. After
user1 calls up the form, user2 will be returned ID 12 rather than 11. So
there's no possible conflict like that.
Okay. I'm just starting to play with with Postgres, so here are a few
questions (that presumably will have some
15 matches
Mail list logo
