Re: [Catalyst] uri_for and Chained actions

Oleg Pronin wrote: > If your project is heavy loaded then i think the best way is to write: > > or (easy to change): > > in Object: > sub update_url {'/myapp/'.shift->id.'/update} > > because Catalyst.uri_for() still takes to much CPU to call it a hundred > times per page. > > If you really t

Re: [Catalyst] Re: Serving a custom 404 page with Catalyst::Plugin::Static::Simple

Will Hawes wrote: > On 10/10/2007, *Will Hawes* <[EMAIL PROTECTED] > > wrote: > > With Catalyst::Plugin::Static::Simple loaded, when I request a path > like '/static/non-existent-file', the plugin does stuff like > $c->res->status(404) for me by default. Howev

Re: [Catalyst] email confirmation widget?

Dave Rolsky wrote: On Wed, 10 Oct 2007, Dustin Suchter wrote: Has anyone put together a nice email-validation-link-generator widget for Catalyst (or Perl, for that matter)? All I can find on CPAN is something that is part of Jifty (whatever that is). http://search.cpan.org/~jesse/Jifty-0.70824

Re: [Catalyst] email confirmation widget?

Dave Rolsky wrote: On Wed, 10 Oct 2007, Dustin Suchter wrote: Has anyone put together a nice email-validation-link-generator widget for Catalyst (or Perl, for that matter)? All I can find on CPAN is something that is part of Jifty (whatever that is). http://search.cpan.org/~jesse/Jifty-0.70824

[Catalyst] Form processing

After yesterdays IRC conversation I've gathered some information about form processing using different CPAN modules at: http://perlmonks.org/?node_id=644032. It's nothing complete or authoritative - feel free to comment. -- Zbigniew Lukasiak http://perlalchemy.blogspot.com/

Re: [Catalyst] email confirmation widget?

On Thursday 11 October 2007 04:09:40 am Ian Docherty wrote: > The principle is this. > > Create a text string containing the user-id and the date, e.g. > '666-20001011' then append a 'secret' code to it only known by the > server giving you a string like '666-20001011-ThiSW1llNev3rBQuessed'. > > Yo

Re: [Catalyst] Any chance there is an arbitrary limit to how many classes you can load this way...?

On Tue, Oct 09, 2007 at 11:58:30PM -0400, John Romkey wrote: > Try making sure that you fully qualify all your model and view names, > and that they're the correct names, no typos. > > So, instead of: > > $c->view('Foo') > > use > > $c->view('MyApp::View::Foo') WRONG. $c->view('Foo') is co

Re: [Catalyst] uri_for and Chained actions

On Thu, Oct 11, 2007 at 02:51:31AM +0400, Oleg Pronin wrote: > If your project is heavy loaded then i think the best way is to write: > > or (easy to change): > > in Object: > sub update_url {'/myapp/'.shift->id.'/update} > > because Catalyst.uri_for() still takes to much CPU to call it a hundre

Re: [Catalyst] Any chance there is an arbitrary limit to how many classes you can load this way...?

On Tue, Oct 09, 2007 at 07:12:18PM -0700, Dustin Suchter wrote: > I added the following line to lib/MyApp.pm and the problem is now fixed: > > __PACKAGE__->config( default_view => qr/View::TT$/ ); That should just be => 'TT' Your problem was probably having 'MyApp::View::TT' in there instead. -

Re: [Catalyst] Catalyst::Model::Adaptor - because models shouldn't *do* anything

On Wed, Oct 10, 2007 at 07:03:42AM -0700, John Napiorkowski wrote: > > --- Jonathan Rockway <[EMAIL PROTECTED]> wrote: > > > John Napiorkowski wrote: > > > One thing that I've done a lot with these kinds of > > > adapters is use AUTOLOAD or use Moose's built in > > > attribute delegation to make

Re: [Catalyst] Any chance there is an arbitrary limit to how many classes you can load this way...?

On Tue, Oct 09, 2007 at 04:41:02PM -0500, Jonathan Rockway wrote: > FWIW, this is going to burn users of View::Template::Declare also. > Given YourApp::View::TD and a templates like YourApp::View::TD::*, set: > >YourApp->config( default_view => qw/View::TD$/ ); > > and *NOT*: > >YourApp

Re: [Catalyst] is it CPAN worthy?

On Wed, Oct 10, 2007 at 10:21:49PM +, Fayland Lam wrote: > A module to let user pick components. You can pass any Module::Pluggable::Object search path / include / exclude parameter via MyApp->config->{setup_components}. I don't see what this code achieves that can't already be done that way?

[Catalyst] Re: is it CPAN worthy?

Matt S Trout wrote: On Wed, Oct 10, 2007 at 10:21:49PM +, Fayland Lam wrote: A module to let user pick components. You can pass any Module::Pluggable::Object search path / include / exclude parameter via MyApp->config->{setup_components}. I don't see what this code achieves that can't alr