On Wed, Apr 30, 2008 at 9:22 AM, Rajesh Dhawan <[EMAIL PROTECTED]>
wrote:

> On Apr 30, 4:39 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
> > As per the NewFormsAdmin Branch -
> http://code.djangoproject.com/wiki/NewformsAdminBranch
> > - there is a proposal convention that reads as follows:
> >
> > """A proposal convention: Specifying all admin options in a file
> > called admin.py, and import it in the __init__.py file of your
> > application module to do the registering during the initialization."""
> >
> > It seems that this proposed conversion is not in place yet.
>
> Nothing stops you from using that convention, actually. Have you tried
> it?
>

I was going to ask the same thing.  Why do you say the convention isn't in
place?  It is, in fact, the one I used when migrating my own app to
newforms-admin.  It woks fine except for occasionally tripping across:

http://code.djangoproject.com/ticket/6776

which Brian Rosner has recently posted a patch for.  He's interested in
feedback, so if this is the problem you are having with the convention, it
would be helpful to for you to give the patch a try and report results.

As for where to post the question, you picked the right list.  You might
want to provide feedback to Brian on the patch in the thread he started on
the dev list, but usage questions are always best started on the user's
list.

Karen

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to