Metadata-Version: 1.0
Name: Products.ATCustomizableView
Version: 0.3.0
Summary: A Plone product that change the standard Plone behaviour of the "View" menu
Home-page: http://plone.org/products/atcustomizableview
Author: keul
Author-email: luca@keul.it
License: GPL
Description: Introduction
        ============
        
        This product can change the behaviour of the Plone's "*Display*" menu, making it a little
        customizable. Those customization are *not* content type related, but are done for a
        single content.
        
        For every specific content of the portal:
        
        * You can block ability of your authors to change content's layouts.
        * You can add custom, additional, views to a content.
        * You can hide all standard available layout for a content, leaving only the new customized
        ones.
        
        .. image:: http://keul.it/images/plone/Products.ATCustomizableView-0.3.0-01.png
        :alt: The menu customization form
        
        User cases
        ----------
        
        `Why freeze the content layout?`
        Sometimes you need to apply a new view to a single content, like a folder.
        For example: you have a folder where you know is used only for *News Item* contents
        and you have a quite good view for this folder.
        
        Registering this view for all Folder content types will give to your author the choice
        to use this view also in other section of the site, but you don't want it.
        A views pollution in the "*Display*" menu can be confusing.
        `Why adding new entry in the menu`
        Keep in mind that you are adding new views to a single content of your site.
        
        For example: you have developed a new view for the *Page* and you want optionally leave
        to your authors to use or not this view in the home-page sub-sections of your site.
        
        Like above, registering this view for the Page content types will leave to authors the
        choice to use this view for *all* page of the site but, for design choice, you want to
        use this view only for some specific pages.
        `Why dropping base views`
        No much to say, may be you don't want to inherit the content types views and don't want
        that your authors are able to use them.
        
        Simplification for developers
        -----------------------------
        
        Behaviour described above can be reach also developing additional content types. However I found
        not very useful developing silly content type or marker interfaces only for obtaining additional
        layout.
        
        TODO
        ====
        
        * Thinking about moving to the approach used for `redturtle.custommenu.factories`__, as soon as
        the per-object menu customization will be moved out of the product.
        
        __ http://plone.org/products/redturtle.custommenu.factories
        
        
        Changes
        =======
        
        0.3.0 (2011-01-09)
        ------------------
        
        * Egg cleanup [keul]
        * Fixed dependency in the product [keul]
        * Product is now installable [keul]
        * Do not apply patches if the product is not installed [keul]
        * Added friendly Plone UI for managing configurations [keul]
        * Translations (for now in Italian, other are welcome) [keul]
        * Tested also on Plone 4 [keul]
        
        0.2.0 (2009-08-11)
        ------------------
        
        * Forget Plone 2.5 support.
        * No more ugly-old-style monkey patch, but now `collective.monkeypatcher`__
        is required. [keul]
        * Added controls on selectable views. [keul]
        
        __ http://pypi.python.org/pypi/collective.monkeypatcher/
        
        0.1.0 (2009-02-07)
        ------------------
        
        * Initial releases
        
Keywords: plone atct default-view layout
Platform: UNKNOWN
Classifier: Framework :: Plone
Classifier: Programming Language :: Python
Classifier: Development Status :: 4 - Beta
Classifier: Topic :: Software Development :: Libraries :: Python Modules
