Yes, that should work (not recommended though). On Thu, Oct 23, 2008 at 1:34 PM, Levi Rosol <[EMAIL PROTECTED]> wrote:
> > thanks for the feedback. Making copies of the models makes sense, > however, i'm trying to reduce any code duplication, or "where the hell > is this model/controller/view at??" headaches. basically, i'm trying > to keep the app as DRY as possible. > > But if i'm understanding what i've read correctly, i could just copy > over all of the model/view/controllers/helpers into the app, and > delete them from the plugin. is this correct? > > thanks!! > > Levi > > On Oct 23, 12:07 pm, "Bruno Bornsztein" <[EMAIL PROTECTED]> > wrote: > > > I anticipate extending nearly every model, some extensively. > > > > This is not really a problem: in your case, I'd recommend just making > copies > > of the models in your application directory. The app will use those > instead > > of CE's. > > > > So my question is, what would it take to move the CE code base from> > being a plugin, to being my actual app? > > > > It's probably not hard, but also not really necessary. You can already > > override any view, helper or controller, and if you need to make changes > to > > models, just duplicate them as indicated above. > > > > As an example, TennisMetro <http://www.tennismetro.com> is is a CE-based > app > > I built that extensively modifies and extends the core framework, while > > still using CE as a plugin. I can't really think of a scenario where what > > you're suggesting would make the most sense. > > > > Good luck! > > Bruno > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
