On Monday, June 25, 2012 12:01:04 AM UTC-4, bs28723 wrote: > > It was recently discussed in another thread in this group, I am > paraphrasing, You need to spend time making sure your data Models are well > thought out before you worry about where the code goes.
This is a great point. In my experience in building applications with more traditional OOP panguages (C# and Java for example), this is where one should always start - designing a class structure. Models don't have to necessarily be tied to a database table, and in fact there might be many more, depending on what data you are managing. If this is well thought out, then the manipulation of these models can be abstracted out in many different ways. Is there a "best practice" in Cake for placing logic for manipulating models that could potentially be called from multiple places in the application? Say calculating the cost of an order with shipping, for example? -- 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 from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
