@Hannibal Lecter: I do use classPaths. Sometimes to achieve proximity of related MVC files for a feature of my application I have to create an 'app' for each feature; each of these apps has a complete cake application structure including config, tmp, app_controllers etc. (beside the regular, feature-related MVC folders) which is redundant.
Especially the config folder may contain files which are an exact copy of the main application's config. Nesting/pushing MVC files into deeper levels in the default cake's MVC structure can help organize folders for different features BUT the proximity is lost and my files get spread out. If I want to make a single improvement / bug-fix to an existing feature I have to look / make changes in multiple places. then I cannot just simply commit/ update/deploy the a single feature folder. Instead I have to commit/ update/deploy files in different places. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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?hl=en -~----------~----~----~----~------~----~------~--~---
