Re: New branch: newforms-admin

2007-01-29 Thread Joseph Kocherhans
On 1/16/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > I'd like to take the clean route and move the admin definitions into a > separate file, or at least still in the models.py but not within the > models themselves. Of course, that's not as convenient as defining the > admin stuff directly

Re: New branch: newforms-admin

2007-01-23 Thread Robert Myers
> Excellent -- I'm excited that you're interested in helping out. The > best bet would be to submit patches against the newforms-admin, but > I'll give the caveat that I'm moving pretty quickly on this and may > duplicate your work. The last thing I want is for you to spend time on > a patch, only

Re: New branch: newforms-admin

2007-01-22 Thread Will McCutchen
Adrian Holovaty wrote: > I'd like to take the clean route and move the admin definitions into a > separate file, or at least still in the models.py but not within the > models themselves. Of course, that's not as convenient as defining the > admin stuff directly within the model, but another

Re: New branch: newforms-admin

2007-01-22 Thread Adrian Holovaty
On 1/22/07, James Bennett <[EMAIL PROTECTED]> wrote: > Joseph and I were kicking around some ideas over lunch today, and one > thing that seemed like a good idea was moving back to the old-school > 'admin as Meta attribute'. Under this scheme, django.contrib.admin > would define a default class

Re: New branch: newforms-admin

2007-01-22 Thread Adrian Holovaty
On 1/15/07, Robert Myers <[EMAIL PROTECTED]> wrote: > I would also like to help out. I wanted to fix a few issues with model > validation specifically for admin options. I'm not sure if you plan on > changing any of the existing options or how the options are called though. > If you are then I

Re: New branch: newforms-admin

2007-01-22 Thread Gary Wilson
James Bennett wrote: > Joseph and I were kicking around some ideas over lunch today, and one > thing that seemed like a good idea was moving back to the old-school > 'admin as Meta attribute'. Under this scheme, django.contrib.admin > would define a default class for model administration. This

Re: New branch: newforms-admin

2007-01-22 Thread James Bennett
On 1/16/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > I'd like to take the clean route and move the admin definitions into a > separate file, or at least still in the models.py but not within the > models themselves. Of course, that's not as convenient as defining the > admin stuff directly

Re: New branch: newforms-admin

2007-01-16 Thread Adrian Holovaty
On 1/16/07, James Bennett <[EMAIL PROTECTED]> wrote: I'm looking at this and the ModelAdminView class, and implied subclassing of it by the inner Admin class of models, seems a bit... weird. Is there a weird backwards-compatibility reason why something which will be a view (and whose base class

Re: New branch: newforms-admin

2007-01-16 Thread James Bennett
On 1/14/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: I've written up some thoughts and goals for this branch: http://code.djangoproject.com/wiki/NewformsAdminBranch I'm looking at this and the ModelAdminView class, and implied subclassing of it by the inner Admin class of models, seems

Re: New branch: newforms-admin

2007-01-15 Thread Robert Myers
I would also like to help out. I wanted to fix a few issues with model validation specifically for admin options. I'm not sure if you plan on changing any of the existing options or how the options are called though. If you are then I wont waste my time working on something that will change. If

Re: New branch: newforms-admin

2007-01-15 Thread patrickk
just 2 small things you may want to implement: 1. the opportunity to translate the apps - useful for the admin index-page. 2. for showing the permissions, use "app | model | Can ..." insted of "model | Can ..." - this is especially useful if one has the same model-names within different apps.

Re: New branch: newforms-admin

2007-01-14 Thread JMCameron
Hi Adrian, I noticed from the wiki on the NewformsAdminBranch that you are considering taking this "opportunity to add extra customization hooks to the admin site". One hook that I would like to see added is the ability to control the field grouping (and line breaks) for related objects. The

Re: New branch: newforms-admin

2007-01-14 Thread Honza Král
Hi, I would like to help with this one... I have already written the custom widget override (ticket #3292), which is reflected in form_for_model I also think it might be useful to implement a page for individual app /admin/app/ which would serve as some sort of portal for the given app (I have

Re: New branch: newforms-admin

2007-01-14 Thread Adrian Holovaty
On 1/14/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: I've created a newforms-admin branch, which will focus on integrating django.newforms with the Django admin site. I've written up some thoughts and goals for this branch: http://code.djangoproject.com/wiki/NewformsAdminBranch Adrian

Re: New branch: newforms-admin

2007-01-14 Thread Ilia Kantor
Could admin also recieve a piece of functionality to have multiple search forms in it ? Very often one wants to search by name, id, smth else. Such a common piece could be really helpful. Hi all, I've created a newforms-admin branch, which will focus on integrating django.newforms with

New branch: newforms-admin

2007-01-14 Thread Adrian Holovaty
Hi all, I've created a newforms-admin branch, which will focus on integrating django.newforms with the Django admin site. A branch is necessary here because it's a big change that will span multiple changesets and undoubtedly cause temporary breakage. I considered just making a separate