Hi again Paulo, Ok. I'll also have a look at that.
I agree that the business logic should be in the views. However, it feels that we need a little more flexibility with the templates when things are truely just a presentation problem. When you have to start constructing your own dictionaries / lists it can start to get a bit of a mess. Lists rely on the order/index. So if you need to add another piece of data that you might have forgotten about you have to make sure you don't mess up the order/indexes. You can also use dictionaries, which can be slightly easier (once you have created a dictionary lookup tag!) but you still have a lot of messing about to do creating the dictionary in the first place. It feels that creating the data in this way misses out on a lot of the power of using ORM within the templates. Oh well. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
