The only reason that I can think of off the top of my head is that when CE upgrades, you will have issues. You will have to manage the upgrade process for your application. Where as if you leave CE as a plugin you can just update the CE code and then you get the fixes, any enhancements and the only things you will have to manually fix are the models where you made changes.
On Thu, Feb 12, 2009 at 1:02 PM, mgutz <[email protected]> wrote: > > I can subclass modesl, create themes and override views easy enough. > By the time I jumped through all the hoops I realize it would have > been easier to customize the views in plugins directory and edit the > models directly. That being the case, then why not promote CE to a > full blown app? I imagine this also makes for a more responsive > application by doing away with the engine plugins altogether. I can > see the benefit of using CE as a plugin if you have an existing rails > app, but if you're creating a site from scratch where most views will > be customized and models changed then CE as a plugin is an extra level > of indirection and added complexity. > > I looked at Insoshi (viral license not good for commercial work), > lovdbyless (like the pre-built functionaly of CE better). Maybe I'll > create a fork on github. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CommunityEngine" 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/communityengine?hl=en -~----------~----~----~----~------~----~------~--~---
