GSOC: Turn contrib.admin into a customizable management interface

2015-03-24 Thread tyrion-mx
Discussing on #django-dev with FunkyBob and others I concluded that refactoring contrib.admin to become a generic management interface (and not a model-centric one as it is now) could be a good thing, so I started a project proposal. It still a draft and I hope to complete it in time, anyway I w

Re: GSOC: Turn contrib.admin into a customizable management interface

2015-03-24 Thread tyrion-mx
On Tuesday, March 24, 2015 at 11:48:59 PM UTC+1, Curtis Maloney wrote: > > Let's not get bogged down in minutiae just yet :) > > How to implement a grid and what level of browser support is something > that can be threshed out in the process. > I agree I love the idea of a Dashboard with custo

Re: rethinking raw_id_fields

2010-09-30 Thread tyrion-mx
I've tried implementing Autocomplete for the admin using jQuery (new) Autocomplete, here's the code: http://bitbucket.org/tyrion/django and here's a live demo (without css for the autocomplete, so it looks kinda ugly): http://djangoac.tyrion.mx/admin/ login with test/test. Let me know what you thi

Using jQuery.noConflict() instead of jQuery.noConflict(true) in contrib.admin

2010-10-22 Thread tyrion-mx
1) contrib.admin places jQuery in its own namespace `django.jQuery`. In this way other jQuery instances should not conflict with it. 2) It also removes the dollar sign AND the `jQuery` object from the global scope. *I think* removing the `jQuery` object is not necessary because it *should* not con

Re: Using jQuery.noConflict() instead of jQuery.noConflict(true) in contrib.admin

2010-10-23 Thread tyrion-mx
On Oct 22, 10:37 pm, Chuck Harmston wrote: > Per the jQuery docs , plugins > should *not* directly reference the jQuery object; they should do it in a > scope-controlled closure executed at creation with jQuery passed to it as a > parameter. This way, pl

Consider allowing customization of ModelForm's init parameters in contrib.admin

2014-01-15 Thread tyrion-mx
I'd like to be able to customize the parameters that gets passed to the form used in all the views of the ModelAdmin. It seems that there is currently no way to do it. A very common scenario in which this could be useful is to provide a default value for an author/user field of a model. For exam