I think not. plugins are meant to be standalone applications, also there is no dependency checking etc.
On Mar 15, 3:08 pm, "Brian French" <[EMAIL PROTECTED]> wrote: > Isn't some of the 'code in the core' already there by taking advantage > of the plugin directory? > > On Mar 14, 1:04 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > what you are proposing is: > > 1) a structure (outside of the core code) where 3rd party pieces of > > code can be put > > 2) you don't explicitly mention this, but for 1) to work, you need > > code *in* the core to support this kind of functionality. > > > This is very similar to what i proposed. > > I paid more attention to what needs to be done to make it work, rather > > then the actually possibilities themselves (which i find obvious), > > while your focus is more the possibilities it creates, "forgetting" > > the work that needs to be done to actually make it work. (hence: code > > inside the core) > > > So, a different focus, but certainly similar ideas :-) > > > On Mar 14, 11:39 am, "adi" <[EMAIL PROTECTED]> wrote: > > > > My proposal is not for something that would be part of the Cake core > > > but rather a structured repository for add-ons. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
