On 10/22/07, DjangoFett <[EMAIL PROTECTED]> wrote: > > I was hoping for more of a tree structure of extensions...
Note that extends can be chained. Using your example: You start with index.html that defines all the blocks you want to customize, as you have it now. Then, in index_title, you extend index and customize the tag_title block. Then, perhaps in index_body, you extend index_title (which has already customized tag_title), and customize block_header and block_body. Then, perhaps in index_footer, you extend index_body and customize block_footer. At that point all your blocks have been customized and your view specifies index_footer as the template to load, which in turn points to index_body, which in turn refers to index_title, which finally gets back to the base index template. Now this particular sequence of extensions for customization may not make much logical sense, but the point is you do not have to override/customize everything in the base template at once. You can chain your extensions. And by creating different extenders for the same base, create a tree of extensions. Not sure if that's the kind of tree you were looking for, though. Hoping this clarifies more than it muddies, Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
