On 8 jan, 23:56, Matias Surdi <matiassu...@gmail.com> wrote:
> Great!!
>
> I think that the _meta attribute will be enough. I think that if I
> define a method on the base model of all my models something like
> get_fields() it could then return a list of the fields by accessing
> self._meta.fields, and this get_fields should be accessible from
> templates,shouldn't it?.
Yeps, but it has a couple drawbacks IMHO. One of them is that it
wouldn't work on other models. Another one is that it makes all of
your models dependant on a same base class for no good (semantic)
reason. Inheritance is vastly overrated IMHO, and one of the nice
points with Python is that it doesn't force you into "purist" OO when
it doesn't make sense. As far as I'm concerned, I'd make get_fields()
a plain function, so you don't have to inherit from YourModelBase to
make use of it. I don't see any need for polymorphic dispatch here so
better to KISS. And if you found a need for polymorphism, it could
easily be implemented using a custom __magicmethod__, so the generic
get_fields function would either call youmodel.__get_fields__() if
implemented or fall back to the default generic behaviour. But I
really doubt you'll find any use case for such a mechanism !-)
wrt/ using this get_fields function, one simple solution I already
mentionned would be to use a dedicated view. Another one - perhaps
more "reusable" is a simple template filter:
<ul>
{% for field in model|get_fields %}
<li><b>{{ field.name }} :</b> {{ field.value }}</li>
{% endfor %}
</ul>
HTH
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
