On 1/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I also don't think that cake should look in directories where it isn't programmed to look in. That's why i think cake should be added the core functionality to support these extensions, so that they work out of the box, without application-specfic code. (after all, the cake core is imho the best place to implement such a feature, just like it is for plugins or vendors) I'm generally against implementing all kinds of fancy stuff (like ajax helpers and stuff like that), but "extensions" (or whatever you want to call them) is something that should be supported out of the box, imho.
Ok convention over configuration is one of our big pushes, but this falls outside of that scope. First there is a performance hit on any application having to check for additional locations of files. I have already give users the ability to place all "components" (not meant as controller components) of an application in multiple locations as they see fit, adding something to the core to check for paths outside of what you already have available to you is not going to happen in the core. Nothing is stopping you from adding code to your bootstrap.php or vendors directory and writing the code yourself to perform this task. -- /** * @author Larry E. Masters * @var string $userName * @param string $realName * @returns string aka PhpNut * @access public */ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
