Hey Laundro, On Tuesday 05 September 2006 06:56, [EMAIL PROTECTED] wrote: > Do I need to create one big view.py that sends all relevant data to one > large template? (I'd imagine not). Is there a way to 'cascade' > view.py's, so that some sort of website-logic decision script can > decide which view.py should be called next?
I think the "website-logic decision script" you are looking for is your urls.py - write templates that include anchors, forms or requests that point to the urls specified in urls.py. That's where decisions are made as to which view function will be called. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
