I use a plugin "tools" where I have my "own" AppController, .. etc as
Libs:
/libs/my_app_controller.php
MyAppController extends Controller {}
now I can use in all projects:
AppController extends MyAppController {}
same for all other classes
On 16 Aug., 09:36, luca capra <[email protected]> wrote:
> Hi,
> I've started using cake 2 years ago, but only from about 6 month
> "productively".
> What I want to ask are some hint on how organize my code.
>
> Actually I would make grow a "branch", something called the "product",
> reusing the same code to permit all sub-project (the "client" dedicated
> implementation) to benefits of new or reviewed functionality.
>
> If I do some edit in app1 then I got to manually patch the other appN.
> I've ended up with fat AppController and AppBheavior which cover common
> functionality for generic situation (eg. action for search,
> autocomplete, contextual list load) which are copy/paste ready.
>
> Could someone kindly share some good practices for "junior" baker like me ?
>
> Thanks in advance,
> Luca
--
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
[email protected] For more options, visit this group at
http://groups.google.com/group/cake-php
