PROTECTED]]
: Sent: Friday, June 07, 2002 4:49 PM
: To: Bill Moseley
: Cc: [EMAIL PROTECTED]
: Subject: Re: [OT] MVC soup (was: separating C from V in MVC)
:
:
: Quoting Bill Moseley ([EMAIL PROTECTED]):
: I, like many, find these discussion really interesting
What I didn't like about this is I then had to adjust the so-called
controller code that decoded the user input for my request object to
include these new features. But really that data was of only interest
to
the model. So a change in the model forced a change in the
controller.
No, a
At 12:13 PM 06/08/02 +0100, Jeff wrote:
The responsibility of the Controller is to take all the supplied user
input, translate it into the correct format, and pass it to the Model,
and watch what happens. The Model will decide if the instruction can be
realised, or if the system should explode.
From: Bill Moseley [mailto:[EMAIL PROTECTED]]
Sent: 08 June 2002 20:48
I've gone full circle on handling user input. I used to try to
abstract
CGI input data into some type of request object that was then passed
onto
the models. But then the code to create the request object ended up
Hi all,
On Fri, 7 Jun 2002, Valerio_Valdez Paolini wrote:
On Thu, 6 Jun 2002, Jeff wrote:
We can take the discussion off-line if the list feels it will be too OT.
No, please :)
Yes, please.
73,
Ged.
Bill Moseley wrote:
My MVC efforts often fall apart in the C an M separation. My M parts end
up knowing too much about each other -- typically because of error
conditions e.g. data that's passed to an M that does not validate. And I
don't want to validate too much data in the C as the C
On 6/7/02 1:04 PM, Perrin Harkins wrote:
For example, if you have a form for registering as a user which has
multiple fields, you want to be able to tell them everything that was
wrong with their input (zip code invalid, phone number invalid, etc.),
not just the first thing you encountered.
Hey Perrin Bill --
You could also just punt and push this out to the
controller. (Not very pure but simple to implement.)
This is exactly what I had in mind. (Perhaps you can explain what you mean
by not very pure.) The methods in any model module I would write would
have expectations
On Thu, 6 Jun 2002, Bill Moseley wrote:
Anyone have links to examples of MVC Perl code (mostly controller code)
that does a good job of M and C separation, and good ways to propagate
errors back to the C?
http://pagekit.org,; might be interesting.
Fiq
Hi Bill --
I, like many, find these discussion really interesting. I always wish
there was some write up for the mod_perl site when all was
said and done.
But I guess one of the reasons it's so interesting is that
there's more
than one correct point of view.
I expect to complete an
On Thu, 6 Jun 2002, Bill Moseley wrote:
Anyone have links to examples of MVC Perl code (mostly controller code)
that does a good job of M and C separation, and good ways to propagate
errors back to the C?
I'm working on my own impelmentation at the moment and am planning to have
a
From: Jesse Erlbaum [mailto:[EMAIL PROTECTED]]
Sent: 06 June 2002 19:34
To: 'Bill Moseley'; [EMAIL PROTECTED]
First off, it is less of an MVC crime to combine your Model and
Controller than it is to combine your Controller and View.
I disagree - coupling Controller and Model
From: Bill Moseley [mailto:[EMAIL PROTECTED]]
Sent: 06 June 2002 19:06
To: [EMAIL PROTECTED]
My MVC efforts often fall apart in the C an M separation.
My M parts end up knowing too much about each other -- typically
because of error conditions e.g. data that's passed to an M that
Bill Moseley writes:
Anyone have links to examples of MVC Perl code (mostly controller code)
that does a good job of M and C separation, and good ways to propagate
errors back to the C?
I humbly (do believe that ;-) submit http://petshop.bivio.biz
Every page contains the control logic which
14 matches
Mail list logo
