Colleen Owens wrote:
>>Did you read the line:
>>
>>Inline editing can be customised. rather than using
>>edit_inline=meta.TABULAR or meta.SOURCE, you can define a custom inline
>>editing mode. This is done by subclassing BoundRelatedObject?, and using
>>that class. eg edit_inline=HorizontalScroller?.
>>
>>You can look at the implemention of TabularBoundRelatedObject to see how
>>to do it. Basically, override the template_name() method IIRC.
>
>
> Oops, yeah, I noticed that line right after I sent my last message. So
> now I'm creating a subclass of TabularBoundRelatedObject in one of my
> own template files that just overrides template_name and includes this:
> NEWTABULAR = len(bound_related_object_overrides.keys())
> bound_related_object_overrides[NEWTABULAR] =
> NewTabularBoundRelatedObject
>
> Since I want to keep all code modifications in my own application code,
> how do I get the admin change_form template to see this code? Do I add
> my own change_form template that inherits from the admin change_form
> and just has an extra include statement?
>
> Thanks for all the help, Edgars and Robert.
>
> Colleen
The overrides stuff is just to allow TABULAR and STACKED to continue to
work, without meaning that the core django has a dependency on the admin
code.
As you are defining your own class, that shouldn't matter for you, you
can just use the class directly, eg
from path.to.custom.admin.code import MyBoundRelatedObject
class Whatever(Model):
parent = ForeignKey(edit_inline=MyBoundRelatedObject)
I really didn't document this very well at all. It would be great if you
could write a paragraph or two when you get this working, and submit it
for inclusion in the docs.
PS
Jacob is currently changing this code. So it might be that all this gets
broken in the near future, as the plan seems to be to abandon non-AJAX
edit inline AFAIK.
