Re: [Fofredux-devel] Re: MVC rethought

[Kevin <ke...@dr...>]

> Kevin, you're correct that a lot of what you're doing is the Model.
> Model interface is the CRUD stuff (for those who don't know - Create,
> Read, Update Delete). The controller is any of the business-logic (as
> Kevin mentioned).
>
> Evan - I don't expect someone to sit and rewrite all of FoFRedux -
> though I did all the refactoring of FoF on the original fork (or
> 'reduxing' :) since FoF was even worse about not DRY (Don't Repeat
> Yourself). But if you subscribe to the Brooks 'Mythical Man-Month'
> theory, then projects should have 1 architect and lots of monkeys. :)
> I'm not prescribing that, but thought it a good idea to have 1 person
> rip through and lay out functions and then as you mentioned, everyone
> fill those functions in.
>
> The alternative is what has happened, which is some init.php functions
> have HTML in them, some don't, some have diff't params,  etc.
>
> So Kevin - don't worry too much about getting everything, but if it's
> ok - just put out what functions and parameter interfaces there is to
> the Model code (the db-side, which you are the expert at :)


The model is a little more then the db interface, but not much.  One exam=
ple
of this is an operation like "update feed".  This is a purely model
activity, IMHO.  It has many steps, only some of which deal with database
access.  Now, update feed is meaningless without the controller to tell
*when* or *if* a feed should be updated.  That's just my take on it.

As long as the line between view and everything else is clear, that's wha=
t
matters, and that's where we will get the most benefit from this exercise=
.


--=20
Kevin