I can see how on occasion you might swap out one template for another, but its more a rarity (in my experience). I agree with Luke, in that templates are alsmot always specific. Why not help make them more readable and easier to use?
If you go along with the idea that template designers are not coders, then it makes more sense to give then names they understand. This idea should make it much more non-coder friendly. And as a coder myself, I have, after years of doing ERP coding and web ERP coding, come to the conclusion code can never to be too self documenting. object list means nothing without a specific context in which to place it. survey_list or person_list is immedialy more specific and thus more relevant and easier to understand. As to Toms response, I highlight the word VIEW. Generic View. Not Template. And yes this would make generic views more generic and templates more specific. Which is entirly the point. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
