#2248: [patch] inline_models, replacement for edit_inline and core=True
--------------------------------+-------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Admin interface
Version: SVN | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 1 | Needs_better_patch: 0
--------------------------------+-------------------------------------------
Comment (by [EMAIL PROTECTED]):
I've been looking at the problem you're trying to solve and I must say
that while your patch would really solve it.
On the other hand, it feels like a hack. From the OO point of view, it
means defining how the base class is going to be used in each child class
inside the base class itself! I think all the options should be in the
child class. I'm not familiar with Django's internals but it would be much
more natural to have all this machinery defined in the foreign key.
Someone (sorry, don't have a ref) suggested adding an "edit_inline_here"
keyword in the foreign key, which would do the same thing.
While this might sound like nitpicking for the current example, it means
to worlds when you're trying to design a modular app. If you have a Person
class somewhere in your app and you want to extend it you should be able
to do so without modifying the base class.
--
Ticket URL: <http://code.djangoproject.com/ticket/2248#comment:14>
Django Code <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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
