Re: [Django Code] #13: Related objects interface should be tighter (edit_inline)

[Django Code]

#13: Related objects interface should be tighter (edit_inline)
------------------------------+---------------------------------------------
Reporter: adrian | Owner: nobody
Status: reopened | Component: Admin interface
Version: newforms-admin | Resolution:
Keywords: nfa-someday | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------+---------------------------------------------
Changes (by cecil):

* cc: oli...@obeattie.com, cml...@gmx.de, gary....@gmail.com,
m...@hex.no, t...@eggdrop.ch, dja...@apolloner.eu, bro...@gmail.com,
to...@lycos.nl, dan.po...@gmail.com, dja...@sparemint.com,
lnie...@eso.org, patrick...@divio.ch (removed)

Comment:

Well,as you pointed in your story, it's difficult to find a way from this
situation. I'm crossing fingers for everybody who is in this situation.
[http://blazingvidreviews.com/ Good Luck!]

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:44>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines

[Django Code]

#13: Related objects interface should be tighter (edit_inline)
------------------------------+---------------------------------------------
Reporter: adrian | Owner: nobody
Status: reopened | Component: Admin interface
Version: newforms-admin | Resolution:
Keywords: nfa-someday | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------+---------------------------------------------

Changes (by Patrick Lauber <patrick...@divio.ch>):

* cc: oli...@obeattie.com, cml...@gmx.de, gary....@gmail.com,
m...@hex.no, t...@eggdrop.ch, dja...@apolloner.eu, bro...@gmail.com,
to...@lycos.nl, dan.po...@gmail.com, dja...@sparemint.com,

lnie...@eso.org, to, patrick...@divio.ch (added)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:45>

[Django Code]

#13: Related objects interface should be tighter (edit_inline)

------------------------------------------+---------------------------------

Reporter: adrian | Owner: nobody
Status: reopened | Component: Admin interface
Version: newforms-admin | Resolution:

Keywords: nfa-someday nfa-changelist | Stage: Accepted

Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0

------------------------------------------+---------------------------------
Changes (by jakub_vysoky):

* keywords: nfa-someday => nfa-someday nfa-changelist

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:46>

[Django Code]

#13: Related objects interface should be tighter (edit_inline)

--------------------------------------+-------------------------------------
Reporter: adrian | Owner: barbuza
Status: new | Milestone: post-1.0

Component: Admin interface | Version: newforms-admin
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |

--------------------------------------+-------------------------------------
Changes (by barbuza):

* owner: nobody => barbuza
* status: reopened => new

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:54>

[Django Code]

#13: Related objects interface should be tighter (edit_inline)
--------------------------------------+-------------------------------------
Reporter: adrian | Owner: barbuza
Status: new | Milestone: post-1.0

Component: Admin interface | Version: SVN

Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------

Changes (by Alex):

* version: newforms-admin => SVN

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:55>

[Django Code]

#13: Related objects interface should be tighter (edit_inline)
--------------------------------------+-------------------------------------
Reporter: adrian | Owner: barbuza

Status: assigned | Milestone: post-1.0

Component: Admin interface | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------

Changes (by barbuza):

* cc: barbu...@gmail.com (added)
* status: new => assigned

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:56>

[Django Code]

#13: Related objects interface should be tighter (edit_inline)
--------------------------------------+-------------------------------------
Reporter: adrian | Owner: barbuza
Status: assigned | Milestone: post-1.0
Component: Admin interface | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------

Comment (by barbuza):

for STACKED editing, i think, we should use one of javascript libraries.
there will be tons of work without one of them.

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:57>

[Django Code]

#13: Related objects interface should be tighter (edit_inline)
--------------------------------------+-------------------------------------
Reporter: adrian | Owner: barbuza
Status: assigned | Milestone: post-1.0
Component: Admin interface | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0

Needs_better_patch: 1 |
--------------------------------------+-------------------------------------
Changes (by barbuza):

* needs_better_patch: 0 => 1

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:58>

[Django Code]

#13: Related objects interface should be tighter (edit_inline)
--------------------------------------+-------------------------------------
Reporter: adrian | Owner: barbuza
Status: assigned | Milestone: post-1.0
Component: Admin interface | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
--------------------------------------+-------------------------------------

Comment (by Frank Malina):

I've tested the diff, you enclosed.

One other problem is that when a new empty line is added, it should
automatically have a delete icon to remove the added node. It's needed in
case user added more nodes than needed or intended.

There is no draggable, as Wilson proposed for sorting. Draggables are
quite easy to do with JQuery and JQuery UI library. I guess JQquery is the
favorite library amongst Django people and core developers, so it makes
sense. There is some code that could be used:
http://www.isocra.com/2008/02/table-drag-and-drop-jquery-plugin/

Frank http://vizualbod.com

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:59>

[Django Code]

#13: Related objects interface should be tighter (edit_inline)
--------------------------------------+-------------------------------------
Reporter: adrian | Owner: barbuza
Status: assigned | Milestone: post-1.0
Component: Admin interface | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
--------------------------------------+-------------------------------------

Comment (by anonymous):

I'm running latest django svn trunk and I've applied inline-tabular.diff
patch.
I was getting a javascript syntax error and I've changed the 121 line in
django/contrib/admin/media/js/admin/InlineObjectsTabular.js to:
{{{
xmlhttp.open('POST', "delete-inline/"+name+'/'+id+'/', true);
}}}
But I can't see any change in the admin forms.
What should I do?

Thanks in advance.

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:60>

[Django Code]

#13: Related objects interface should be tighter (edit_inline)
--------------------------------------+-------------------------------------
Reporter: adrian | Owner: barbuza
Status: assigned | Milestone: post-1.0
Component: Admin interface | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
--------------------------------------+-------------------------------------

Changes (by anonymous):

* cc: flavio....@gmail.com (added)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:61>

[Django]

#13: Related objects interface should be tighter (edit_inline)

-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: closed | Milestone: post-1.0
Component: django.contrib.admin | Version: SVN
Resolution: fixed | Keywords: nfa-someday nfa-changelist

Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |

-------------------------------------------+--------------------------------
Changes (by anonymous):

* status: assigned => closed
* resolution: => fixed

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:62>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: closed | Milestone: post-1.0
Component: django.contrib.admin | Version: SVN
Resolution: fixed | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by anonymous):

a

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:63>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza

Status: reopened | Milestone: post-1.0
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist

Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Changes (by anonymous):

* status: closed => reopened
* resolution: fixed =>

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:64>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone: post-1.0
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Changes (by Guilherme M. Gondim <sem...@taurinus.org>):

* cc: sem...@taurinus.org (added)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:65>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone: post-1.0
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by patrickk):

about a year ago, the status was "This ticket is not fixed, but very close
;)".
any updates on this?

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:66>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone: post-1.0
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by benhasek219):

[http://six-pack-abs.0mbt.com/article/10/Does-Diet-Soda-Make-You-Fat%2C-
or-is-it-Really-Good-for-Weight-Loss%3F.html Does Diet Soda Make You Fat,
or is it Really Good for Weight Loss?]
the nasty chemicals, the gut-fattening high fructose corn syrup, and a
myriad of health problems caused by this carbonated cocktail worshipped by
those that don't care about their health or body. Surprisingly, many
people falsely believe that "diet" soda is in some way a good thing for
losing body fat.
Unusual bulges will always be distracting to the eyes.
In fact, I hear people all the time proudly state that they eat so healthy
and only drink diet soda.
Cardiovascular training helps us lose weight and get fit.
So let's set the record straight...

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:67>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone: post-1.0
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Changes (by anonymous):

* cc: step...@harobed.org (added)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:68>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza

Status: closed | Milestone: post-1.0
Component: django.contrib.admin | Version: SVN
Resolution: fixed | Keywords: nfa-someday nfa-changelist

Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------
Changes (by anonymous):

* status: reopened => closed
* resolution: => fixed

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:69>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza

Status: reopened | Milestone: post-1.0
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist

Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Changes (by apollo13):

* status: closed => reopened
* resolution: fixed =>

Comment:

anonymous having fun?!

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:70>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:

Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by juriejan):

i'm looking at implementing this. anyone made any progress that i can
possibly build upon? should i start a discussion on django-developers
about this?

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:72>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Changes (by juriejan):

* cc: juriej...@gmail.com (added)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:73>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by CollinAnderson):

Correct me if I am wrong, but there are already some implementations out
there using jQuery, and we just need to make our own implementation
without requiring a library.

http://www.arnebrodowski.de/blog/507-Add-and-remove-Django-Admin-Inlines-
with-JavaScript.html

http://www.djangosnippets.org/snippets/1053/ (Simon's Orderable inlines
using drag and drop with jQuery UI)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:74>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by juriejan):

That's the way it seems to me too. But I believe there is a whole
discussion on using too much Javascript in the standard shipment of
Django. It seems to me that this would be better suited for distribution
as a separate application.

Let's continue the discussion at [http://groups.google.co.za/group/django-
developers/browse_thread/thread/50dd66128b2f486f]

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:75>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by anonymous):

"That's the way it seems to me too. But I believe there is a whole
discussion on using too much Javascript in the standard shipment of
Django. It seems to me that this would be better suited for distribution
as a separate application. "

Well obviously django doesnt want to favor any js lib but on the other
hand it would be rather stupid to reinvent the wheel. I guess this is why
this issue is still open. Obiviously this is a bad circle. We want nice js
and ajax bells and whistles but we dont want to favor any js lib (even if
jquery is the best ;) the result? the admin will remain rigid. third party
admins like http://code.google.com/p/sorl-curator/ will take over.

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:76>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by James Wheare):

Um, hate to break it to you but... the admin already is a contrib app so
I'm not sure choosing a JS library would suggest any sort of core
endorsement of a library. It's possible to get too shackled to ideals of
impartiality sometimes. Occasionally you know... building things is good.
:)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:77>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by anonymous):

Not choosing a js lib just wastes human resource.

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:78>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Changes (by velmont):

* cc: velmont (added)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:80>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by test):

test

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:81>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Changes (by anonymous):

* cc: b...@usagebot.com (added)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:83>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Changes (by juriejan):

* cc: juriej...@gmail.com (removed)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:84>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Comment (by anonymous):

Who do I need to talk to if I want

to help implement this?
That would be me. I go by "coderanger" on IRC, and can be found there most

of the time.
[http://www.gln2008.com/ ed hardy]A (simple) ticket can be attached

to an (aggregate) ticket:
•to a milestone, as it is done now (display in the combobox only available

milestone tickets)
•to a master ticket (display in that combobox only available master

tickets)
It remains to be seen if an

(aggregate) ticket could itself be attached to another (aggregate)

ticket... A master ticket attached to a milestone makes seYou're quite
right - reworking the modules and

breaking down the tickets into different types seems a good solution, and

more flexible than simply 'bolting on' master tickets.
Master tickets should be children of Milestone tickets, but not other

Master tickets.

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:86>

Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups "Django updates" group.
To post to this group, send email to django-...@googlegroups.com.
To unsubscribe from this group, send email to django-update...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------
Comment (by anonymous):

Who do I need to talk to [http://www.guccishopping.com/ ed hardy]if I want

to help implement this?
That would be me. I go by "coderanger" on IRC, and can be found there most

of the time.

A (simple) ticket can be attached

to an (aggregate) ticket:
•to a milestone, as it is done now (display in the combobox only available

milestone tickets)
•to a master ticket (display in that combobox only available master

tickets)
It remains to be seen if an

(aggregate) ticket could itself be attached to another (aggregate)

ticket... A master ticket attached to a milestone makes sense.

You're quite right - reworking the modules and

breaking down the tickets into different types seems a good solution, and

more flexible than simply 'bolting on' master tickets.
Master tickets should be children of Milestone tickets, but not other

Master tickets.

--

Ticket URL: <http://code.djangoproject.com/ticket/13#comment:85>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------
Comment (by anonymous):

Who do I need to talif I want

to help implement this?
That would be me. I go by "coderanger" on IRC, and can be found there most

of the time.A (simple) ticket can be attached

to an (aggregate) ticket:
•to a milestone, as it is done now (display in the combobox only available

milestone tickets)
•to a master ticket (display in that combobox only available master

tickets) It remains to be seen if an

(aggregate) ticket could itself be attached to another (aggregate)

ticket... A master ticket attached to a milestone makes sense.

[http://www.cc1c.com/ micro bikini]You're quite right - reworking the

modules and

breaking down the tickets into different types seems a good solution, and

more flexible than simply 'bolting on' master tickets.
Master tickets should be
children of Milestone tickets, but not other

Master tickets.

--

Ticket URL: <http://code.djangoproject.com/ticket/13#comment:88>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------
Comment (by anonymous):

Who do I need to talif I want

to help implement this?
That would be me. I go by "coderanger" on IRC, and can be found there most

of thA (simple) ticket can be attached

to an (aggregate) ticket:
•to a milestone, as it is done now (display in the combobox only available

milestone tickets)
•to a master ticket (display in that combobox only available master

tickets)

[http://www.maslou.com/ louis vuitton]It remains to be seen if an

(aggregate) ticket could itself be attached to another (aggregate)

You're quite right - reworking the modules and

breaking down the tickets into different types seems a good solution, and

more flexible than simply 'bolting on' master tickets.
Master tickets should be children of Milestone tickets, but not other

Master tickets.

--

Ticket URL: <http://code.djangoproject.com/ticket/13#comment:87>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------
Comment (by anonymous):

Who do I need to talk to [http://www.guccishopping.com/ ed hardy]if I want

to help implement this?
That would be me. I go by "coderanger" on IRC, and can be found there most

of the time.

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:85>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza

Status: closed | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: fixed | Keywords: nfa-someday nfa-changelist

Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------

Changes (by anonymous):

* status: reopened => closed
* resolution: => fixed

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza

Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist

Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------
Changes (by anonymous):

* status: closed => reopened
* resolution: fixed =>

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:86>

[Django]

#13: Related objects interface should be tighter (edit_inline)

------------------------------------------------+---------------------------

Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist

Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 |
------------------------------------------------+---------------------------
Changes (by dokterbob):

* cc: mathijs@… (added)
* has_patch: 0 => 1

Comment:

So far, it seems that no work has been done on this issue for a long time.
Meanwhile, I am sure that it is still a feature that many users would like
to see integrated into the Django admin. Given that, by now, people have
made the wise decision to ship jQuery with the Django admin, it seems to
me as about time to start fixing this issue.

Currently, if `order_with_respect_to` is specifeid in a Model's Meta field
is specified, a cute `_order` field is indeed added to the Model's
database table. However (AFAIK because of the underscore), this field is
not represented at all in the Admin interface. This implies that - for now
- it is still easier to explicitly add some Integer ordering field to a
Model rather than using the much more elegant, available, but
disfunctional, API that ships with Django.

As fixing/completing this feature should be fairly easy for someone who's
used to getting into the debts of the (very scarcely documented)
Admin/Model internals, it might not even be too unrealistic to have this
fixed before 1.3 or the first point release after.

To make it a bit easier, I have made a start by providing this patch which
fixes at least the `get_ordered_objects` method of Model's `_meta`. This
causes the Admin to load a non-existant file `dom-drag.js` which should be
replaced by a jQuery equivalent thereof. Furthermore, the
InlineModelAdmin's formset should have it's `can_order` parameter set to
`True`, I believe, to allow for the ordering to get through to the Admin
in the first place.

Meanwhile, I have spotted the following tickets relating to this same
issue - parts of which I used for writing the - still very incomplete -
patch:
* #13296
* #9338
* #2137

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:87>

[Django]

#13: Related objects interface should be tighter (edit_inline)
------------------------------------------------+---------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 |
------------------------------------------------+---------------------------

Comment (by jezdez):

Which patch are you referring to?

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:88>

[Django]

#13: Related objects interface should be tighter (edit_inline)
------------------------------------------------+---------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday nfa-changelist
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 |
------------------------------------------------+---------------------------

Comment (by dokterbob):

@jezdez Apparently I could not attach my patch to the message itself. It
should have become clear in this last edit. :)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:89>

[Django]

#13: Related objects interface should be tighter (edit_inline)

-------------------------------------+-------------------------------------
Reporter: adrian | Owner: barbuza
Type: New | Status: reopened
feature | Component: contrib.admin
Milestone: | Severity: Normal
Version: SVN | Keywords: nfa-someday nfa-
Resolution: | changelist

Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 |

-------------------------------------+-------------------------------------
Changes (by lrekucki):

* type: defect => New feature
* severity: normal => Normal

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:90>

[Django]

#13: Related objects interface should be tighter (edit_inline)
-------------------------------------+-------------------------------------
Reporter: adrian | Owner: barbuza
Type: New | Status: reopened
feature | Component: contrib.admin
Milestone: | Severity: Normal
Version: SVN | Keywords: nfa-someday nfa-
Resolution: | changelist
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 |
-------------------------------------+-------------------------------------

Changes (by obeattie):

* cc: oliver@… (removed)

--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:91>