One of the needs I have (and, I imagine, others too) is to be able to
display a view of a single record in a table. This is the case when
the record has many fields, not all of which are appropriate for (or
need to be) display in the normal list view.
What I need to know is: is this a "standard" feature in the admin
interface? If so, how do I go about activating it? If not, could
someone please explain how to extend the admin interface for this to
work?
On 6 Lis, 07:55, derek <gamesb...@gmail.com> wrote:
> One of the needs I have (and, I imagine, others too) is to be able to
> display a view of a single record in a table. This is the case when
> the record has many fields, not all of which are appropriate for (or
> need to be) display in the normal list view.
> What I need to know is: is this a "standard" feature in the admin
> interface? If so, how do I go about activating it? If not, could
> someone please explain how to extend the admin interface for this to
> work?
Do you mean displaying single record on change list?
You can try using search or filtering features for this.
The usual way that records get displayed is in a tabular list format.
This is suitable when a record only has a few fields; some tables
however
have many fields in them and so would need to be displayed "in full"
just
by themselves.
I am looking for a way to have a link to this "detail view" embedded
in each
line entry of the normal tabular list display - a type of "click here
for more
details" link. This would not form part of a search or query.
On Nov 7, 1:24 am, Tomasz Zieliński <tomasz.zielin...@pyconsultant.eu>
wrote:
> On 6 Lis, 07:55, derek <gamesb...@gmail.com> wrote:
> > One of the needs I have (and, I imagine, others too) is to be able to
> > display a view of a single record in a table. This is the case when
> > the record has many fields, not all of which are appropriate for (or
> > need to be) display in the normal list view.
> > What I need to know is: is this a "standard" feature in the admin
> > interface? If so, how do I go about activating it? If not, could
> > someone please explain how to extend the admin interface for this to
> > work?
> Do you mean displaying single record on change list?
> You can try using search or filtering features for this.
> I am not sure what you mean by "on change list"?
> The usual way that records get displayed is in a tabular list format.
> This is suitable when a record only has a few fields; some tables
> however
> have many fields in them and so would need to be displayed "in full"
> just
> by themselves.
> I am looking for a way to have a link to this "detail view" embedded
> in each
> line entry of the normal tabular list display - a type of "click here
> for more
> details" link. This would not form part of a search or query.
> On Nov 7, 1:24 am, Tomasz Zieliński <tomasz.zielin...@pyconsultant.eu>
> wrote:
> > On 6 Lis, 07:55, derek <gamesb...@gmail.com> wrote:
> > > One of the needs I have (and, I imagine, others too) is to be able to
> > > display a view of a single record in a table. This is the case when
> > > the record has many fields, not all of which are appropriate for (or
> > > need to be) display in the normal list view.
> > > What I need to know is: is this a "standard" feature in the admin
> > > interface? If so, how do I go about activating it? If not, could
> > > someone please explain how to extend the admin interface for this to
> > > work?
> > Do you mean displaying single record on change list?
> > You can try using search or filtering features for this.
> On 8 Kasım, 08:44, derek <gamesb...@gmail.com> wrote:
> > I am not sure what you mean by "on change list"?
> > The usual way that records get displayed is in a tabular list format.
> > This is suitable when a record only has a few fields; some tables
> > however
> > have many fields in them and so would need to be displayed "in full"
> > just
> > by themselves.
> > I am looking for a way to have a link to this "detail view" embedded
> > in each
> > line entry of the normal tabular list display - a type of "click here
> > for more
> > details" link. This would not form part of a search or query.
> > On Nov 7, 1:24 am, Tomasz Zieliński <tomasz.zielin...@pyconsultant.eu>
> > wrote:
> > > On 6 Lis, 07:55, derek <gamesb...@gmail.com> wrote:
> > > > One of the needs I have (and, I imagine, others too) is to be able to
> > > > display a view of a single record in a table. This is the case when
> > > > the record has many fields, not all of which are appropriate for (or
> > > > need to be) display in the normal list view.
> > > > What I need to know is: is this a "standard" feature in the admin
> > > > interface? If so, how do I go about activating it? If not, could
> > > > someone please explain how to extend the admin interface for this to
> > > > work?
> > > Do you mean displaying single record on change list?
> > > You can try using search or filtering features for this.
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:
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:
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.
> 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:
> 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.
> 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:
|
