On Thursday, 21 June 2012 15:44:26 UTC+2, André Luis wrote: > > It´s not the cause of being appropriate or not, but i would like to > use plugins folder ONLY for really PLUGINS, wich i dont change > anything, just use... Modular will work ONLY for that application. >
So - put your modules in the app/Plugin folder, and put your plugins in your ./Plugin folder. I think you dont yet recognise that a plugin can be anything - even a single file/class. > > The reason for modular programming is: > imagine you have /products/categories wich uses Category model, and > you have also /blog/categories wich would use also a Category model > that you need to give it another name, or create plugins to separate > models/controllers and views with same name but different objectives. > I don't see how the name of the folder where you put your "modules" makes any difference. Above you're talking about namespaces, which is something that is a ~problem in <5.3 code whatever you name the folder where you put your "modules". > > I hope soon Cake have this feature wich some other frameworks already > have, but even i prefer much more cake. > It already does have this feature - you can define the include paths however you want. AD -- 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
