On 7/9/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 7/8/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > 1. Expand the default application skeleton, or differentiate somehow
> > between a minimal, "traditional" app skeleton and a more robust one
> > which includes files and directories oriented at a distributable
> > application.
> >
> > 2. Spend a lot more time documenting best practices of application
> > development, possibly even mentioning in the tutorial that the "apps
> > inside project" model it uses is followed for convenience and not
> > because it's the best/only way to work.
> >
> > Any thoughts or strong opinions one way or another?
>
> I'm heavily in favor of #2, documenting best practices of application
...

> I'm not too crazy about #1, if only because two options makes things
...

I pretty much concur with Adrian.

Anything more than a basic skeleton for an app is going to end up
being wrong more often than it is right. I can see your point
regarding adding default metadata, etc for an app - that sort of
addition might be worthwhile, but beyond simple additions of that
sort, I'm not sure I see much value in beefing up the template
projects.

Besides, about the only time I ever use startapp/startproject is when
I'm trying to debug a problem that someone has had with the tutorial.
I usually end up rolling my own or copying an existing project/app as
a starting point. If we're not going to eat the dogfood... :-)

I think #2 is where the effort is worthwhile. Actually, I would
broaden the scope a little. I don't know why, but there seems to be a
general misunderstanding about exactly what Django is. A lot of people
seem to treat Django as some sort of magical programming language on
its own, rather than a set of APIs and tools built on and for Python.

A fair number of the questions asked regularly on the users list could
be avoided if the point was made that Django code is just Python code
- if it isn't legal Python, it isn't going to work in Django, and any
nifty trick that works in Python will work in Django too. Using the
tutorials to reinforce the point that Django == Python would hopefully
reduce the frequency of these questions. Pointing out the possibility
of putting apps outside the project directory would be one good way to
exemplify the point.

Yours,
Russ Magee %-)

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to