James Bennett wrote:
> On 8/17/06, Gary Wilson <[EMAIL PROTECTED]> wrote:
> > IMO, the dependency checking is the easy part. In the README or
> > something, I say MyCoolApp requires the admin app. It's the
> > configuration settings of the admin app that's hairy.
>
> That's what application docu
On 8/17/06, Gary Wilson <[EMAIL PROTECTED]> wrote:
> IMO, the dependency checking is the easy part. In the README or
> something, I say MyCoolApp requires the admin app. It's the
> configuration settings of the admin app that's hairy.
That's what application documentation is for. In theory it's
On Wed, 2006-08-16 at 22:36 -0700, Gary Wilson wrote:
> James Bennett wrote:
> > The more I think about it, the more I like the idea of using imports
> > in __init__.py to specify an application's dependencies; the thing
> > that'd make it especially nice would be some method -- either
> > convent
James Bennett wrote:
> The more I think about it, the more I like the idea of using imports
> in __init__.py to specify an application's dependencies; the thing
> that'd make it especially nice would be some method -- either
> conventional or built straight in to Django -- of checking for
> "impor
James Bennett wrote:
> On 8/13/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > The Lawrence guys have mentioned on this list previously that they have
> > many different applications they pull together in various projects.
>
> :)
>
> If we couldn't modularize, we wouldn't be able to sell dif
On 8/13/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> The Lawrence guys have mentioned on this list previously that they have
> many different applications they pull together in various projects.
:)
If we couldn't modularize, we wouldn't be able to sell different
"editions" of Ellington.
Not wanting to get overly involved, but I just want to put my 2p in on
this.
Todd O'Bryan wrote:
> 1. Allow people to set a prefix for each app in the settings.py file.
> This would basically tell the app what URLs that are mapped to it
> start with, and views and templates inside the app could u
On Sun, 2006-08-13 at 01:15 -0700, [EMAIL PROTECTED] wrote:
> > Malcolm Tredinnick wrote:
> > One point of view (mine!) is that if an application can't play nicely
> > with other applications and wants to do its own authentication, etc,
> > then it's not an application, it's a whole other project.
On Sat, 2006-08-12 at 22:29 -0700, Gary Wilson wrote:
> Malcolm Tredinnick wrote:
> > One point of view (mine!) is that if an application can't play nicely
> > with other applications and wants to do its own authentication, etc,
> > then it's not an application, it's a whole other project. The pro
> Malcolm Tredinnick wrote:
> One point of view (mine!) is that if an application can't play nicely
> with other applications and wants to do its own authentication, etc,
> then it's not an application, it's a whole other project. The project
> developer should have complete control over what the
Malcolm Tredinnick wrote:
> One point of view (mine!) is that if an application can't play nicely
> with other applications and wants to do its own authentication, etc,
> then it's not an application, it's a whole other project. The project
> developer should have complete control over what the po
Malcolm Tredinnick wrote:
> I'm not a fan of infinite flexibility as solutions for undefined future
> problems, so it's good that you've put in some specific cases you've
> encountered. Food for thought here.
+1 on that.
All these suggestions are going to make Django much fatter. It will
make th
On Wed, 2006-08-02 at 22:41 -0700, Gary Wilson wrote:
> Malcolm Tredinnick wrote:
> > > Or maybe we don't need any of this and I'm just being overly anal
> > > retentive.
> >
> > Not at all. Particularly as people start trying to write more Django
> > applications that are designed to be sharable
Malcolm Tredinnick wrote:
> > Or maybe we don't need any of this and I'm just being overly anal
> > retentive.
>
> Not at all. Particularly as people start trying to write more Django
> applications that are designed to be sharable beyond their immediate
> development group, we are going to see mo
Hey Bill,
OK, maybe it's just because it's early in the morning or because I'm a
bit stupid, but I'm not sure that I am understanding what you are
suggesting in some cases here. A few requests for clarification below...
On Wed, 2006-08-02 at 21:39 +0100, Bill de hÓra wrote:
> Malcolm Tredinnick
Malcolm Tredinnick wrote:
> Hi Todd,
>
> On Sat, 2006-07-29 at 19:42 -0400, Todd O'Bryan wrote:
>> 3. Develop some kind of explicit way that apps can declare
>> dependencies on other apps so that apps can just be dropped in with
>> any dependencies, their prefixes set, and they be good to go
Malcom,
> This is still work in progress. Unfinished as yet. I don't think the tag
> exists yet, but the django.core.urlresolvers.reverse() and
> django.db.models.permalink() methods are part of this.
Thanks, I check this out
> TEMPLATE_DIRS is for project-wide templates, so I'm not sure why
On Jul 29, 2006, at 8:18 PM, Malcolm Tredinnick wrote:
>> 1. Allow people to set a prefix for each app in the settings.py file.
>> This would basically tell the app what URLs that are mapped to it
>> start with, and views and templates inside the app could use this
>> when they want to create int
Assuming that the reverse url mappings is taken care of I see two things
one may want to define per app. configuration and dependencies
There are usually two kinds of configuration settings an app may need.
Required ones that the user must set for the app to work, and optional
ones for which s
On Sat, 2006-07-29 at 19:49 -0500, Martin Glueck wrote:
> Malcom,
>
> I'm pretty new to django, so please forgive me if I missed something.
>
> > However, that doesn't take care of the reverse URL mapping, as you
> > indicate above. Work on that area is being done by Adrian with his
> > reve
Malcom,
I'm pretty new to django, so please forgive me if I missed something.
> However, that doesn't take care of the reverse URL mapping, as you
> indicate above. Work on that area is being done by Adrian with his
> reverse URL mapping stuff (there have been some commits on this
> recently
Hi Todd,
On Sat, 2006-07-29 at 19:42 -0400, Todd O'Bryan wrote:
> As our application is growing larger, we're noticing some issues with
> coupling and the modularity of apps.
>
> In particular, how plugable are apps supposed to be? It's clear that
> at the
As our application is growing larger, we're noticing some issues with
coupling and the modularity of apps.
In particular, how plugable are apps supposed to be? It's clear that
at the top level, a project should be able to access all of its
parts, but it seems like it should b
23 matches
Mail list logo
