> I'd recommend switching to something like ReportBug()
> (http://djangosnippets.org/snippets/2214/) - which is mail based, New Relic
> (http://www.newrelic.com) or using a better approach to store the
> tracebacks (maybe serialize to disk, use MongoDB etc). Also remember, that
> when storing
> Yep. Could you outline your plan of attack for this?
1) create "newadmin" project to be a dropin replacement for admin.
(Clone current admin and slowly replace features/trim dead code)
2) Split out filterspec functionality into newadmin.filter.
- Give it a nicer wrapper such that a
> If someone is willing to take this on then I'd be happy to provide some
> support by reviewing patches, giving feedback etc.
Cheers. Would you be willing to review code that swaps out entire
swathes of admin functionality?
--
You received this message because you are subscribed to the Google
> Getting "admin-like" functionality into the mainstream was one of the
> prime motivations behind the introduction of class-based generic
> views. Django's admin contains a number of neat features (like
> fieldsets, views with inline formsets, filtering and searching) that
> can be very easily
I'd like to propose a project to split out the table/list
functionality and the filtering functionality in the django admin into
a seperate contrib app. This is really core functionality which is
lacking from django (in terms of being locked to the admin app).
I believe this would be beneficial
The thing is that I believe django as a whole would benefit from this
kind of functionality. The whole point of custom managers is to add
functionality, not just to your app, but to every app that FKs against
your models.
In the case of contrib.auth, this functionality is really handy
spanning
out what it does, but
this would be a fantastic thing to have in templates where there is no
way to specify filtering.
On Sep 23, 9:26 pm, Aymeric Augustin
<aymeric.augus...@polytechnique.org> wrote:
> 2011/9/23 tWoolie <thomas.woolf...@student.adelaide.edu.au>:
>
> > I've
I've submitted a pull request (https://github.com/django/django/pull/
51) for an active() relatedmanager method on the models class. I
wanted to get some feedback from other devs about inclusion into
trunk. I've included a patch to the docs if you want more info.
--
You received this message
