On Jan 8, 1:35 pm, Dieter wrote: > On 1/8/07, AD7six <[EMAIL PROTECTED]> wrote: > it's a nice feature though, that you can just add some code in your > bootstrap to tell cake to load some more models/controllers/.. from the > paths you specify. But letting cake look automatically in a specific > directory would make much more sense to me. (like it does for > plugins/vendors) I think you misunderstand Dieter, if you specify these path variables, they are checked 100% transparently.
With transparency, i mean "out of the box", without any application-specific code.
I don't think cake should look anywhere except where it expects things to be out of the box, and with a minor edit to the bootstrap you can turn on and off these merge-ins with only the css/js problem left to solve.
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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
