Survey application with TurboGears and CatWalk

Part Tree

Rendering your surveys

We want to show our published surveys to our users and let them choose, fill and submit a survey.

We open our controller file and edit our index method. Index should return a list of published surveys: @turbogears.expose(html="survey.templates.surveys") def index(self): surveys=[{ 'id':s.id, 'name':s.name, 'description':s.description } for s in model.Survey.select(model.Survey.q.publish==True) ] return dict(surveys=surveys)

Remember to import your model in your controller file

We procede to create a new kid template file called 'surveys.kid' it will look like this: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:py="http://purl.org/kid/ns#" py:extends="'master.kid'"> <head> <meta content="text/html; charset=UTF-8" http-equiv="content-type" py:replace="''"/> <title>Superb survey</title> </head> <body> <h1>Pick a survey</h1> <ul> <li py:for="survey in surveys"> <a href="show?id=${survey['id']}" py:content="survey['name']">survey name here...</a> <br /> ${survey['description']} </li> </ul> </body> </html>

Go to your browser and se it working =)

Rendering your survey

To render our survey we implement a method called 'show' that expect a survey id as a parameter and returns a dictionary with the survey properties, questions and options: @turbogears.expose(html="survey.templates.survey") def show(self,id): try: survey = model.Survey.get(id) except sqlobject.SQLObjectNotFound: return 'uh uh' questions = [] for q in survey.questions: options = [] for o in q.options: options.append( {'id':o.id, 'text':o.text}) questions.append( { 'id':q.id, 'text':q.text, 'type':q.qType, 'options': list(options) } ) return dict( id=survey.id, name=survey.name, description=survey.description, questions = questions )

Now let's do some Kid Kong Fu. We create a new template called survey.kid which renders the survey properties and loops trough it's questions. The work of rendering each question type is delegated to templates functions based on the question type. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:py="http://purl.org/kid/ns#" py:extends="'master.kid'"> <head> <meta content="text/html; charset=UTF-8" http-equiv="content-type" py:replace="''"/> <title py:content="name">title</title> </head> <div py:def="text(question)"> <input type="text" name="question_${question['id']}" /> </div> <div py:def="textarea(question)"> <textarea name="question_${question['id']}"></textarea> </div> <div py:def="radio(question)"> <span py:for="option in question['options']"> <input type="radio" name="question_${question['id']}" value="${option['text']}"/> ${option['text']} <br /> </span> </div> <div py:def="select(question)"> <select name="question_${question['id']}"> <option py:for="option in question['options']" value="${option['text']}">${option['text']}</option> </select> </div> <div py:def="checkbox(question)"> <span py:for="option in question['options']"> <input type="checkbox" name="question_${question['id']}" value="${option['text']}"/> ${option['text']} <br /> </span> </div> <body> <h1 py:content="name">name</h1> <p py:content="description">description</p> <form action="process" method="post"> <input type="hidden" name="survey_id" value="${id}" /> <div class="question" py:for="question in questions"> <h2 py:content="question['text']">question</h2> <div>${ locals()[question['type']](question) }</div> </div> <br /> <input type="submit"/> </form> </body> </html>

Survey application with TurboGears and CatWalk

Part Tree

Rendering your surveys

Rendering your survey

Our rendered survey now looks like this: