[cgi-prototype-users] linking to non-default page

2005-06-28 Thread John S J Anderson
I'm just starting to try to wrap my head around C::P::Hidden (or vice versa), so it's entirely possible I'm not thinking about this properly -- but I can't figure out the Right Way to link to a non-default page. Suppose I have two "pages": Welcome and Login. (A "page" is a combination o

Re: [cgi-prototype-users] linking to non-default page

2005-06-28 Thread Randal L. Schwartz
> "john" == John S J Anderson <[EMAIL PROTECTED]> writes: john> 2) encode '?_state=Login' into the URL in the href attribute (or various john>other schnanigans with specifying some state in the URL -- use john>'state=login' and switch on that in the respond_per_page() in the john>b

Re: [cgi-prototype-users] linking to non-default page

2005-06-28 Thread Randal L. Schwartz
> "Randal" == Randal L Schwartz writes: Randal> Then I can say: Randal> [% WRAPPER link state = "Login" %]Login![% END %] No, that's not right. I have to do something with a href =. Not sure how I was using that here. :) Randal> ---

Re: [cgi-prototype-users] linking to non-default page

2005-06-28 Thread Andrew Gianni
Generally, here's how I've dealt with it: Make your link on the welcome page something along the lines of: wrote: > > I'm just starting to try to wrap my head around C::P::Hidden (or vice > versa), so it's entirely possible I'm not thinking about this properly > -- but I can't figure out

[cgi-prototype-users] Using multiple base classes for an app

2005-06-28 Thread Andrew Gianni
I'm starting to run into situations where I have (or will soon have) multiple applications that need to occasionally share pages, or at least some functionality. I was thinking that a good way of doing this would be to allow the config_class_prefix method (CGI::Prototype::Hidden) return an array ra