For mine, being able to deal with objects in the view would greatly improve the readability of data (the whole $user['User']['email'] etc looks incredibly difficult to read to me, compared with $user->email which would be much nicer).
I've always felt dealing with arrays is a bit of a 'hack'. I understand the choice, but I think the idea to move towards a more object oriented approach is more than hype, and long overdue. On Sat, Jul 7, 2012 at 7:35 PM, tigr <alb...@tigr.net> wrote: > No, that is not "nice". The strength of the CakePHP design is in being > very straightforward when it comes to working with the data. I have seen > other frameworks and I think that object-oriented ways are not suitable for > working with data. Well, of course, you can, but would you want to, given a > choice? My answer was "no" and that is why I am using Cake. I am worried > that the object-oriented hype will get the best of you and we will lose a > perfectly sensible data processing framework to the object-oriented glory. > For practical reasons, it would be great to leave the model layer > principles as they are. > > -- > 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 > cake-php+unsubscr...@googlegroups.com For more options, visit this group > at http://groups.google.com/group/cake-php > -- 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 cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
