Yeah, correct ideas guys, thanks for the feedback. The intention though of the discussion is in review of the purpose of the naming conventions so as to obtain clarity and maybe shared thought on the current consistency of the classes and names. I moved away from this scenary a while ago, I am not saying that I would do this in practice. 1 model is still the better way forward.
Thick models and thin controllers and views... definitely something that I have started to implement and move to over the last month. It is without a doubt VERY good practice. What are your thoughts though on the naming conventions and the last aspects of my previous reply? ie. ******* I agree with what you are saying about writing less. If this is the case then, perhaps the controller filename would be better being the same as the helpers, components etc. filename = users.php; class = UsersController. Then the same theory should perhaps apply to the models to maintain consistency... filename = user.php; class = UserModel. Overall this would be adopting better conformity to the conventions across the files and class names. ******* --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
