Re: Admin coding guidelines order?

[Micky Hulse]

On Sat, Sep 17, 2011 at 7:14 PM, Micky Hulse  wrote:
> How's this for organization(?):

Bare bones example:



Note on comments:

Trying to follow similar guidelines for comments as found here:



I have always liked that style of "Section separators".

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

Re: Admin coding guidelines order?

[Micky Hulse]

On Sat, Sep 17, 2011 at 4:10 PM, Micky Hulse  wrote:
> But are what about the admin.py file?

How's this for organization(?):



I guess I am curious how other folks would go about organizing things. :)

Thanks!
Micky

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

Admin coding guidelines order?

[Micky Hulse]

Hello,

I follow the rules on this page for my models (and other files/code):



But are what about the admin.py file?

Sometimes my admin classes can get pretty cluttery (form,
display_on_top, prepopulated_fields, filter_horizontal, fieldsets,
methods, other).

Do any of ya'll have any tips on keeping the admin classes organized
and readable?

Thanks!
Micky

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