Not clear on what you mean by "more robust views". Can you please elaborate?
Regarding the term "views", I do mean actually invoking the python function via the url routing system. I would settle for calling a regular python function that returns some html snippet but I think the existing views would just work fine. 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? Cheers, Sagi On Aug 1, 10:29 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 8/1/07, sagi s <[EMAIL PROTECTED]> wrote: > > > I realize that this is an option but it seems to me more natural to > > control the content from the template so a designer can build views > > using "lego-blocks", without having to tweak the view. > > You either want: > > 1. More robust views, or > 2. Some custom template tags which allow your template authors to > access the things they want to pull in. > > Using the term "views" here to refer to both "the Python function to > which the URL is routed" and "some piece of content I want in a > template" is also likely to end up in severe confusion... > > -- > "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 -~----------~----~----~----~------~----~------~--~---
