hugo wrote: >>Either way, the admin does neither thing today. It seems to >me that >>situations like this would happen regularly and would be an >excellent >>candidate for inclusion in the admin. All the information >required to >>create the interface already exists in the model definitions. > > > In what is that what you want different from edit_inline=meta.TABULAR > or edit_inline=meta.STACKED? > > Ok, the one problem those two have: in Django trunk they only support > editing one level of hierarchy. But with the new_admin branch, I think > that should be solved, too. > > bye, Georg > >
This does not work in the new-admin branch, because any sane fix for this (fully recursive manipulators) should be done after core fields die. As new-admin is meant to be a backwards compatible branch (so that regressions can be easily spotted), I haven't removed core fields yet. Also, it remains to be seen what will need to be done for eg paging for inline edited objects. At the moment, it is assumed that all the data will be loaded at once. Robert
