Hi, Diogo.
If your aim is to separate the models from the controllers, views, etc., then Cake can handle that. I haven't tried this yet, but I was looking at the possibility of splitting off the back-end functions of my app to a separate app on a sub-domain. From there I can either link to the models in in the main app, or split the models off into their own "app" just for modularity. Like Reuben said, plugins would also help to avoid redundant code between apps.
The Cookbook shows you here http://book.cakephp.org/2.0/en/core-utility-libraries/app.html, in the section titled "Adding paths for App to find packages in" how to direct Cake to another directory containing the Models to be used by your app (theoretically, the same would apply for other Cake classes, like controllers, views, etc.).
Like I said, I haven't tried this yet, so I am not sure if there are any practical issues to be resolved.
Good luck.
--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/groups/opt_out.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment