Hi, At YPlan we've hacked in view permissions to the admin, exactly because of the reasons Markus talked about - it's the front end we've built for employees, done rather than building a proper process-based interface. I think it could just about be done in a third-party package (It might rely on a patchy.patch <https://github.com/adamchainz/patchy> call though), rather than incorporating it into Django - have you considered this? At this point we're all in preference of a better toolbox for building internal tools, as Markus is suggesting, rather than "improving" the admin.
Adam On Thursday, January 28, 2016 at 6:17:26 AM UTC, Markus Holtermann wrote: > > Hi Petr, all, > > I managed to find some time to look into your PR (updated link: > https://github.com/django/django/pull/5297) and the related issue: > https://code.djangoproject.com/ticket/8936 . > Also, related discussion: > https://groups.google.com/d/topic/django-developers/rZ5Pt9R94d4/discussion > and issues: https://code.djangoproject.com/ticket/820 and > https://code.djangoproject.com/ticket/17295 > > First of all, thank you for your your contribution and persistence. > > I think Django should provide an easy way to get a read-only view of your > data in the database. However, I don't really like the integration into > contrib.admin . As it stands now, people commonly use the admin as a front > end for their employees instead of building a proper process-oriented > interface. This may work to some degree but it's not uncommon that > developers need to fiddle with the internals of the admin to make specific > things work. Adding a read-only view to the admin would encourage people > even more to use the admin for reasons where they shouldn't. > > I'd prefer an approach on a different level where Django gains a proper > (de)serialization implementation. The implementation would e.g. leverage > content negotiation to define the output, e.g. JSON, XML, HTML, etc. > > What I'm pretty much saying is, I'd rather see a proper django.rest (or > whatever we wanna call it) instead of a feature on top of the convoluted > admin which provides only half of what people probably want and use. > > Cheers, > > /Markus > > On Wednesday, August 26, 2015 at 9:49:58 PM UTC+10, Petr Dlouhý wrote: >> >> Hello all, >> >> I am still waiting for some information about what should I do next to >> get this pulled into Django. Isn't here somebody willing to take a look at >> this? >> >> PR is at https://github.com/django/django/pull/5108 >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6c8a91c7-dff6-461f-97fb-f63c98f0f1f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
