I second what Nate said, especially #2. It would be awesome if Mambo was both a full standalone CMS, but also a plugin that could be dropped into any Cake app to provide CMS functionality.
-Matt http://www.pseudocoder.com On Nov 25, 1:55 pm, andphe <[EMAIL PROTECTED]> wrote: > Hi Nate, > > On Nov 25, 11:20 am, Nate <[EMAIL PROTECTED]> wrote:> Based on your stated > goals, the two suggestions I would add are: > > > (1) Develop as many of Mambo's features as possible as extensions. > > This will not only make the CMS itself as flexible as possible (and > > the CMS's extension API as robust as possible), but it will also help > > you 'feel the pain' of extension developers as they write new > > extensions or migrate old ones. > > It's a good idea, and it much as we want to go, build what Mambo 4.7 > can do using cakePHP > > > (2) Develop as much of the functionality of the Mambo core itself as > > CakePHP plugins. This will not only make the core easily extensible, > > but it will enable CakePHP developers to more easily integrate Mambo > > code within their own applications, and lower the barrier to entry on > > contributing back to the Mambo core. > > thanks for share your thoughts, very appreciated. > > Andrés --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
