I have been programming with several different languages for many years but always in a procedural manner. I have been trying to use OO development ideals recently but they always end up in a messy hybrid implementation.
So have started trying to use cakePHP. Frustrating to say the least! Least of all because I am so used to being able to quickly produce code that gets me through a problem and onto the next one. I had direct control over the entire application structure. How long is it going to take to get the hang of the cake structure MVC stuff? Has anyone come from being a strong procedural developer to the OO approach got any recommendations/pointers/humour to make this frustrating day a little less so... I have worked through a few of the tutorials on cakePHP.org without too much difficulty but I don't feel any better prepared to take on a real project? My growing concern now is that I don't get how a large application looks or acts. All the examples I have seen so far are single purpose. How do multiple controllers within an application communicate. Can database tables related to several different models get updated/altered in one transaction? I am looking at using cakePHP to develop a virtual project management application for a commercial project I have undertaken and could do with some belief lest this fledgling baker will have to hang up his apron. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
