On 1/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I think the name plugin would be very suitabe for this (as this behaviour is even more "plug-in" then the plugins that we have now) but since that's already taken, we could call them "extensions" , "patches" or maybe even "injections"
I have been thinking on these lines as well and was intending to call them "merge-ins". However for me "merge-ins" are a set of properly packed models, views and components already correctly placed in proper directories which the end users just untar /unzip and upload directly in the /app folder any decent ftp client will take care of putting stuff in proper folders. The reason that I considered this was I wanted a miniscule CMS for Cheesecake-Photoblog which allows end users to create a few pages and since plugins do not have their own webroot they cannot be used for this without hacking the main .htaccess which I did not want.
so your app would have a directory "extensions", just like it has plugins and vendors. and a directory you place in extensions would contain the normal layout (eg models,controllers, etc etc)
What would be advantages of this over giving more power to plugins? Cheers Tarique -- ============================================================= PHP Applications for E-Biz: http://www.sanisoft.com Cheesecake-Photoblog: http://cheesecake-photoblog.org ============================================================= --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
