I think it would be possible to write the core of the application as a plugin, but distribute it inside of an application that provides the front-end. This would serve the purpose of (a) appealing to a mass market by making it a working application out of the box, (b) providing a plugin for CakePHP developers to integrate into their own apps, and (c) an example application that demonstrates how to integrate said plugin, for the benefit of those who wish to do so.
I think a lot of re-distributable CakePHP apps could benefit from being designed like this. Anyway, something to think about. On Oct 23, 9:12 am, Mathew <[EMAIL PROTECTED]> wrote: > > I have honestly not given that idea much thought. I mostly approached > > the development as if phpShop were the base application and that it > > would have it's own set of plugins to expand its functionality. I > > would have to see how a plugin can have plugins... Or how to have a > > similar ability to extend functionality. If you have ideas or can > > point me in the right direction, please let me know. > > If you redesign it to be a CakePHP plug-in then your addressing a much > smaller market, and that isn't healthy for the project. > > What you should do is continue with what your doing, but add a > phpShopAPI and then develop a CakePHP plugin that uses that > phpShopAPI. > > Now PHP developers can use your phpShopAPI, and Cake developers can > use the phpShopAPI plugin. While regular phpShop users can just use > the standalone application. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
