On 2/13/07, Rob Hudson <[EMAIL PROTECTED]> wrote: > I agree with another poster, adding FK and M2M and their options would > be a nice addition if there is room.
Might be worth doing up multiple sheets, kind of like YUI does with their components. > Is there any reasoning to when an admin class option is a list and > when it is a tuple? I tend to default to tuple since I don't want to > have to go look it up every time. Can admin options be standardized > to tuples across the board to make it easy? Not really. Anything you can do to a tuple (which is, basically, iterate over it, slice it and access specific items out of it) you can also do to a list. A tuple is just a little bit more efficient when you know you're dealing with something that isn't/shouldn't be mutable. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
