Changes between Initial Version and Version 1 of Ticket #16174, comment 9
- Timestamp:
- Dec 6, 2011, 2:03:21 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #16174, comment 9
initial v1 1 1 That approach is definitely best. 2 2 3 I think some sort of mixin as AndrewIngram mentioned would be ideal .3 I think some sort of mixin as AndrewIngram mentioned would be ideal although it depends on what you mean by "as much class based views API as possible." 4 4 5 5 My initial thoughts are thoughts are that a mixin would be a bit brittle because its `post` method would always need to be resolved first with respect to the inheritance tree. 6 6 7 7 Another option would be to replace the `ProcessFormView` and provide new bases for the create, update, and delete views in the new form preview package. 8 8 9 Or maybe I'm just not thinking outside the box ;) I will have a look this weekend and report back. 9 If you mean the underlying API and not providing easy previews for the existing views in `edit.py`, perhaps the current form preview functionality could be replaced using the new form wizard machinery. 10 11 Maybe I'm just not thinking outside the box ;) I will have a look this weekend and report back.