Lesson 11 - More Model-based Views

Transcript

1. Lesson 11 More Model-based Views Dana Spiegel dana@sociabledesign.com 1
2. Review: Model-based Views 2 • List of Teams and Players • Create templates • Create views • Add views to url router • Including url routers in base url router
3. Review: InlineModelAdmin • Allow the inclusion of related objects in the Model change form • Show up as a table of additional objects with defined fields • Must define a TabularInline class that works like ModelAdmin • Must include a reference to the Model • In the ModelAdmin where the inlines will be shown, define inlines, a tuple or list of the TabularInline classes 3 class StatisticAdmin(admin.TabularInline): model = Statistic fields = ('player', 'at_bats', 'runs', 'singles', 'doubles', 'triples', 'home_runs', 'rbis', 'walks', ) max_num = 12 extra = 12 class RosterAdmin(admin.ModelAdmin): list_display = ('team', 'home_game', 'away_game', ) inlines = (StatisticAdmin, )
4. Individual Team View • To provide a drill-down view into an individual team requires specifying which team to display • Handled by indicating the team ID in the URL • The URL specifies which team is being viewed • URL provides easy and understandable presentation in browser, and is SEO friendly • Links to team view pages are easy to generate • Single URL pattern for team view for any team 4 http://dev.hatcherydevshop.com:8080/softball/team/3/
5. Team View: Template • Team view template expects a team object in the context • Create softball/team/view.html • Present the team name in an H1 at the top of the page • Include a list of players with statistics • Iterate through team.players.all • Create a table with all player data • Include a list of games played • Iterate through team.rosters.all • Store game in template variable • Don’t have roster.game method! • Template requires it, so create it! • Display text in green if team is winner, red if loser • Versus column requires a test to see if team is home or away 5
6. Team View: View Method • Create team_view method to support view.html template • To know what team to display, team_view requires a team_id parameter • Using the team_id parameter, look up team with Team.objects.get • If team lookup fails because team doesn’t exist, return a 404 response using raise Http404 • Include team in template context dictionary 6 def team_view(request, team_id): """ Lists the details of the team with team_id """ try: team = models.Team.objects.get(id=team_id) except models.Team.DoesNotExist: raise Http404 return TemplateResponse(request, 'softball/team/view.html', { 'team': team, 'record': team.record(), })
7. Team View: URL Routing • To make team_view work, need to support url with team ID specified • URL regex must look for digits representing team ID • Once team ID is found, capture in team_id variable • All captured text is passed to view as parameters • Named captures using (?<name>...) will be passed to view based on parameter name (so order isn’t important) • Since view takes a team_id parameter, it will process the passed team_id properly • Because captured text is captured as digits, it will be passed as an int 7 url(r'^team/(?P<team_id>\d+)/$', 'softball.views.team_view', name='team_view')
8. Add Win/Loss Data to Template • Adding win/loss data presentation in template really isn’t easily implemented by pulling data from model • Instead, we gather data in view, and pass data to template in context dictionary • Allows reduction in database load—1 query instead of 2 • Makes template rendering a little faster since 1 fewer database call 8 def team_view(request, team_id): """ Lists all teams in the Database """ try: team = models.Team.objects.get(pk=team_id) except models.Team.DoesNotExist: raise Http404 return TemplateResponse(request, 'softball/team/view.html', { 'team': team, 'record': team.record(), })
9. Add Win/Loss Data to Template • To display record, use index notation to get data from tuple • Use pluralize template filter to show singular/plural text based on value of record • Pluralize works by rendering “s” if value filtered is 0 or > 1 • Renders nothing when value filtered is 1 • Can take an argument representing the letters to render in the case of pluralization of text, for example “es” • Ensures users read content naturally, and is very easy to integrate into template 9 <div class="well well-small right"> Record<br/> <strong>{{ record.0 }} win{{ record.0|pluralize }} / {{ record.1 }} loss{{ record.1|pluralize:"es" }}</strong> </div>
10. Work in Class • Add view, template, url for Player view • Add view, template, url for Game view • Homework • Finish adding views • Finish adding Bootstrap 10