[cgiapp] Can I substitute something else for $self

Probably a dumb question, but I have to ask. I assume $self can be any name. What are the ramifications of changing it? For instance, to the name of my application? So, instead of $self, I were to go with my $login = shift;? Cool? Thanks, Brad

[cgiapp] cgiapp_postrun

Hello again, I'm trying to understand exactly what postrun allows me to do. I would like to have it set a new session (via C:P:A:Session) before the script outputs my .tmpl page. This code produces an error: Error executing class callback in postrun stage: Can't call method 'session' on an

Re: [cgiapp] cgiapp_postrun

works. I want to know more about the engine. Thanks again. Brad Cathey wrote: Hello again, I'm trying to understand exactly what postrun allows me to do. I would like to have it set a new session (via C:P:A:Session) before the script outputs my .tmpl page. This code produces an error

[cgiapp] Good practices: how many run modes in an app

I'm writing a medium-sized web-based financial application that will have up to 50 run modes between presenting empty forms, saving, editing, updating, and deleting from them. Run modes *could* be broken down into groups, e.g., these 4 deal with managing users, these 6 deal with managing project

Re: [cgiapp] Good practices: how many run modes in an app

Thank you Michael, that was very helpful. Unfortunately it uncovered areas I'm unfamiliar with, that a good study of OO will help. Brad Cathey wrote: I'm writing a medium-sized web-based financial application that will have up to 50 run modes between presenting empty forms, saving, editing

Re: [cgiapp] Re: Good practices: how many run modes in an app

I agree wholeheartedly with Mark. I've found this very helpful. A discussion and some examples of the base and apps classes in use would be great as well. Brad 50 is definitely too much. There isn't a hard rule to follow for what is too much, but I think there can never be too few. I usually

Re: [cgiapp] Re: Transferring control to another application

Mark, On 2005-12-20, Ricardo SIGNES [EMAIL PROTECTED] wrote: We do this a lot, with a method that, simplified to remove other weird thin= gs we do, looks like this: sub redispatch { my ($self, $newclass) =3D @_; eval require $newclass; die $@ if $@; # by default,

[cgiapp] Exit strategies from C::A

Hi all, Still trying to learn all the in's and out's of C::A. I'm curious about handling situations where I have common operations that must be applied to all modes upon exiting. Example: I load a unique .tmpl files and assign values to parameters in run modes. But before outputing, I want to

[cgiapp] Uploading files with C::A

Hi all, I've not used C::A to upload files. Anything different or do I just use standard CGI? If different, does anyone have some basic code they can share. I'm just allowing uses to upload a small .gif or .jpg which will be stored in the database or in a folder. I have a validation sub that

Re: [cgiapp] How do I delete a session in C::A::P::Session?

; In your teardown method Dan -Original Message- From: Brad Cathey [mailto:[EMAIL PROTECTED] Sent: Wednesday, 24 January 2007 5:34 a.m. To: cgiapp@lists.erlbaum.net Subject: [cgiapp] How do I delete a session in C::A::P::Session? I've heard rumors for a while that this doesn't work

Re: [cgiapp] Persistence

Bottomline, CGI::App does lots of the work for you. Life is easier. I could not develop for the Web without it. Brad On Feb 5, 2008 4:44 AM, Mark Knoop [EMAIL PROTECTED] wrote: Hi I'm new to CGI::Application. I like the way it makes me organize the script but I guess I could do it in this

[cgiapp] Anomaly in CAP::Session

I don't know if this has been discussed previously, but I can't kill a session with: $self-session_delete; however: my $session = new CGI::Session(); $session-delete(); works like a champ. Am I missing anything? Thanks! # CGI::Application community mailing list

[cgiapp] Understanding sessions

Hello, Though I'm been using CGI::App for a few years, this will sound like a newbie thread, but bear with me--your help will be greatly appreciated. I'm still trying to understand queries, sessions and cookies. First, I have read the CAP::Session docs several times and my understanding is:

Re: [cgiapp] Understanding sessions

Mark, That was a big help. Mainly knowing that the cleaning up of these /tmp files outside the realm of anything in my initial application. It does make sense. I'll work on a cron job to eliminate the dead wood every so often. On Sun, Feb 24, 2008 at 10:24 AM, Mark Fuller [EMAIL PROTECTED]

Re: [cgiapp] Usefulness of the FillInForm plugin since the HTML::FillInForm 2.0 release?

Mark, I use both, but only HTML::FillInForm in legacy code before I started using C::A exclusively. I've had no issues with either. I do a ton of online forms where I untaint and validate the data and use CAP::FillInForm to repopulate the form if I need to re-output the form do to a