I'm new to Django and have been trying to read up on generic views and sessions. I might be missing something, so please correct me as needed.
The a value (a callable) in the 'extra_context' dict passed to a generic view (like django.views.generic.list_detail.object_list) can be used to computed the value of a tag: http://www.djangoproject.com/documentation/generic_views/#django-views-generic-list-detail-object-detail I think using TEMPLATE_CONTEXT_PROCESSORS (all applications?) and 'context_processors' (per application - think decoupling applications/ portability) are ways of adding tags. BTW, my settings.py didn't have TEMPLATE_CONTEXT_PROCESSORS - I think Django settings are usually explicitly set to their defaults. If this is normal, it might trip up newbies like me. The more I read about and experiment with Django, the more I find it well designed. However, the 'extra_context' function seemed less useful to me because it didn't have an HttpRequest, which could safely be ignored. Then I realized, it's functionally a subset of what 'context_processors' (the arg. to generic views), but lack the request, and hence, a way of accessing session vars, POST vars, and other states. Would it be unreasonable to have these functions accept a HttpRequest object? Another way to look at it would be: should the callable aspect of 'extra_context' be removed since it's redundant? thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
