Author: Plone Foundation




This package provides a base class for folderish content types based
on `B-trees`_, a.k.a. "large folders" in Plone_.  Storing content in
such folders provides significant `performance benefits`_ over regular
folders.  However, "large folders" do not support explicit ordering of
their contents out-of-the box.  That is, you cannot manually specify the
order of items within the folder, you can only sort things according to
a given criteria after fetching items from the folder.

  .. _`B-tree`:
  .. _`B-trees`:
  .. _`Plone`:
  .. _`performance benefits`:
  .. |---| unicode:: U+2014  .. em dash

Many times, though, it is desirable to be able to explicitly order
a folder's content, for example for items that are related to site
navigation.  Sorting alphabetically often doesn't make sense here.

To compensate ``plone.folder`` provides ordering support for `B-tree`_
folders via the above mentioned base class, which can make use of an
adapter to store the actual order information.  It also comes with two
sample adapter implementations:

  * A default adapter handling order information for all objects
    contained in a folder.  This adapter can be used to build fully
    backwards-compatible drop-in replacements for folderish content.
    In other words, when using this adapter `B-tree`_-based folders should
    behave just like the "regular" folder implementation, but provide some
    of the performance benefits at the same time.

  * An alternative adapter implementation that is targeted towards
    sites with only a relatively small percentage of content for which
    (explicit) order matters.  It'll only manage order information for
    certain content types (via a marker interface).

The latter allows to not having to separate such content from
"non-orderable" content.  Up to now many large sites ended up storing
"orderable" items |---| for example everything related to navigation
and typically only a few |---| in regular folders and the bulk of the
content in "large" folders, most of the time solely for performance
reasons.  This adapter will hopefully help avoid having to make this
distinction in the future and still provide the better performance
characteristics of `B-tree`_ folders.


1.0.5 (2013-12-07)

- Allow reversing the current order, without specifying a key for

- Allow ordering by a method instead of an attribute.

1.0.4 (2012-08-30)

- Update to fix packaging error.

1.0.3 (2012-08-29)

- In, name more dependencies explicitly.

1.0.2 (2012-07-02)

- Update notifyContainerModified import location.

- Add

1.0.1 - 2010-08-08

- Added objectValues and objectItems method to the ordered folder
  implementation, which use objectIds and thus the ordering information. In
  Zope 2.13 BTreeFolder2 was optimized to loop over the internal _tree data
  structure avoiding the objectIds indirection.

1.0 - 2010-07-18

- Avoid dangerous memoization in the DefaultOrdering adapter.

- Update license to GPL version 2 only.

1.0b5 - 2010-03-06

- Remove support for setting ``__parent__`` and ``__name__`` for content
  providing ``IContained`` as it can cause severe performance issues when
  used on Zope 2.x.

1.0b4 - 2010-02-17

- Register all ordering adapter by default now that they can co-exist.

- Add `__getitem__` support to the default ordering adapter to help
  previous/next support in ``.

1.0b3 - 2010-02-09

- Make sure order changes are persisted when using the partial ordering
  [hannosch, witsch]

1.0b2 - 2010-01-28