> "Harald" == Harald Joerg <[EMAIL PROTECTED]> writes:
Harald> That's what I like with CGIPH: The code is so slim that it is pretty
Harald> easy to understand, hence rather riskless to overload, and TIMTOWTDI!
Thanks! That was the point. Do just the basics. Don't go nutty.
Add things as yo
On 10/25/07 10:32 AM, "Harald Joerg" <[EMAIL PROTECTED]>
wrote:
> Writing an extra mantra $self->name_to_page() dozens of times (in
> every respond, every module) is sightly annoying and gives me the
> impression of a decentralized workaround.
Actually, I just look at it as useful refactoring. We
Andrew Gianni <[EMAIL PROTECTED]> writes:
> On 10/25/07 5:31 AM, "Harald Joerg" <[EMAIL PROTECTED]>
> wrote:
>
>> sub respond {
>># ...du whatever needs to be done in response to the user's request
>>return 'NextPage';
>> }
>
> Try:
>
> sub respond {
>my $self = shift;
>return $sel
On 10/25/07 5:31 AM, "Harald Joerg" <[EMAIL PROTECTED]>
wrote:
> sub respond {
># ...du whatever needs to be done in response to the user's request
>return 'NextPage';
> }
Try:
sub respond {
my $self = shift;
return $self->name_to_page('NextPage');
}
Or is there some specific reas
Yesterday I've encountered a case where CGIPH isn't as DWIM as it
could be. It had never hit me before, because usually I use mod_perl
and compile all stuff in the startup routine.
The docs of CGIPH state:
... The package for the class is autoloaded if needed.
This is true as long as the class i
