Added notes in old generic views howto about the new class based approach.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@14610 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
9712f4c7a4
commit
a205fe9378
|
@ -2,6 +2,16 @@
|
||||||
Generic views
|
Generic views
|
||||||
=============
|
=============
|
||||||
|
|
||||||
|
|
||||||
|
.. versionchanged:: 1.3
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
From Django 1.3, function-based generic views have been deprecated in favor
|
||||||
|
of a class-based approach, described in the class-based views :doc:`topic
|
||||||
|
guide </topics/class-based-views>` and :doc:`detailed reference
|
||||||
|
</ref/class-based-views>`.
|
||||||
|
|
||||||
Writing Web applications can be monotonous, because we repeat certain patterns
|
Writing Web applications can be monotonous, because we repeat certain patterns
|
||||||
again and again. Django tries to take away some of that monotony at the model
|
again and again. Django tries to take away some of that monotony at the model
|
||||||
and template layers, but Web developers also experience this boredom at the view
|
and template layers, but Web developers also experience this boredom at the view
|
||||||
|
|
Loading…
Reference in New Issue