Code

Changes between Version 1 and Version 2 of ClassBasedViews


Ignore:
Timestamp:
10/01/10 04:45:18 (4 years ago)
Author:
bfirsh
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ClassBasedViews

    v1 v2  
    2525 * '''Ease of decoration''': Does the proposed technique pose any impediments to easily decorating views? 
    2626 
    27 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. 
     27=== View instantiation and thread safety === 
     28The [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. 
    2829 
    2930=== !__call!__() and copy() === 
     
    9091 * Requires special cases in !UrlResolver which almost inevitably involve isinstance(!ViewClass) or some analog. 
    9192 
    92 = Recommendation = 
     93=== Recommendation === 
    9394 
    9495Based 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. 
     96 
     97== How to help == 
     98 
     99Class-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: 
     100 
     101 * A simple readme for getting started 
     102 * Testing it in real applications 
     103 * More test coverage 
     104 * Support for ModelForms that mimics the current generic views 
     105 * Full documentation 
     106 
     107Fork the Github project if you want to help out.