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 extension from the other side: it has a Permission class with content_type/id pointers to the relevant object. Unfortunately permissions are not checked/handed out automatically, but at least this solves the model problem to some extend. Will keep everyone posted, I'm not quite there yet... help is very welcome. On Feb 22, 2:36 am, Shawn Milochik <sh...@milochik.com> wrote: > 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 much, > but you could do worse than checking out the work of one of the core > developers of Django. > > http://www.youtube.com/watch?v=A-S0tqpPga4 > > In addition, the actual app is here, for your reading pleasure: > > http://bitbucket.org/ubernostrum/django-registration/ > > Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
