On 10 août, 21:52, Kayode Odeyemi <drey...@gmail.com> wrote: > On Wed, Aug 10, 2011 at 6:57 PM, bruno desthuilliers < > > bruno.desthuilli...@gmail.com> wrote: > > On 10 août, 16:30, Tom Evans <tevans...@googlemail.com> wrote: > > > Now for the third solution: write your own template tag. Not > > necessarily required, but that's often the best solution wrt/ > > decoupling / flexibility / maintainability / reusability. > > I've been considering using custom template tag. Yeah, it is standard and > pretty. I guess > this might take me a while to implement.
Well, the first time, yes, possibly. But that's not rocket science neither, and that's something anyone whishing to make proper use of Django should learn. > However, can this concept also be used to pass page objects (e.g model data > passed to a template from a view) from one view to another. You don't pass anything from "one view to another". You eventually pass data from a request to another, using either request params (querystring, post...), cookies, or sessions (and of course the parts of your urls that become view args). > For instance, I have a request model dynamic data Sorry, but I don't know what a "request model dynamic data" is supposed to be. Care to explain more clearly ? -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
