- jQuery: Inlines are written as a jQuery plugin, DateTime and i18n are written without jQuery. The version of jQuery included is 1.4.2, which is ~3 years old. Do we want to have jQuery in this project? I think Django should include it, as it helps solve a lot of browser inconsistencies and is familiar to all JS devs. But if so, we should try to keep it up to date.
I'm eager to start working on pull requests for some of these changes (smaller first) but I wanted to take the pulse of django-developers first and see how they felt about it.
Django namespaces it's jquery under django.jquery, there should be no issue including an up2date version for your projects. Django probably will never keep up with jquery's release cycle.
I can vouch for this. It would be nice to keep it more up-to-date, but it is namespaced in a way that keeps it from bother other parts of the code that require a more modern version of jQuery. I'm currently using 1.7.x in my admin alongside Django's jQuery 1.4 version.
Agreed that this code is not a good as it could be. Having created a custom admin on top of admin_tools, I've come across a lot of pain points and have slowly (more slowly than I'd like) been refactoring bits of the admin JS into something that's more extensible.
As for your actual idea, I'd have to see it to fully understand what you're proposing here. Could you mock up some pseudo code that shows what you're trying to accomplish? It doesn't need to be complex, just something that shows the order of execution using comments and what would be called.