Like many developers a proportion of my time is spent creating reports based on database data. Sometimes if it is a very simple report which may never be reused I may even simply create a flat php page to get the data out to the user. I do this because I know I can knock it up in about 15 minutes and the job will be done.
I have been following the development of the framework with great interest and I have learnt a lot about MVC and the obvious benefits seperating the logic from the presentation. So I just want a bit of advise regarding these typical day to day tasks. If I were to create a CMS system which creates numerous reports based on data in a database using the Framework and adhering to the MVC architecture, how should the data be transfered to the view? Should the model grab all of the data from a database and generate a large multi-dimensional array which basically mirrors the table to be displayed to the user? Then pass this data to the view (via controller) and create the HTML using somesort of 'for' loop. Does that qualify as not having logic in the view layer? What if you are working with a large amount of data. Is filling a massive array really the most efficent way of achieving this? -- View this message in context: http://www.nabble.com/View-Logic-tf3845561s16154.html#a10890623 Sent from the Zend Framework mailing list archive at Nabble.com.
