Metadata-Version: 1.1
Name: collective.cover
Version: 1.0a5
Summary: A sane, working, editor-friendly way of creating front pages and other composite pages. Working now, for mere mortals.
Home-page: https://github.com/collective/collective.cover
Author: Carlos de la Guardia et al.
Author-email: cguardia@yahoo.com
License: GPLv2
Description: ****************
        collective.cover
        ****************
        
        .. contents:: Table of Contents
        
        Life, the Universe, and Everything
        ----------------------------------
        
        ``collective.cover`` is a package that allows the creation of elaborate covers
        for website homepages, especially for news portals, government sites and
        intranets that require more resources than a simple page or collection can
        offer. However, despite offering rich resources to build a cover,
        ``collective.cover`` also provides a very easy mechanism for managing its
        contents, built around a drag-and-drop interface.
        
        ``collective.cover`` is based on `Blocks`_ and `Tiles`_, like `Deco`_, the new
        layout composition system for Plone.
        
        .. TODO: explain why we need cover instead of just using Deco itself.
        
        .. TODO: add a comparison between Deco and collective.cover
        
        Use cases
        ^^^^^^^^^
        
        Suppose you are running The Planet, a news site that has a bunch of editors
        focused on getting news on different topics, like Economy, Health or Sports.
        
        If you are the main publisher of the site, you may want to delegate the
        construction of the cover page of the Economy section to the people working on
        that content area, but you might not want them messing around the Sports
        section as well.
        
        Also, suppose you have the final game of the World Cup and the match is going
        to be defined on penalties: you may want to prepare a couple of cover pages
        and publish the right one focused on the team that won in the end.
        
        These are the kind of issues we want to solve with this package; we are still
        far from it, but that is the idea.
        
        Mostly Harmless
        ---------------
        
        .. Warning::
           ``collective.cover`` is currently not compatible with standard Plone tiles;
           this will be addressed in a future realease of the package. See issues
           `#81`_ and `#112`_ for more information.
        
        .. Warning::
            ``collective.cover`` 1.0a4 includes a new banner tile that will replace
            image and link tiles completely, as we found them redundant. Please
            replace manually any instance of image and link tiles in your covers with
            banner tiles. Image and link tiles will be completely removed on next
            release 1.0a5 (see issue `#218`_ for more information).
        
        .. image:: https://secure.travis-ci.org/collective/collective.cover.png?branch=master
            :target: http://travis-ci.org/collective/collective.cover
        
        .. image:: https://coveralls.io/repos/collective/collective.cover/badge.png?branch=master
            :target: https://coveralls.io/r/collective/collective.cover
        
        Got an idea? Found a bug? Let us know by `opening a support ticket`_.
        
        Don't Panic
        -----------
        
        Installation
        ^^^^^^^^^^^^
        
        To enable this package in a buildout-based installation:
        
        #. Edit your buildout.cfg and add add the following to it::
        
            [buildout]
            ...
            eggs =
                collective.cover
        
            [versions]
            ...
            plone.app.blocks = 1.1.1
            plone.app.drafts = 1.0a2
            plone.app.jquery = 1.7.2
            plone.app.tiles = 1.0.1
            plone.tiles = 1.2
        
        #. If you are using Plone 4.2.x you need to add the following also::
        
            [versions]
            ...
            collective.js.jqueryui = 1.8.16.9
            plone.app.jquerytools = 1.5.6
        
        After updating the configuration you need to run ''bin/buildout'', which will
        take care of updating your system.
        
        Go to the 'Site Setup' page in a Plone site and click on the 'Add-ons' link.
        
        Check the box next to ``collective.cover`` and click the 'Activate' button.
        
        .. Note::
        
            You may have to empty your browser cache and save your resource registries
            in order to see the effects of the product installation.
        
        Adding Cover
        ^^^^^^^^^^^^
        
        .. figure:: https://raw.github.com/collective/collective.cover/master/cover1.png
            :align: center
            :height: 312px
            :width: 367px
        
        
        You add a cover like you would any type of content in Plone:
        
        #. Navigate to the folder where you want to create a cover;
        
        #. Open the "Add Item..." menu and choose "Cover";
        
        #. Fill in the required fields:
        
            "Title" and "Description"
                Same as with other Plone content, like Page.
            "Layout"
                Choose one of the predefined cover layouts (you will see a preview of
                the selected layout).
        
        #. "Save".
        
        .. figure:: https://raw.github.com/collective/collective.cover/master/cover1a.png
            :align: center
            :height: 600px
            :width: 680px
        
        Your cover is now created based on the information provided.
        
        Adding content in your Cover
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        
        After the cover is created, you'll notice it comes with some predefined blocks
        (according to the selected layout), but it still has no content associated.
        To define the content that will appear on the cover, perform the following
        steps:
        
        .. figure:: https://raw.github.com/collective/collective.cover/master/cover2.png
            :align: center
            :height: 460px
            :width: 680px
        
        #. Select the "Compose" tab.
        
        #. Open the "Add Content" tab to the right of the green bar. A small window
           will appears showing the most recent items added in the portal.
        
        #. Select the title of any item in the list and drag it to one of the tiles
           (dotted boxes) in the content area.
        
        #. Hover the item over one of the Tile boxes. Each Tile allows only certain
           types of content to be added. If the content you selected is allowed on
           that Tile, the box will turn green. If not, it will remain gray.
        
        #. Release the item. Information from that content will be automatically
           applied to the chosen tile and will be visible on the cover.
        
        #. Repeat the process to add content to each one of the other tiles.
        
        #. To visualize the final result, select the "View" tab.
        
        .. figure:: https://raw.github.com/collective/collective.cover/master/cover3.png
            :align: center
            :height: 500px
            :width: 670px
        
        There are also two other navigation options to find content.
        
        Searching for content
        +++++++++++++++++++++
        
        You can use the search field in the content selection window to locate the
        content you want:
        
        #. Type the term you want to find.
        
        #. Push the "Search" button.
        
        The items related to the term you search will be displayed and can be used
        according to the steps above.
        
        Content tree
        ++++++++++++
        
        Inside the content selection window you can also navigate through your site to
        locate existing content.
        
        #. Select the "Content Tree" tab.
        
        #. Select the links to browse through the structure of your site until you
           find the desired content. All items listed are available to be used
           according to the steps above.
        
        Images in folderish content
        +++++++++++++++++++++++++++
        
        When you drop a 'folderish' content inside a list or a carousel tile, the tile
        will try to load the contained images. This way a folder, a collection, or some
        other kind of containers could be used to drop several images into a tile in
        just one step.
        
        Changing tile configuration
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^
        
        .. figure:: https://raw.github.com/collective/collective.cover/master/cover6.png
            :align: center
            :height: 640px
            :width: 760px
        
        After a content is added to a cover tile, a copy of some of its information
        will be stored in the cover and will appear to the end user. If necessary, you
        can change some of the information related to the content exclusively for the
        cover, without changing the information in the original item. This feature is
        very useful to adjust the content for the cover. For example, you can shorten
        a title to better fit it into a homepage layout.
        
        To change the information on the cover, follow these steps:
        
        #. Select the "Compose" tab.
        
        #. Select the portion of text you want to change, like the title, the
           description or any other text element.
        
        #. Change the text and "Save".
        
        The changes will be applied to your cover immediately.
        
        .. Important::
            As mentioned before, the changes will be applied only to the cover tile,
            not to the original content.
        
        Advanced Actions
        ----------------
        
        Changing the layout of your cover
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        
        If you have created a blank cover or if want to change the structure of your
        current cover, you can add or delete tiles, change the position of an existing
        tile, or even change the rows and columns structure of the cover. These
        operations can be performed from the "Layout" tab.
        
        .. figure:: https://raw.github.com/collective/collective.cover/master/cover4.png
            :align: center
            :height: 427px
            :width: 696px
        
        A cover is a combination of three basic elements:
        
        - Rows (which may contain one or more columns, arranged horizontally)
        - Columns (which may contain one or more tiles arranged vertically)
        - Tiles
        
        Adding rows and columns
        +++++++++++++++++++++++
        
        To add a new row, follow these steps:
        
        #. In the Layout tab, click the Row icon and drag it to your page. Then you
           need to add one or more columns to this row so you can add tiles later.
        
        #. Click on the Column icon and drag it into a row.
        
        You can repeat this operation as often as you need. ``collective.cover`` will
        divide the space between the rows and columns automatically.
        
        Changing the width of columns
        +++++++++++++++++++++++++++++
        
        You can control the width of each column individually:
        
        #. Push the configuration icon of the desired column.
        
        #. Drag the slider sideways, adjusting the desired number of column widths.
           The higher the number, the larger the column width.
        
        #. "Save".
        
        .. figure:: https://raw.github.com/collective/collective.cover/master/cover5.png
            :align: center
            :height: 450px
            :width: 670px
        
        By default, ``collective.cover`` uses a grid of 16 units. Therefore, the sum
        of the all widths in a column must not exceed 16. To make it easier to edit
        the width of all columns, adjust first the width of the smallest column.
        
        Adding new tiles
        ^^^^^^^^^^^^^^^^
        
        Now that you have created columns, you can add tiles to it:
        
        #. In the Layout tab, select the Tile icon and drag it to the column where you
           want to place it.
        
        #. Choose one of the available tiles in the pop-up overlay.
        
        #. Change the configuration as desired.
        
        #. Push "Save".
        
        The new tile can be used in the Compose tab to select/add content.
        
        Adjusting tiles
        ^^^^^^^^^^^^^^^
        
        You can change the settings from previously added tiles at any time:
        
        #. In the Layout tab, select the Setup icon of the respective tile.
        
        #. Modify the information.
        
        #. "Save".
        
        Moving tiles around
        ^^^^^^^^^^^^^^^^^^^
        
        On a page that has more than one column, you can conveniently move your tiles
        around:
        
        #. Select the "Layout" tab.
        
        #. Click on a tile and drag it over another column in any of the rows.
        
        #. When you release, the tile it will be positioned in the new column.
        
        #. Repeat as often as necessary.
        
        #. When finished, push "Save" and the new configuration will be applied.
        
        Saving a layout as a model
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
        
        You can save one of your covers as a template for creating other covers on
        your website:
        
        #. Select the Layout tab.
        
        #. At the top of the page, enter a name for your model.
        
        #. "Save".
        
        Now this layout can be used as a model to create new covers, as explained in
        the section "Adding a cover".
        
        Views
        ^^^^^
        
        Tiles for the collective.cover package provide 3 different views:
        
        Rendered view
        +++++++++++++
        
        This is the view that will be rendered for anyone that has View permission. It
        will render all fields defined in the schema of the tile, based on their
        configuration, as set in the configuration view.
        
        Edit view
        +++++++++
        
        This view is a common edit view, where all fields from the schema definition
        of the tile will be rendered in an "edit" mode. Data entered here will persist
        in the tile itself.
        
        All fields from the schema will get rendered, irrespective of their setting in
        the configuration view.
        
        This view is accessed through the "Compose" view of the cover. You should see
        an "edit" button for each tile.
        
        If you don't want your tile to be editable, you should override the
        ``is_editable`` attribute of your tile base class and set it to False
        
        Configuration view
        ++++++++++++++++++
        
        This view is similar to the edit one, except it is intended for configuring
        different aspects of the tile. From here you can specify which fields get
        rendered when viewing the tile, or the order in which they show up.
        
        In addition, each field widget can provide specific configuration options.
        For instance, an ITextLinesWidget will provide an extra configuration 
        option, "HTML tag", which allows to specify the HTML tag to be used when
        rendering data saved in this field.
        
        This view is accessed through the "Layout" view of the cover. You should see
        a "configuration" button for each tile.
        
        If you don't want your tile to be configurable, you should override the
        ``is_configurable`` attribute of your tile base class and set it to False
        
        Writing a custom widget in "configure" mode for a field
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        
        The configuration view uses z3c.form to automatically render a form based on
        the tile's schema definition. For that, it renders widgets in a "configure" 
        mode. You can see how existing ones are defined, checking the configure.zcml
        file under tiles/configuration_widgets
        
        How to develop a tile for collective.cover
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        
        Follow instructions in David Glick's `Using tiles to provide more flexible
        Plone layouts`_ to understand how to develop tiles, and how they work.
        
        Instead of inheriting from plone.tiles.PersistentTile, inherit from
        ``collective.cover.tile.base.PersistentCoverTile``.
        
        Register your tile on the registry using the "plone.app.tiles" record::
        
            <record name="plone.app.tiles">
              <value purge="false">
                <element>my.package.mytile</element>
              </value>
            </record>
        
        There are a couple of methods defined in this base class that provide
        additional functionality expected by the cover object, that you should
        override in your class:
        
        **populate_with_object(obj)**
            It takes a Plone content object as parameter, and it will store the
            content information into the tile. Make sure to call this method to check
            for permissions before adding content to the tile. Check the code of
            existing tiles for examples of use.
        
        **delete()**
            It removes the persistent data created for the tile.
        
        **accepted_ct()**
            It returns a list of valid content types that this tile will accept, or
            ``None`` in case it doesn't accept any.
        
        **get_tile_configuration()**
            It returns the stored configuration options for this tile.
        
        Storage
        +++++++
        
        Data and configuration for tiles are stored in an annotation of the context
        where the tile is being shown.
        
        You can see how this works by looking into data.py and configuration.py under 
        the tiles directory.
        
        Render view
        +++++++++++
        
        In order to visualize the tile's content, you need to write a view that will
        render it. For that, you need to get some things into consideration.
        
        #. The view will always be rendered, so you need to add conditions to show
           specific content based on what information the tile has, if any.
        
        #. You need to render content based on the configuration of the tile fields.
           For that, there's a helper method provided with every tile called
           ``get_configured_fields``. This will iterate over all fields, and will
           get the configuration and data for each, in the order that they should be
           rendered. If the field has no data stored, then it will not be included
           among the returned values.
        
           You can override this, in case you need a different behavior, check
           collection.py under the tiles directory and collection.pt under the
           tiles/templates directory for an example. 
        
        For additional hints on how to create a template for your tile and make it
        work, check all tiles provided by this package, under the tiles directory.
        
        Image field and scales
        ++++++++++++++++++++++
        
        To add an image field to your tile::
        
            image = NamedImage(
                title=_(u'Image'),
                required=False,
            )
        
        Then, you have several ways of using image scales in your tile templates.
        
        #. You can pass width and height to the ``scale`` method explicitly::
        
            <img tal:define="scales view/@@images;
                             thumbnail python: scales.scale('image', width=64, height=64);"
               tal:condition="thumbnail"
               tal:attributes="src thumbnail/url;
                               width thumbnail/width;
                               height thumbnail/height;
                               class position;
                               alt view/data/title" />
        
        #. Or you can use Plone predefined scales::
        
            <img tal:define="scales view/@@images;
                             thumbnail python: scales.scale('image', scale=scale);"
                 tal:condition="thumbnail"
                 tal:attributes="src thumbnail/url;
                                 width thumbnail/width;
                                 height thumbnail/height;
                                 class position;
                                 alt view/data/title" />
        
        .. Tip::
            Use the scale saved from the configuration. Check tile templates to get
            the idea.
        
        Cover tiles supports external images too, that means than if you drop a
        content with an image into a cover tile than implements an image field, cover
        will honor the image and scales in the original object. This way the image
        data isn't duplicated and products than allow scales modifications are
        supported.
        
        Not entirely unlike
        -------------------
        
        Over the years there have been some packages designed to solve the problem of
        creating section covers in Plone. We have used and have taken ideas from the
        following:
        
        `CompositePack`_
            Very old; the legacy code is so complex that is not maintainable anymore.
            It has (arguably) the best user interface of all. Layouts can not be
            created TTW. Viewlets are just page templates associated with content
            types; you can drag&drop viewlets around the layout. Publishers love it.
        
        `CMFContentPanels`_
            Code is very old, but still maintained (at least works in Plone 4). Allows
            to create complex layouts TTW and use any layout as a template. Easy to
            extend and edit (but is terrible to find a content to use). Needs a lot of
            memory to work and aggressive cache settings.
        
        `Collage`_
            Allows the creation of layouts TTW but it has (arguably) the worst user
            interface of all. It is easily extended and there are several add-ons
            available that provide new functionality for it.
        
        Home Page Editor of the Brazilian Chamber of Deputies Site
            Strongly based on `Collage`_, this package was presented at the `World
            Plone Day 2012 Brasilia`_. It allows editing of home pages and the
            definition of permissions on blocks of content. Available only for Plone 3
            and not openly published… yet.
        
        `collective.panels`_
            A new package that lets site editors add portlets to a set of new
            locations: above and below page contents, portal top and footer. The
            package comes with a number of flexible layouts that are used to position
            the portlets, and locations can be fixed to the nearest site object, to
            facilitate inheritance. In ``collective.cover`` (this package), we don't
            want to use portlets at all.
        
        .. _`#112`: https://github.com/collective/collective.cover/issues/112
        .. _`#218`: https://github.com/collective/collective.cover/issues/218
        .. _`#81`: https://github.com/collective/collective.cover/issues/81
        .. _`Blocks`: https://github.com/plone/plone.app.blocks
        .. _`CMFContentPanels`: http://plone.org/products/cmfcontentpanels
        .. _`Collage`: http://plone.org/products/collage
        .. _`collective.panels`: https://github.com/collective/collective.panels
        .. _`CompositePack`: http://plone.org/products/compositepack
        .. _`Deco`: https://github.com/plone/plone.app.deco
        .. _`opening a support ticket`: https://github.com/collective/collective.cover/issues
        .. _`see and comment on our mockups online`: https://simples.mybalsamiq.com/projects/capas/grid
        .. _`Tiles`: https://github.com/plone/plone.app.tiles
        .. _`Using tiles to provide more flexible Plone layouts`: http://davisagli.com/blog/using-tiles-to-provide-more-flexible-plone-layouts
        .. _`World Plone Day 2012 Brasilia`: http://colab.interlegis.leg.br/wiki/WorldPloneDay
        
        Share and Enjoy
        ---------------
        
        ``collective.cover`` would not have been possible without the contribution of
        the following people:
        
        - André Nogueira
        - Asko Soukka
        - Carlos de la Guardia
        - Cleber J. Santos
        - Davi Lima
        - Érico Andrei
        - Franco Pellegrini
        - Giorgio Borelli
        - Gonzalo Almeida
        - Héctor Velarde
        - Juan A. Díaz
        - Juan Pablo Giménez
        - Marcos F. Romero
        - Ricardo Bánffy
        - Rodrigo Ferreira de Souza
        - Silvestre Huens
        - Thiago Tamosauskas
        - `Launched Pixels`_ (icon)
        
        You can find an updated list of package contributors on `GitHub`_.
        
        Development sponsored by Open Multimedia, Ravvit and `Simples Consultoria`_.
        
        .. _`Launched Pixels`: http://www.launchedpixels.com/
        .. _`GitHub`: https://github.com/collective/collective.cover/contributors
        .. _`Simples Consultoria`: http://www.simplesconsultoria.com.br/
        
        There's a frood who really knows where his towel is
        ---------------------------------------------------
        
        1.0a5 (2013-10-02)
        ^^^^^^^^^^^^^^^^^^
        
        - Added norwegian translation. [espenmn]
        
        - Install IRelatedItems behavior to avoid 'ReferenceException: Invalid target
          UID' (fixes `#294`_). [hvelarde]
        
        - Implement link integrity on Rich Text tile references (closes `#35`_).
          [jpgimenez]
        
        - Register new alternate view for covers; the new view behaves like a standard
          content type view displaying object's title, description and viewlets on
          Plone's main_template main slot (closes `#271`_). [hvelarde]
        
        - Fixes content-search in content chooser to correctly get the first 
          page of results (closes `#276`_). [marcosfromero]
        
        - Added any content type support for banner tile. If it has an `image`
          or `getImage` attribute, displays that image. And always adds
          a link (closes `#241`_). [marcosfromero]
        
        - Prevent unnecesary page reloads when saving or canceling edit overlay
          in tiles (closes `#274`_). [marcosfromero]
        
        - On collection tile, return a thumbnail only if the item has an image field
          and the field is visible (closes `#278`_). [cleberjsantos, hvelarde]
        
        - Added Cover as Linkable in TinyMCE settings (closes `#259`_).
          [marcosfromero]
        
        - Default CSS class for tiles (closes `#262`_). [marcosfromero]
        
        - When adding a tile, display configuration icon only for configurable
          tiles (closes `#204`_). [marcosfromero]
        
        - Auto add a column when adding a row (closes `#212`_).
          [marcosfromero]
        
        - Remove dependency on plone.batching to avoid ``IndexError: multiple_pages``
          on Plone 4.2. [jpgimenez]
        
        - Move CSS to registry_css (closes `#244`_). [agnogueira]
        
        - Collection tile now fulfills the configured image size (fixes `#239`_).
          [cleberjsantos]
        
        - Friendly layout for tile configuration (closes `#133`_). [agnogueira]
        
        
        1.0a4 (2013-07-27)
        ^^^^^^^^^^^^^^^^^^
        
        - Add Finnish translation. [datakurre]
        
        - Add Italian translation. [gborelli]
        
        - Package documentation was updated. [hvelarde]
        
        - 'buttons.cancel' in prepOverlay closeselector has to be in quotes to
          avoid unrecognized expression javascript errors [ericof]
        
        - Refactor collection tile to include header and footer fields and fix tile's
          i18n. (closes `#118`_) [hvelarde]
        
        - Add simple Chinese translations (zh_CN). [Adam tang]
        
        - Add banner tile that will replace image and link tiles; add deprecation
          warning to image and link tiles as they will be removed from package on
          next release; an upgrade step is provided for unregistering them to
          avoid further addition on covers. (closes `#218`_). [hvelarde]
        
        - Make carousel tile configurable and avoid NoneType error by checking if
          carousel is empty (fixes `#203`_). [hvelarde]
        
        - Refactor image tile to use original image and scales, when possible.
          [ericof, hvelarde]
        
        - Add border to carousel tile dot. (closes `#206`_). [hvelarde]
        
        - Upgrade to plone.app.blocks 1.1 [ericof]
        
        - Refactor EnabledTilesVocabulary to avoid issues with situations in which
          we have no context/request (HT datakurre). [hvelarde]
        
        - Spanish and Brazilian Portuguese translations were updated. [hvelarde]
        
        - [bugfix] Prevent the configuration view to crash if the widget does not
          provide an 'accesskey'. [frapell]
        
        - Allow editor to add custom class for each tile (closes `#190`_). [jpgimenez]
        
        - Refactor vocabularies and avoid ComponentLookupError when tile is not
          available. [hvelarde]
        
        - Add 'alt' attribute to images in list tile. [ericof]
        
        - Fix image scaling view. [ericof]
        
        - Avoid ComponentLookupError by improved handling of Unauthorized access of
          non-published or deleted objects referenced in the tiles. [ericof]
        
        - Fix translation of Compose and Layout that must be in plone domain. [toutpt]
        
        - Add French translation. [toutpt]
        
        
        1.0a3 (2013-05-03)
        ^^^^^^^^^^^^^^^^^^
        
        - Better support for internal and external images (closes `#188`_).
          [jpgimenez]
        
        - Gallery tile now allows sorting of items easily through a widget created for
          that purpose (closes `#198`_). [Quimera]
        
        - A custom permission for the export layout funcionality was added; exporting
          a cover layout to the Plone registry is now an administrative task
          accomplished only by Managers and Site Administrators (closes `#177`_).
          [Quimera]
        
        - Fix a bug in collection tile when the target collection was removed
          (closes `#138`_). [jpgimenez]
        
        - Improve interface and performance of content chooser
          (closes `#168`_ and `#169`_). [jpgimenez]
        
        - Add upgrade step to rename resources in CSS and JS registries
          (fixes `#171`_). [hvelarde]
        
        - An option in the control panel configlet was added in order to select the
          tiles that will be available for cover layout creation; an upgrade step
          is provided to update the registry with the new record (closes `#191`_).
          [hvelarde]
        
        - Tile selection functionality in layout edit view was refactored  to an
          explicit D&D UI (closes `#183`_). [Quimera]
        
        - Apply default configuration to tiles at initialization (closes `#100`_).
          [hvelarde]
        
        - Store basic tile data in unicode format to avoid UnicodeDecodeError
          (closes `#144`_). [hvelarde]
        
        - A new special widgect for the cover creation and layout selection was added;
          the widget draws a preview of the layout in real time using an HTML5 canvas
          element (closes `#179`_). [Quimera]
        
        - Show title of object as alt attribute in image of basic tile. [hvelarde]
        
        - Ensure tile UUID does not start with a number (fixes `#137`_). [hvelarde]
        
        - Implements an original size scale to show the original image. [jpgimenez]
        
        - Improve the way than images are accesed from the original object,
          using the standard images traversal. (issue `#158`_) [jpgimenez]
        
        - Fixed a bug with Plone 4.3 that avoided TinyMCE being displayed for
          RichText. (closes `#157`_). [ericof]
        
        
        1.0a2 (2013-04-09)
        ^^^^^^^^^^^^^^^^^^
        - Move Galleria's stylesheet and JS init to <head>. [davilima6]
        
        - New tile: `PloneFormGen`_ embedded form. [ericof]
        
        - New tile: Content Body. [ericof]
        
        - Update package documentation. [hvelarde, jpgimenez]
        
        - Package is now compatible with Plone 4.3. [ericof, jpgimenez, hvelarde]
        
        - Remove dependency on plone.principalsource (closes `#152`_). [ericof]
        
        - Support five.grok 1.3.2 and plone.app.dexterity 2.0.x. [ericof]
        
        - Update JQuery UI to version 1.8.16.9 (fixes `#124`_). [hvelarde]
        
        - Fix TinyMCE table conflict (closes `#142`_). [agnogueira]
        
        - News Items can now be added to the carousel tile (fixes `#146`_).
          [jpgimenez]
        
        - Basic tile date field visibility is now configurable. [jpgimenez]
        
        - Refactor carousel tile to use collective.js.galleria (closes `#123`_).
          [jpgimenez]
        
        - Refactor list tile to use adapters to get the contained items uids.
          [jpgimenez]
        
        - Implements a way to ommit fields from tiles edit form and show it at
          configure form. [jpgimenez]
        
        - Refactor of collection tile. [hvelarde]
        
        - List and carousel tiles now support loading images from folderish content.
          [jpgimenez]
        
        - Have the <base> tag to include a slash at the end so relative ajax calls are
          called for the object and not its parent (fixes `#48`_). [frapell]
        
        - In order to be able to load Dexterity items from the import content GS step,
          we need to provide this interface manualy, until a proper fix in Dexterity
          is implemented. [frapell]
        
        - Make the cover object to be an Item instead of a Container (fixes `#114`_).
          [frapell]
        
        - Date and subjects fields on basic tile are now Read Only (fixes `#129`_).
          [jpgimenez]
        
        - Fix row height in layout view (closes `#128`_). [Quimera]
        
        - Fix filter feature on content chooser (closes `#121`_). [Quimera]
        
        
        1.0a1 (2013-01-07)
        ^^^^^^^^^^^^^^^^^^
        
        - Initial release.
        
        .. _`PloneFormGen`: https://pypi.python.org/pypi/Products.PloneFormGen
        .. _`#35`: https://github.com/collective/collective.cover/issues/35
        .. _`#48`: https://github.com/collective/collective.cover/issues/48
        .. _`#100`: https://github.com/collective/collective.cover/issues/100
        .. _`#114`: https://github.com/collective/collective.cover/issues/114
        .. _`#118`: https://github.com/collective/collective.cover/issues/118
        .. _`#121`: https://github.com/collective/collective.cover/issues/121
        .. _`#123`: https://github.com/collective/collective.cover/issues/123
        .. _`#124`: https://github.com/collective/collective.cover/issues/124
        .. _`#128`: https://github.com/collective/collective.cover/issues/128
        .. _`#129`: https://github.com/collective/collective.cover/issues/129
        .. _`#133`: https://github.com/collective/collective.cover/issues/133
        .. _`#137`: https://github.com/collective/collective.cover/issues/137
        .. _`#138`: https://github.com/collective/collective.cover/issues/138
        .. _`#142`: https://github.com/collective/collective.cover/issues/142
        .. _`#144`: https://github.com/collective/collective.cover/issues/144
        .. _`#146`: https://github.com/collective/collective.cover/issues/146
        .. _`#152`: https://github.com/collective/collective.cover/issues/152
        .. _`#157`: https://github.com/collective/collective.cover/issues/157
        .. _`#158`: https://github.com/collective/collective.cover/issues/158
        .. _`#168`: https://github.com/collective/collective.cover/issues/168
        .. _`#169`: https://github.com/collective/collective.cover/issues/169
        .. _`#171`: https://github.com/collective/collective.cover/issues/171
        .. _`#177`: https://github.com/collective/collective.cover/issues/177
        .. _`#179`: https://github.com/collective/collective.cover/issues/179
        .. _`#183`: https://github.com/collective/collective.cover/issues/183
        .. _`#188`: https://github.com/collective/collective.cover/issues/188
        .. _`#190`: https://github.com/collective/collective.cover/issues/190
        .. _`#191`: https://github.com/collective/collective.cover/issues/191
        .. _`#198`: https://github.com/collective/collective.cover/issues/198
        .. _`#203`: https://github.com/collective/collective.cover/issues/203
        .. _`#204`: https://github.com/collective/collective.cover/issues/204
        .. _`#206`: https://github.com/collective/collective.cover/issues/206
        .. _`#212`: https://github.com/collective/collective.cover/issues/212
        .. _`#218`: https://github.com/collective/collective.cover/issues/218
        .. _`#239`: https://github.com/collective/collective.cover/issues/239
        .. _`#241`: https://github.com/collective/collective.cover/issues/241
        .. _`#244`: https://github.com/collective/collective.cover/issues/244
        .. _`#259`: https://github.com/collective/collective.cover/issues/259
        .. _`#262`: https://github.com/collective/collective.cover/issues/262
        .. _`#271`: https://github.com/collective/collective.cover/issues/271
        .. _`#274`: https://github.com/collective/collective.cover/issues/274
        .. _`#276`: https://github.com/collective/collective.cover/issues/276
        .. _`#278`: https://github.com/collective/collective.cover/issues/278
        .. _`#281`: https://github.com/collective/collective.cover/issues/281
        .. _`#294`: https://github.com/collective/collective.cover/issues/294
        
Keywords: plone cover javascript dexterity
Platform: UNKNOWN
Classifier: Development Status :: 3 - Alpha
Classifier: Environment :: Web Environment
Classifier: Framework :: Plone
Classifier: Framework :: Plone :: 4.2
Classifier: Framework :: Plone :: 4.3
Classifier: Intended Audience :: End Users/Desktop
Classifier: Intended Audience :: System Administrators
Classifier: License :: OSI Approved :: GNU General Public License v2 (GPLv2)
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: JavaScript
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2.6
Classifier: Programming Language :: Python :: 2.7
Classifier: Topic :: Office/Business :: News/Diary
Classifier: Topic :: Software Development :: Libraries :: Python Modules
