Re: Best way to extend an existing django app

On May 2, 12:01 am, Scott SA <[EMAIL PROTECTED]> wrote: > On 5/1/08, joasch ([EMAIL PROTECTED]) wrote: > > I've been reading about newforms here > but have yet to put it > into action. That will change any day now - I appreciate your pointing

Re: Best way to extend an existing django app

On 5/1/08, joasch ([EMAIL PROTECTED]) wrote: >this is what I have done. I checked out satchmo trunk and keep it >updated. After checkout I exported it to a new copy and check it in on >my own SVN, and there I make my changes. When ever there is a change >in satchmo trunk I merge these changes int

Re: Best way to extend an existing django app

Scott, this is what I have done. I checked out satchmo trunk and keep it updated. After checkout I exported it to a new copy and check it in on my own SVN, and there I make my changes. When ever there is a change in satchmo trunk I merge these changes into my own copy. It's a bit of extra work bu

Re: Best way to extend an existing django app

Hi Rajesh, On 4/30/08, Rajesh Dhawan ([EMAIL PROTECTED]) wrote: >> Is there a reasonable/accptable ot better yet "recommended" way to add >functionality, etc. to an app without resorting to the above points? If so, >what stones should I turn (via google serches, etc.) to figure this out. > >It

Re: Best way to extend an existing django app

Hi, > Is there a reasonable/accptable ot better yet "recommended" way to add > functionality, etc. to an app without resorting to the above points? If so, > what stones should I turn (via google serches, etc.) to figure this out. It depends quite a bit on how "extensibly" the said app was desi

Best way to extend an existing django app

Hi, I'm looking for clues as to the best way I can add methods and attributes to an existing django app. I need to add quite a bit of functionality to a portion of the existing app, while other portions are good (very good, actually). Two initial, but undesirable, options I see are to fork or