#16807 closed New feature (fixed)
Document/Introduce the process and usage of class based views outside of generic view context
| Reported by: | Preston Holmes | Owned by: | Preston Holmes |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | bluejeansummer@…, timograham@… | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
Currently class based views are strongly and directly coupled with generic views leading to confusion as to whether the approach can be used as a general view replacement.
Change History (10)
comment:1 by , 13 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 13 years ago
| Cc: | added |
|---|
comment:3 by , 13 years ago
hopefully the documentation of decoration will also be updated via #14512
comment:5 by , 13 years ago
Just a note to link where I'm working on this ticket:
github.com/ptone/django/tree/ticket16807
and a proposed outline for how the reference docs may be organized (the order of Views is not right here, this is all currently machine generated).
gist.github.com/gists/1246480
Input & collaboration welcome
comment:7 by , 11 years ago
| Cc: | added |
|---|---|
| Has patch: | set |
| Patch needs improvement: | set |
comment:8 by , 11 years ago
Hi Preston, nice work so far. I'd like to try to get this committed. I've done some work with your existing patch.
https://github.com/timgraham/django/commit/5aa27d5c78024e9c5fdadd883bbac63bf29a9aec
It looks like you had some more ideas as there were some notes at the bottom of the existing commits. Would you like to describe a little more what you had in mind?
https://github.com/ptone/django/commit/ce46758c02eafd90c92dc07862c5fad9dde40a03#L0R180
comment:9 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I'm currently working on this at DjangoCon2011 sprints