On Wed, Aug 10, 2011 at 6:57 PM, bruno desthuilliers < [email protected]> wrote:
> On 10 août, 16:30, Tom Evans <[email protected]> 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. 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. For instance, I have a request model dynamic data saved in a session. I'm passing this data to another view and I want it to change based on the value of a url parameter? -- Odeyemi 'Kayode O. http://www.sinati.com. t: @charyorde -- 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?hl=en.
