Thanks. On #1, there is already similar information in the class (such as the overall feed description, url, etc...
#2 makes sense though. mike chambers Rajesh Dhawan wrote: > On May 1, 2:11 pm, Mike Chambers <[EMAIL PROTECTED]> wrote: >> I am using the feed api, and it works well. However, i was curious why >> the title and description fields are specified via templates, and not >> just as a property of the feed class? > > Two reasons that I can think of: > > 1. The title and description are for final consumption of the feed's > user. So, their right place is in the template layer. That's similar > reasoning to why you don't build your entire HTML inside your Python > view code but rather in your templates. > > 2. It allows you to use templatetags and filters on the title and > description fields. For example, you could strip HTML tags from your > description value, make it include only the first 10 words, make it > include a combination of fields from a model instead of just one > field. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
