Re: [Catalyst] Single-domain multi-shop, multi-gateway; linked to the one shopping-cart

2011-12-05 Thread Denny
On Mon, 2011-10-31 at 02:38 +1100, Alec Taylor wrote: > Good morning, > > How would I go about integrating/developing a multi-levelled > meta-shopping-cart using Catalyst? > > [ ... ] > > Thanks for all suggestions, On Mon, 2011-12-05 at 15:53 +1100, Alec Taylor wrote: > Good afternoon, > > H

Re: [Catalyst] Team development and module management

2011-12-05 Thread John Napiorkowski
> > From: Bill Moseley >To: The elegant MVC web framework >Sent: Monday, December 5, 2011 10:41 AM >Subject: [Catalyst] Team development and module management > > >We are slowly replacing a large legacy monolithic application with a (somewhat >monolithic) Cat

[Catalyst] Team development and module management

2011-12-05 Thread Bill Moseley
We are slowly replacing a large legacy monolithic application with a (somewhat monolithic) Catalyst app. There's about a dozen or so developers working mostly on three development boxes. Much of the code is placed into standard (CPAN-style) modules. Everything is under revision control (subvers

Re: [Catalyst] YA CRUD module

2011-12-05 Thread David Schmidt
I updated my code so it does pretty much what CatalystX::SimpleLogin does. Namely to inject a Controller then applying or removing traits. Unlike SimpleLogin I want to be able to inject many Controllers. here is what I came up with: 1 use Catalyst qw/+CatalystX::Resource/; 2 3 __PACKAGE__->

Re: [Catalyst] YA CRUD module

2011-12-05 Thread David Schmidt
Here is a simple testcase of what I did. Once i noticed that i required a method defined in the same role it made sense. #!/usr/bin/env perl use strict; use warnings; use Test::More; { package MyRole; use Moose::Role; requires 'a'; has a => (is => 'rw'); } { package MyClass

Re: [Catalyst] YA CRUD module

2011-12-05 Thread Tomas Doran
On 4 Dec 2011, at 23:46, David Schmidt wrote: just thought i'll keep you up to day so you dont waste time trying to help with a problem i already solved. Turns out the error cause was in one of the roles. It required a method declared in the same role. This has to be a Moose bug in some way.