Re: [Catalyst] Splitting up a large application: Shared config and templates for multiple applications

On 28 Aug 2009, at 17:55, Rodrigo wrote: Anyone building applications out of multiple small Catalyst applications like this? How do you set up the apps to share templates and a config? Anything more interesting than passing in paths? I have a working module called

Re: [Catalyst] ActionClass vs. Moose Role?

On 28 Aug 2009, at 19:05, Bill Moseley wrote: Well, if you were going to write something like RenderView now would you still write it as an ActionClass? Yes, as Render view isn't something I would ever want two of them on the same action. As a counter example, Catalyst::ActionRole::ACL

[Catalyst] Feedback requested on HTML::FormHandler's new widget system

A new widget system for HTML::FormHandler is currently under development, and it would be nice to get feedback from those who might be interested in it before putting it out in a release. It's currently in the HTML::FormHandler repository on github:

[Catalyst] TEST - Please ignore.

Test email, please ignore. Cheers t0m ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site:

[Catalyst] Class data in a Moose::Role plugin

I also tried with Catalyst::ClassData. Must be missing something. All modules up to date. On Perl 5.10.0. $ catalyst.pl MyApp $ cat lib/Catalyst/Plugin/Role.pm package Catalyst::Plugin::Role; use Moose::Role; use MooseX::ClassAttribute; class_has 'Cache' = ( is = 'rw',

[Catalyst] Testing OpenID Logins + more

Hey guys, I'd really like to start testing my controllers, and I wished I'd started sooner, but oh well. The biggest barrier at this point is the login system. It uses OpenID for auth, which is where the hard stuff comes from. I *have* looked at the tests for the OpenID module for catalyst

Re: [Catalyst] Class data in a Moose::Role plugin

Bill Moseley wrote: I also tried with Catalyst::ClassData. Must be missing something. Nope, you're not missing anything - class data in roles doesn't play nicely. This would all be a lot easier (or not needed) if we had an app class instance, rather than it being a class.. Cheers t0m

[Catalyst] Where to add access control? Override execute() or dispatch()?

I'm in the process of adding custom access control for actions. I've been looking over C::P::Authorization::ACL. It overrides execute() which is run for every method called by the dispatcher, which includes begin, auto, the action itself, and end. Depending on how the ACLs are specified, the

Re: [Catalyst] Testing OpenID Logins + more

On 1 Sep 2009, at 04:43, fREW Schmidt wrote: I'd really like to start testing my controllers, and I wished I'd started sooner, but oh well. The biggest barrier at this point is the login system. It uses OpenID for auth, which is where the hard stuff comes from. snip Why bother with the

Re: [Catalyst] Where to add access control? Override execute() or dispatch()?

On 30 Aug 2009, at 21:17, Bill Moseley wrote: I'm trying to decide if this is the best approach, or if would be better to test the ACL before dispatching. The issue is if the request is for /foo/bar, and an ACL rule blocks that, should Foo::(begin|end|auto) still run? Or should it act as if

[Catalyst] Fetching URL Content

I have a requirement to fetch URL content - this is currently mostly to do with the View phase, to include chunks of HTML for core branding in the templating. ie; Top header, footer, global nav, that sort of thing. Ideally, I'd like to do it directly from the Template Toolkit templates, but TT