On Mar 8, 8:16 am, ajaishankar <ajai.shan...@gmail.com> wrote: > Thanks Viklap > > We have been doing a lot of ModelAdmin & ModelForm tweaking as > mentioned in those slides. > > But still kind of skeptical we should be opening up the admin to other > companies; and go through the gymnastics of restricting say a foreign > key lookup to just the data they are allowed to access etc. > > Ajai > > On Mar 7, 11:57 pm, vikalp sahni <vikalpsa...@gmail.com> wrote: > > > > > > > > > Hi, > > > Django Admin is nicely structured to give you lot of flixibility. > > > We have tweaked around admin using all possible features and with good > > mingling of MIDDLEWARE, AUTH_BACKENDS and STORAGE one can > > achive a lot of integrations and customizations. > > > have a look at these slides, it brings more amount of confidence to going > > forward > > with > > Django-Adminhttp://www.slideshare.net/lincolnloop/customizing-the-django-admin > > > <http://www.slideshare.net/lincolnloop/customizing-the-django-admin>Regards,//Vikalp > > > On Tue, Mar 8, 2011 at 11:19 AM, ajaishankar <ajai.shan...@gmail.com> wrote: > > > Hi > > > > We have a app built on Django, and have been using the admin to good > > > effect. > > > > Right now we want to open up the app to other companies: > > > > 1. They can log in, create *their* own users > > > 2. They can only see data that belongs to their company etc. > > > 3. Also in one part of the app, we expect a highly customized UI where > > > there is a lot of ajaxy image upload etc going on. > > > > I do know we can tweak the admin to restrict querysets etc. and also > > > override admin templates - but is admin preferable in this situation? > > > > Or is it better to treat all this as a front end web app, and start > > > work on fresh pages. > > > > Any pointers would be much appreciated.
Our approach has been to use the Admin - there is not *that* much tweaking required in Django to filter data, and the approach of writing a completely new interface is a lot more work. But we had that approach "built-in" from the start; you need to consider your situation and see how many extra changes are needed. In our situation there is also a lot of shared data/tables, and so it makes to have a common interface to access that. HTH Derek -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
