Tom,
Thanks for going forward with this, there are alot of people who
want something like this.
On Mar 23, 8:17 am, Tom Smith <[EMAIL PROTECTED]> wrote:
> > Unfortunatly given your example, 90% of what you want (urls.py with
> > static file handling, a media directory, building the actual mo
> Unfortunatly given your example, 90% of what you want (urls.py with
> static file handling, a media directory, building the actual model)
> are things I expressly do NOT want the wizard to do for ME. (I have my
> own genapp.py tool I use for creating new apps.)
Interesting... I'd like to know wh
Every time this gets brought up it ends up falling apart at the 'what
should it really do' stage.
Unfortunatly given your example, 90% of what you want (urls.py with
static file handling, a media directory, building the actual model)
are things I expressly do NOT want the wizard to do for ME. (I h
On 3/22/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> my head -- every time additions are proposed. In this case, my feeling
> is that adding this extra functionality to management.py -- the core
> management routines in Django -- is not the right place.
I agree it doesn't belong in managem
> It becomes less useful as you get more
> experienced, because there is no "one size fits all" approach to
> application layout.
You wouldn't say that if you'd seen my code... I'd love to be guided
on application layout, in fact, it was only at the end of my first
django project that I think
On Thu, 2007-03-22 at 10:17 +, Tom Smith wrote:
>
> On 22 Mar 2007, at 06:57, Malcolm Tredinnick wrote:
>
> >
> >
> > On Wed, 2007-03-21 at 23:36 -0700, [EMAIL PROTECTED] wrote:
> > > > Hmm... if we do it, this feels like something that should be
> > > > kept
> > > > separate from the stan
On 22 Mar 2007, at 06:57, Malcolm Tredinnick wrote:
>
> On Wed, 2007-03-21 at 23:36 -0700, [EMAIL PROTECTED] wrote:
>>> Hmm... if we do it, this feels like something that should be kept
>>> separate from the standard manage.py;
I don't mind "where" this functionality "lives"... and really don't
On Wed, 2007-03-21 at 23:36 -0700, [EMAIL PROTECTED] wrote:
> > Hmm... if we do it, this feels like something that should be kept
> > separate from the standard manage.py; I can certainly see it being an
> > immense help to developers who are just starting to work with Django,
> > but I can also s
> Hmm... if we do it, this feels like something that should be kept
> separate from the standard manage.py; I can certainly see it being an
> immense help to developers who are just starting to work with Django,
> but I can also see more experienced users saying "I just want a blank
> app, without
On 3/21/07, Tom Smith <[EMAIL PROTECTED]> wrote:
> This is my very crude attempt, which first calls startapp, then does
> standard stuff that ALWAYS seem to have to do and ALWAYS forget like:
> Add a urls.py for my app...
> Add a URL pattern to load static images
> Create the folder to host the
I'd love it if someone made an intelligent startapp call for manage.py. At the moment, it looks like Rails... but doesn't DO an awful lot This is my very crude attempt, which first calls startapp, then does standard stuff that ALWAYS seem to have to do and ALWAYS forget like: Add a urls.py for
11 matches
Mail list logo
