> The other approach I've seen from James Bennett's blog, is to create a
> template tag to retrieve model data generally. This works too, but it
> feels like it's more legwork that should be required.
We ran into this problem on a site we just launched. We tried several
approaches but ultimately went with templatetags. Our most involved
case was where a page contained one or more boxes of information which
needed to be populated based on some moderately complex rules of user
membership level, object premium level, object type, subject category,
etc. At the template level it looked deceptively simple:
{% selector <selector_name> as <var_name> %}
Behind the scenes, this fetched a rule set, determined the matching
objects, cached the result, and returned a dict of arrays of objects.
Sigh. The client got exactly what they wanted (in fact, demanded) but
they ultimately descended into choice overload and fell back to a
simple override scheme where they simply gave a list of objects for
each box. Getting the selector code and admin interface right took
many hours, but what they actually ended up using could have been
coded in 30 minutes. Meh.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
