On 11/23/2010 07:54 PM, Bill Moseley wrote:
On Tue, Nov 23, 2010 at 8:16 AM, Sir Robert Burbridge
rburb...@cisco.com mailto:rburb...@cisco.com wrote:
By the way, I forgot to mention one piece of practical advice when
determining what should be in your controller vs. model:
- Original Message
From: Eden Cardim edencar...@gmail.com
To: The elegant MVC web framework catalyst@lists.scsys.co.uk
Sent: Tue, 23 November, 2010 0:59:18
Subject: Re: [Catalyst] Begginer's question about application structure
Martin == Martin Bendix martinben...@yahoo.co.uk
From: Sir Robert Burbridgerburb...@cisco.com
To: The elegant MVC web frameworkcatalyst@lists.scsys.co.uk
Sent: Mon, 22 November, 2010 17:20:16
Subject: Re: [Catalyst] Begginer's question about application structure
I use DBIx::Class with multiple interfaces in the same app
On Tue, Nov 23, 2010 at 8:16 AM, Sir Robert Burbridge rburb...@cisco.comwrote:
By the way, I forgot to mention one piece of practical advice when
determining what should be in your controller vs. model:
*Write your controller first.*
Don't you mean second? After writing the tests? ;)
--
Hi,
As a Perl and Catalyst novice, I have recently completed the online Catalyst
tutorial, and read the Definitive Guide to Catalyst. However, I have a few
questions about the basic structure of a thin controller, fat model application.
I'd like to take my learning to the next stage by
Personally, as a novice too ^^, I like to keep the Model code clean enough,
not to include too much functions like parameters check, which we can just
create a controller action to accomplish.
I got similar questions though: Some common functions, like date
manipulation/formate, what is the
Personally (and this does mean personally), I'd do it as follows:
Your actual logic code (e.g. the whole deal of storing and retrieving
things from the database) should be in a separate set of modules. Call
those the 'backend' stuff. The main module here should be able to
connect to the
Martin Bendix wrote:
As a Perl and Catalyst novice, I have recently completed the online
Catalyst tutorial, and read the Definitive Guide to Catalyst. However, I
have a few questions about the basic structure of a thin controller, fat
model application.
I'd like to take my learning to
- Original Message
From: Ben van Staveren benvanstave...@gmail.com
To: The elegant MVC web framework catalyst@lists.scsys.co.uk
Sent: Mon, 22 November, 2010 15:13:00
Subject: Re: [Catalyst] Begginer's question about application structure
Personally (and this does mean personally
Have a look at this article
http://www.catalystframework.org/calendar/2007/14 which covers using
Catalyst models externally.
The code that goes with it is well out of date but should give you the
general idea using an external DBIC model class.
Access to the model from a batch script:
On 11/22/2010 09:17 AM, Martin Bendix wrote:
Hi,
As a Perl and Catalyst novice, I have recently completed the online Catalyst
tutorial, and read the Definitive Guide to Catalyst. However, I have a few
questions about the basic structure of a thin controller, fat model application.
I'd like to
Martin == Martin Bendix martinben...@yahoo.co.uk writes:
Martin My model should be well separated from the controller.
Martin Most, if not all of the application functionality should be
Martin exposed via the model, so that the Catalyst controller only
Martin needs to make simple
From: Sir Robert Burbridge rburb...@cisco.com
To: The elegant MVC web framework catalyst@lists.scsys.co.uk
Sent: Mon, 22 November, 2010 17:20:16
Subject: Re: [Catalyst] Begginer's question about application structure
I use DBIx::Class with multiple interfaces in the same app
13 matches
Mail list logo
