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 static images > Put some examples in the views calls and add standard imports > Create all the classes in models.py that I think I'm gonna need (but not > call syncdb yet) > Add __str__ calls to all classes, and Admin classes (it's easier to delete > them than to add them by hand later) > Docstrings, one day I may comment my code.
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 having to answer all these questions at the prompt". So maybe this could work more as an introductory tool, so that once a developers are familiar enough with Django to make the choice, they can decide to keep using it or switch to the standard manage.py app skeleton. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
