Great explaniation Jeremy! +1
I recently got my head around the principle too. I'd recomend it
included in the cookbook alongside MVC introduction to reinforce the
DRY concept. Essential learning for more complex systems.
On Jan 30, 9:52 pm, jeremyharris wrote:
> The best advice is to keep thing
Cool, glad it helped. There are other examples around the internet too.
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe fro
Thank you Jeremy. This is a great, concise description and the example code
helps a lot to see the difference.
{c}
On Mon, Jan 30, 2012 at 4:52 PM, jeremyharris wrote:
> The best advice is to keep things DRY (Don't Repeat Yourself). Generally,
> this results in thin controllers (small control
The best advice is to keep things DRY (Don't Repeat Yourself). Generally,
this results in thin controllers (small controller functions) and fat
models (more methods on the models). Any functionality that you will find
yourself reusing across different controllers that appropriately relate to
a
I see the oft-repeated phrase "Keep your controllers thin and models fat",
but I'm having a problem wrapping my head around it. Most of the tutorials
and examples I see have just about all of the code in the controllers, and
the models have little more than associations.
So.. what exactly does a f
