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.
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 hope soon Cake have this feature wich some other frameworks already have, but even i prefer much more cake. On 21 jun, 08:10, AD7six <andydawso...@gmail.com> wrote: > On Thursday, 21 June 2012 12:07:27 UTC+2, the_woodsman wrote: > > > Re the difference with plugins - I get your point, but if I want to have a > > plugin with multiple models and controllers etc, then surely I still end up > > losing that module structure, and end up with /Controllers and /Views > > lumping things together? > > > My best reasoning for this is: > > > * easier to share code around, without resorting to plugins, or when > > plugins are inappropriate / overkill > > Can you give a specific an explicit example of how a plugin is > inappropriate / overkill please. > > 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 cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
