Derek,

If you want something that display data but doesn't allow you to edit
it, you should check out the databrowse[1] contrib app. You just
register a model with it (like the admin) and it generates all the
pages. It lets users look through the data, but not edit it.

[1]http://docs.djangoproject.com/en/dev/ref/contrib/databrowse/

Hope that helps,
Alex

On Nov 10, 3:36 am, derek <gamesb...@gmail.com> wrote:
> Yes, the fields should not be editable in a "view".
>
> However, I do not see it as "a problem" - more as "a desirable
> feature".  There are any number of use cases for letting users see
> detailed record data but not be able (or not need, at that point in
> time) to edit it.   This feature is not meant to replace the existing
> ability to edit a record; but to add another option to the interface.
>
> It just seems strange to me that the admin interface allows for
> display of multiple records in a listing, but has no facility to
> display a complete, single record "view".  I do not want to have
> redevelop an admin-like interface just to allow for this option (given
> that is such a generic one).
>
> It is not clear from what you say - but I assume that it is not
> possible to readily alter the current admin interface to incorporate
> the generic views you refer to?  If it is, any guidance, or examples,
> along these lines would be appreciated.
>
> On Nov 9, 2:37 pm, Ludwik  Trammer <lud...@gmail.com> wrote:
>
> > I have a really hard time understanding what do you need, and I
> > suspect I'm not the only one. You are talking about the admin
> > interface, right? It displays a list containing all records, and when
> > you click on a record you go to a page that shows all fields for this
> > record (and lets you change their values). Isn't that exactly what you
> > want?
>
> > If the problem is that you don't want the fields to be editable,
> > because you just want to display read-only lists of records: re-think
> > using admin interface. It is meant specifically for managing records
> > on your website. Just use
> > "django.views.generic.list_detail.object_list" (display list of
> > records) and "django.views.generic.list_detail.object_detail" (display
> > detailed view of a single record) generic views:
>
> >http://docs.djangoproject.com/en/dev/ref/generic-views/#django-views-......
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to