<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: peter-baumgartner</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/peter-baumgartner.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-03-25T22:53:28+00:00</updated><author><name>Simon Willison</name></author><entry><title>Better Use of Newforms</title><link href="https://simonwillison.net/2008/Mar/25/django/#atom-tag" rel="alternate"/><published>2008-03-25T22:53:28+00:00</published><updated>2008-03-25T22:53:28+00:00</updated><id>https://simonwillison.net/2008/Mar/25/django/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://lincolnloop.com/blog/2008/mar/13/better-newforms/"&gt;Better Use of Newforms&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Two really neat techniques: using an inclusion tag template to DRY your custom form templates, and adding what-to-do-next methods to the form class itself to cut down on the application code in your views.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/django"&gt;django&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/dry"&gt;dry&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/newforms"&gt;newforms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/peter-baumgartner"&gt;peter-baumgartner&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;&lt;/p&gt;



</summary><category term="django"/><category term="dry"/><category term="newforms"/><category term="peter-baumgartner"/><category term="python"/></entry></feed>