> 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 -~----------~----~----~----~------~----~------~--~---
