To provide a simple API to your templates I like to use class based views because they expose your class attributes via view.* in your templates. if you want something more solid where you can easily switch your API based on layouts, use pyramid_layout... it rocks.
On Monday, September 2, 2013 6:51:17 AM UTC-4, Marek Szwałkiewicz wrote: > > Hi all, > > in current project I need to include 2 form objects (flatland forms) in > context of almost every template. > > Those 2 objects are used in master template (that is inherited everywhere) > and need to be available in almost all cases. > What is a best way to include those objects (except from manually > including it in every view return dictionary)? > > Thanks, > Mark Szwałkiewicz > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
