Changes between Version 1 and Version 2 of ClassBasedViews

Timestamp:

Oct 1, 2010, 6:45:18 AM (14 years ago)

Author:

Ben Firshman

Comment:

--

ClassBasedViews

@@ -25 +25 @@
  * '''Ease of decoration''': Does the proposed technique pose any impediments to easily decorating views?
 
-The [http://groups.google.com/group/django-developers/browse_thread/thread/e23d9a5a58fe5891 most recent django-developers discussion on the topic] discussed many of the available options. Here is a summary of the various approaches that have been proposed.
+=== View instantiation and thread safety ===
+The [http://groups.google.com/group/django-developers/browse_thread/thread/e23d9a5a58fe5891 most recent django-developers discussion on the topic] discussed many of the available options on instantiating the views and protecting them from threading issues. Here is a summary of the various approaches that have been proposed.
 
 === !__call!__() and copy() ===
@@ -90 +91 @@
  * Requires special cases in !UrlResolver which almost inevitably involve isinstance(!ViewClass) or some analog.
 
-= Recommendation =
+=== Recommendation ===
 
 Based on these discussions, plus in-person discussions at !DjangoCon.eu,  !__copy!__() on !__call!__() appears to be a slight front runner, with !__new!__() as a close runner up.
+
+== How to help ==
+
+Class-based views are being developed as a [http://github.com/bfirsh/django-class-based-views separate application on Github]. There are a few things yet to be done:
+
+ * A simple readme for getting started
+ * Testing it in real applications
+ * More test coverage
+ * Support for ModelForms that mimics the current generic views
+ * Full documentation
+
+Fork the Github project if you want to help out.