On 8/1/07, sagi s <[EMAIL PROTECTED]> wrote: > Not clear on what you mean by "more robust views". Can you please > elaborate?
Write views which select more data. > Regarding custom template tags, I guess I expect many users to want to > use django this way, so I think that having a "load_view" template > element would be useful. Don't you agree? Not really, because this sort of thing is precisely what custom template tags are for. Think of the view as the primary "thing" that happens when a user hits a particular URL, and focus the view on that thing. Let's take a simple example: a news site. Now, the detail page for a story on the news site obviously needs to focus on one particular thing: retrieving and returning the story. But there are many other things you'd probably want to do as part of the presentation of that story, including displaying a list of latest stories published, a list of comments associated with the story, etc., etc. Because they're aspects of how the "thing" -- the story retrieved by the view -- is presented, they belong in the presentation layer and should be handled by template tags, not by some system for going and hitting huge numbers of views (which, by definition, would involve corresponding numbers of full request/response cycles -- a horribly inefficiency) just to build up what is, essentially, presentation. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
