Re: Status update on newforms-admin branch

2007-02-05 Thread David Larlet
2007/2/4, Russell Keith-Magee <[EMAIL PROTECTED]>: > > The *Inline classes need not just be data containers - they could > contain all the rendering information for handling their own display, > and the display of the subforms for each related object - and if this > is the case, they can be used b

Re: Status update on newforms-admin branch

2007-02-03 Thread Russell Keith-Magee
On 2/3/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > Regarding "edit inline," a couple of decisions need to be made. Ticket > #2248 (http://code.djangoproject.com/ticket/2248) has an interesting > suggestion: you define the inline stuff within the admin class. I'll > copy and paste from that

Re: Status update on newforms-admin branch

2007-02-03 Thread sansmojo
I could also see a use for this. Also, it would be nice to specify that at least one instance of the inline object be required. With the above example, when adding a Kingdom, at least one (or however many specified) Phylums would be required. A common use for this would be a person model, with

Re: Status update on newforms-admin branch

2007-02-02 Thread gabor
Adrian Holovaty wrote: > > I've > also taken the opportunity to refactor some admin-specific options -- > raw_id_admin and prepopulate_from -- so that they're defined in the > "class Admin" rather than in the model fields themselves. with this change to the raw_id_admin, what is the recommended

Re: Status update on newforms-admin branch

2007-02-02 Thread Rob Hudson
> I agree this approach is a huge improvement over the current syntax, > but I wonder whether it can be expanded even more. Instead of > dictionaries, let's use objects: Woah... inline that is specified by objects that can be subclasses? I'll have to wrap my head around that one. Would it be pos

Re: Status update on newforms-admin branch

2007-02-02 Thread oggie rob
On Feb 2, 12:01 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote: > The Jan. 31 deadline for merging the newforms-admin has passed, so I > thought I'd give a status update: Kudos on these changes (& newforms, of course). I really like that admin is now as "legit" as regular forms for public views

Status update on newforms-admin branch

2007-02-02 Thread Adrian Holovaty
The Jan. 31 deadline for merging the newforms-admin has passed, so I thought I'd give a status update: I'm really excited about the changes made so far in this branch. In a nutshell, the way admin options are specified has gotten *much* more flexible, resulting in easier and more powerful customi