Re: how to organise this app
Damn, I'm the other way around. I just got it set in libraries and had been using the Joomla framework. Now I want to expand outwards without learning another language, and Cake was the natural choice. I'm just used to design my pages, slip in some code, including a file here and there, and letting it run on a server. Now I have to break it up, and the terminology is making me do it right. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~--~~~~--~~--~--~---
Re: how to organise this app
my application is similiar with admin/client/user. Roughly speaking, each model represents a table. For a small application I would create a controller for each admin, client and user, but there are no hard and fast rules for this. You may split your controller into smaller chunks for whatever reason. I really struggled with web developement before MVC. The whole PHP thing was a bleeding mess and i think cake is just what the doctor ordered. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~--~~~~--~~--~--~---
Re: how to organise this app
There are plenty of "real" apps on cakeforge.org, including some that probably apply directly to this situation. There are several that deal with different methods of access control. Also, if you wanted to organize your data properly, you'd have each User belonging to a Role, and each Role having a set of permissions. That would be the most flexible/extensible way to approach the problem. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~--~~~~--~~--~--~---
how to organise this app
i have 3 sets of users (lets not worry about ACL right now) they have 3 separate logins and they goto a different area admin -> admin area client -> client area user -> user area they all use certain functions here and there, i'd only want to restrict access to pages and elements on them, not particular functions. the MVC is a little confusing to how i've written it previously, where I just put them through to a certain set of pages, and included a file with all the functions they need. So how do i setup my model? The database has about 20 tables, about 100,000 records. do i have an admin model, client model and a user model or 1 model, the application name, and just call the necessary functions. tutorials only deal with 1 table, its a bit silly, and there are no real apps to download install and learn from. thanks sicapitan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~--~~~~--~~--~--~---
