#22154 closed Cleanup/optimization (fixed)
Rename Class Based Generic Views to Built-in Class Based Views
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Documentation | Version: | 1.6 |
Severity: | Normal | Keywords: | Class Based Views |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Class Based Generic Views should be renamed to 'Built-in Class Based Views' or 'Built-in Class Views' to avoid a confusion with the implementation of a user defined Class Based View. The names Class Based Generic Views and Class Based Views which are meant to mean different things generates much confusion in the django community due to their subtle difference in naming scheme. This subtly impedes meaningful discussions on the subject. Nomenclature is an important part of any system in science and unless a thing or idea is clearly identified it cannot not be clearly communicated.
Attachments (1)
Change History (7)
comment:1 by , 11 years ago
Component: | Uncategorized → Documentation |
---|---|
Triage Stage: | Unreviewed → Accepted |
Type: | Uncategorized → Cleanup/optimization |
comment:2 by , 11 years ago
Yes. You will note in the here - https://docs.djangoproject.com/en/1.6/ that the built-in class based views are referred to as "built-in" but in the actual page referenced they are referred to as Class-based generic views.
Class-based views: Overview | Built-in display views | Built-in editing views | Using mixins | API reference | Flattened index
https://docs.djangoproject.com/en/1.6/
Note here they are referred to differently as Generic display views
https://docs.djangoproject.com/en/1.6/ref/class-based-views/
I believe that removing any ambiguity of terms will help the understanding and increase use of class based views where appropriate.
It would help if the documentation made a clear distinction between the implementation of class based views and the use of (ready made) "built-in class based views". The implementation of class based views generally involving a user defined class view inheriting from django.views.generic.base.View and mix-ins as needed to generate the appropriate view. The use of "built-in class based views" generally meaning to use ready made views based on the implementation class based views.
by , 10 years ago
Attachment: | 22154.diff added |
---|
comment:3 by , 10 years ago
Has patch: | set |
---|
Attached is a patch that renames two sections. Any other changes you would make?
comment:4 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I found that usage on this page. Is that what you were referring to?