[Django] #33776: django-admin inline should not be append but prepend

4 views
Skip to first unread message

Django

unread,
Jun 10, 2022, 12:24:36 AM6/10/22
to django-...@googlegroups.com
#33776: django-admin inline should not be append but prepend
-------------------------------------+-------------------------------------
Reporter: Ritik | Owner: nobody
Soni |
Type: | Status: new
Uncategorized |
Component: | Version: 4.0
contrib.admin |
Severity: Normal | Keywords: django-inline admin
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 1 |
-------------------------------------+-------------------------------------
![image](https://user-
images.githubusercontent.com/47344024/172989144-55eb2368-fe43-4004-88b4-1f2c7e3551f9.png)

Problem:- this is so uncomfortable if inline has 1k instances then the
user has to scroll down.

Solution:-
1. so when we press add more inline (button) it should append an inline
instance at the starting in the fieldset.
2. that button also should be in the starting of fieldset
[[Image(https://user-
images.githubusercontent.com/47344024/172989144-55eb2368-fe43-4004-88b4-1f2c7e3551f9.png)]]

--
Ticket URL: <https://code.djangoproject.com/ticket/33776>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jun 10, 2022, 12:25:25 AM6/10/22
to django-...@googlegroups.com
#33776: django-admin inline should not be append but prepend
-------------------------------------+-------------------------------------
Reporter: Ritik Soni | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.admin | Version: 4.0
Severity: Normal | Resolution:

Keywords: django-inline admin | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Description changed by Ritik Soni:

Old description:

> ![image](https://user-
> images.githubusercontent.com/47344024/172989144-55eb2368-fe43-4004-88b4-1f2c7e3551f9.png)
>
> Problem:- this is so uncomfortable if inline has 1k instances then the
> user has to scroll down.
>
> Solution:-
> 1. so when we press add more inline (button) it should append an inline
> instance at the starting in the fieldset.
> 2. that button also should be in the starting of fieldset
> [[Image(https://user-
> images.githubusercontent.com/47344024/172989144-55eb2368-fe43-4004-88b4-1f2c7e3551f9.png)]]

New description:

Problem:- this is so uncomfortable if inline has 1k instances then the
user has to scroll down.

Solution:-
1. so when we press add more inline (button) it should append an inline
instance at the starting in the fieldset.
2. that button also should be in the starting of fieldset
[[Image(https://user-
images.githubusercontent.com/47344024/172989144-55eb2368-fe43-4004-88b4-1f2c7e3551f9.png)]]

--

--
Ticket URL: <https://code.djangoproject.com/ticket/33776#comment:1>

Django

unread,
Jun 10, 2022, 3:03:38 AM6/10/22
to django-...@googlegroups.com
#33776: django-admin inline should not be append but prepend
-------------------------------------+-------------------------------------
Reporter: Ritik Soni | Owner: nobody
Type: Uncategorized | Status: closed
Component: contrib.admin | Version: 4.0
Severity: Normal | Resolution: wontfix

Keywords: django-inline admin | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):

* status: new => closed
* resolution: => wontfix


Comment:

This would be quite a disruptive change, and additional ModelAdmin options
to avoid that wouldn't be worth the complexity I'd think.

I think by the time you have 1K+ inlines you need to be considering a
custom widget, or a custom view+template entirely. (On the old principle
that the admin is not your application...)

--
Ticket URL: <https://code.djangoproject.com/ticket/33776#comment:2>

Reply all
Reply to author
Forward
0 new messages