p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Edited changes to docs/tutorial04.txt from [5649] 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@5651 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2007-07-12 04:44:45 +00:00
parent 0c5d001531
commit 8c4cc32352
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/tutorial04.txt
View File

@ -210,7 +210,7 @@ objects" and "display a detail page for a particular type of object."
``object_id`` for the generic views.
* We've added a name, ``poll_results``, to the results view so that we have
a way to refer to its url later on (see `naming URL patterns`_ for more on
a way to refer to its URL later on (see `naming URL patterns`_ for more on
named patterns).
.. _naming URL patterns: http://www.djangoproject.com/documentation/url_dispatch/#naming-url-patterns
@ -261,8 +261,8 @@ the new templates and context variables. Change the template call from
``polls/detail.html`` to ``polls/poll_detail.html``, and pass ``object`` in the
context instead of ``poll``.
The last thing to do is fix the url handling to account for the use of generic
views. In the vote view above we used the ``reverse()`` function to avoid
The last thing to do is fix the URL handling to account for the use of generic
views. In the vote view above, we used the ``reverse()`` function to avoid
hard-coding our URLs. Now that we've switched to a generic view, we'll need to
change the ``reverse()`` call to point back to our new generic view. We can't
simply use the view function anymore -- generic views can be (and are) used