Thanks Shawn - but James' talk is exactly what got me into this
mess :-)
I'm aware of the possibility of specifying the model to be used as a
default kw arg in views etc. But I want all my models to become 'owner
aware'.
http://code.google.com/p/django-granular-permissions/ approaches the
model's
Check out James Bennett's DjangoCon 2008 talk on reusable apps. He goes into
some detail on how he made django-registration in such a way that it wasn't
necessary to require a specific model in order for it to work. I haven't
implemented anything this reusable myself so I can't really give you
Hi all,
Maybe I'm asking the wrong questions, maybe I'm asking the impossible,
maybe I need to do the hard thinking myseld. Anyway: here's my
problem.
We have a bunch of projects (about 4 big customers), some of which
have significant overlap. The current approach is copy/paste,
supported by
3 matches
Mail list logo