Google Groups Home
Help | Sign in
Message from discussion Default application layout, project/app distinction and encouraging best practices
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
James Bennett  
View profile
 More options Jul 9 2007, 9:14 am
From: "James Bennett" <ubernost...@gmail.com>
Date: Mon, 9 Jul 2007 08:14:42 -0500
Local: Mon, Jul 9 2007 9:14 am
Subject: Re: Default application layout, project/app distinction and encouraging best practices
On 7/9/07, Marty Alchin <gulop...@gamemusic.org> wrote:

> I don't know if this is what Adrian was referring to, but I would
> think an ideal "project" would be nothing more than settings.py,
> urls.py (which might be split into multiple files), a set of templates
> and static media content. Essentially, in addition to models, every
> app would be written to have generic views, which can be dropped into
> any environment, provided the proper dependencies are provided.

That's pretty much what I've been doing for a good long while now;
djangosnippets.org, for example, is a project that has a settings
file, root URLConf and templates, and everything else lives inside the
apps it uses.

The biggest hurdle I've seen a lot of people hit is the "how do I have
a home page" question; some folks even go so far as to dedicate an
application to that, which I personally think is overkill, but it'd be
nice if we're going to write up best practices to document ways of
tackling that problem.

--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2008 Google