Metadata-Version: 1.1
Name: django-extra-views-ng
Version: 0.3.2
Summary: Extra class-based views for Django
Home-page: https://github.com/hovel/django-extra-views
Author: Pavel Zhukov
Author-email: gelios@gmail.com
License: MIT
Description: django-extra-views-ng - The missing class-based generic views for Django
        =====================================================================
        
        Django's class-based generic views are great, they let you accomplish a large number of web application design patterns in relatively few lines of code.  They do have their limits though, and that's what this library of views aims to overcome.
        
        Installation
        ------------
        
        Installing from pypi (using pip). ::
        
            pip install django-extra-views-ng
        
        Installing from github. ::
        
            pip install -e git://github.com/hovel/django-extra-views.git#egg=django-extra-views
        
        
        Features so far
        ------------------
        
        - FormSet and ModelFormSet views - The formset equivalents of FormView and ModelFormView.
        - InlineFormSetView - Lets you edit formsets related to a model (uses inlineformset_factory)
        - CreateWithInlinesView and UpdateWithInlinesView - Lets you edit a model and its relations
        - GenericInlineFormSetView, the equivalent of InlineFormSetView but for GenericForeignKeys
        - Support for generic inlines in CreateWithInlinesView and UpdateWithInlinesView
        - Support for naming each inline or formset with NamedFormsetsMixin
        - SortableListMixin - Generic mixin for sorting functionality in your views
        - SearchableListMixin - Generic mixin for search functionality in your views
        
        Still to do
        -----------
        
        I'd like to add support for pagination in ModelFormSetView and its derivatives, the goal being to be able to mimic the change_list view in Django's admin. Currently this is proving difficult because of how Django's MultipleObjectMixin handles pagination.
        
        Examples
        --------
        
        Defining a FormSetView. ::
        
            from extra_views import FormSetView
        
        
            class AddressFormSet(FormSetView):
                form_class = AddressForm
                template_name = 'address_formset.html'
        
        Defining a ModelFormSetView. ::
        
            from extra_views import ModelFormSetView:
        
        
            class ItemFormSetView(ModelFormSetView):
                model = Item
                template_name = 'item_formset.html'
        
        Defining a CreateWithInlinesView and an UpdateWithInlinesView. ::
        
            from extra_views import CreateWithInlinesView, UpdateWithInlinesView, InlineFormSet
            from extra_views.generic import GenericInlineFormSet
        
        
            class ItemInline(InlineFormSet):
                model = Item
        
        
            class TagInline(GenericInlineFormSet):
                model = Tag
        
        
            class CreateOrderView(CreateWithInlinesView):
                model = Order
                inlines = [ItemInline, TagInline]
        
        
            class UpdateOrderView(UpdateWithInlinesView):
                model = Order
                inlines = [ItemInline, TagInline]
        
        
            # Example URLs.
            urlpatterns = patterns('',
                url(r'^orders/new/$', CreateOrderView.as_view()),
                url(r'^orders/(?P<pk>\d+)/$', UpdateOrderView.as_view()),
            )
        
        If you want to use granular access in templates you can name your inlines or formsets with NamedFormsetsMixin. ::
        
            from extra_views import NamedFormsetsMixin
        
            class CreateOrderView(CreateWithInlinesView):
                model = Order
                inlines = [ItemInline, TagInline]
                inlines_names = ['Items', 'Tags']
        
        You can add search ability for your classes by adding SearchableMixin and by setting search_fields::
        
            from django.views.generic import ListView
            from extra_views import SearchableListMixin
        
            class SearchableItemListView(SearchableListMixin, ListView):
                template_name = 'extra_views/item_list.html'
                search_fields = ['name', 'sku']
                model = Item
        
        In this case ``object_list`` will be filtred if GET query will be provided (like /searchable/?q=query), or you
        can manually override get_search_query method, to build custom search query
        
        Also you can define `search_fields` as list of tuples (e.g. `[('name', 'exact', ), 'sku']`)
        to provide custom lookups for searching. Default lookup is `icontains`
        
        Define sorting in view. ::
        
            from django.views.generic import ListView
            from extra_views import SortableListMixin
        
            class SortableItemListView(SortableListMixin, ListView):
                sort_fields_aliases = [('name', 'by_name'), ('id', 'by_id'), ]
                model = Item
        
        You can hide real field names in query string by define sort_fields_aliases attribute (see example)
        or show they as is by define sort_fields. SortableListMixin adds ``sort_helper`` variable of SortHelper class,
        then in template you can use helper functions: ``{{ sort_helper.get_order_query_by_FOO }}``,
        ``{{ sort_helper.get_order_query_by_FOO_asc }}``, ``{{ sort_helper.get_order_query_by_FOO_desc }}`` and
        ``{{ sort_helper.is_sorted_by_FOO }}``
        
        More descriptive examples to come.
        
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Environment :: Web Environment
Classifier: Framework :: Django
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python
