Re: When to use admin, and when not to.

2009-05-27 Thread Sam Kuper
2009/5/27 Andy Mikhailenko > > User behaviour can be formalized as actions + objects. Some actions > span multiple objects. > Admin is a great tool that corresponds the *structure* of data. It > allows to view and edit all your base for great justice. Err, all your > database for zero cost. Out of

Re: When to use admin, and when not to.

2009-05-27 Thread Andy Mikhailenko
User behaviour can be formalized as actions + objects. Some actions span multiple objects. Admin is a great tool that corresponds the *structure* of data. It allows to view and edit all your base for great justice. Err, all your database for zero cost. Out of the box. Nice! However, "editing an ob

Re: When to use admin, and when not to.

2009-05-26 Thread Masklinn
On 26 May 2009, at 15:44 , Sieker Adi Jörg wrote: > On 26.05.2009, at 14:28, Sam Kuper wrote: > Also to actually get access to the > admin views, the user needs be flagged as a superuser (I as far as I > remember). > Staff, actually, superuser is another user class (one that gets all admin right

Re: When to use admin, and when not to.

2009-05-26 Thread Sam Kuper
Thanks so much for the comprehensive reply! All best, Sam 2009/5/26 Sieker Adi Jörg > > On 26.05.2009, at 14:28, Sam Kuper wrote: > > > 2009/5/26 Sieker Adi Jörg > > In my humble opinion. As soon as you mention users, the admin is the > > wrong tool. > > contrib.admin is for admin's and not f

Re: When to use admin, and when not to.

2009-05-26 Thread Sieker Adi Jörg
On 26.05.2009, at 14:28, Sam Kuper wrote: > 2009/5/26 Sieker Adi Jörg > In my humble opinion. As soon as you mention users, the admin is the > wrong tool. > contrib.admin is for admin's and not for users. > > Another take on it is: > - Anyone that creates an account on your site, doesn't get to

Re: When to use admin, and when not to.

2009-05-26 Thread Sam Kuper
2009/5/26 Sieker Adi Jörg > In my humble opinion. As soon as you mention users, the admin is the > wrong tool. > contrib.admin is for admin's and not for users. > > Another take on it is: > - Anyone that creates an account on your site, doesn't get to ses the > admin > - Anyone that you create an

Re: When to use admin, and when not to.

2009-05-26 Thread Sieker Adi Jörg
Hi, On 26.05.2009, at 12:17, Sam Kuper wrote: > 2009/5/26 Alex Gaynor >> It's not even an authorisation issue, it's that I'd be overiding >> nearly every method to make sure the behavior was what I wanted, >> and then I'd replace all the templates since I want everything the >> user sees

Re: When to use admin, and when not to.

2009-05-26 Thread Sam Kuper
2009/5/26 Alex Gaynor > It's not even an authorisation issue, it's that I'd be overiding nearly > every method to make sure the behavior was what I wanted, and then I'd > replace all the templates since I want everything the user sees to be > similarly themed, and at this point I've already rewri

Re: When to use admin, and when not to.

2009-05-25 Thread Alex Gaynor
On Mon, May 25, 2009 at 8:25 PM, Sam Kuper wrote: > 2009/5/26 Alex Gaynor > >> On Mon, May 25, 2009 at 7:51 PM, Sam Kuper >> wrote: >> >>> Suppose you were re-writing Facebook in Django. >>> >>> Would you handle the complex profile and privacy settings pages by: >>> >>> A) exposing the relevant

Re: When to use admin, and when not to.

2009-05-25 Thread Sam Kuper
2009/5/26 Alex Gaynor > On Mon, May 25, 2009 at 7:51 PM, Sam Kuper > wrote: > >> Suppose you were re-writing Facebook in Django. >> >> Would you handle the complex profile and privacy settings pages by: >> >> A) exposing the relevant admin pages to users, with careful auth to stop >> users from

Re: When to use admin, and when not to.

2009-05-25 Thread Alex Gaynor
On Mon, May 25, 2009 at 7:51 PM, Sam Kuper wrote: > Suppose you were re-writing Facebook in Django. > > Would you handle the complex profile and privacy settings pages by: > > A) exposing the relevant admin pages to users, with careful auth to stop > users from being able to access admin pages the

When to use admin, and when not to.

2009-05-25 Thread Sam Kuper
Suppose you were re-writing Facebook in Django. Would you handle the complex profile and privacy settings pages by: A) exposing the relevant admin pages to users, with careful auth to stop users from being able to access admin pages they shouldn't be able to. Obviously this would require much cus