Ticket #9544 (closed PLIP: wontfix)

Opened 6 years ago

Last modified 5 years ago

Improved Large Folder behaviour and user interface

Reported by: dukebody Owned by:
Priority: minor Milestone: Future
Component: General Version:
Keywords: Cc:

Description (last modified by dukebody) (diff)

 http://plone.org/products/plone/roadmap/116

The Large Folder in Plone should be improved to work better with large amounts of content, since this is the primary use case for it.

Proposed by

Alexander Limi

Proposal type

User interface

State

being-discussed

Definitions

Large Folder

Here used as a common term for any BTree-based folder, which are designed to hold thousands of elements. They are not the same in all cases, but the improvements proposed here are applicable to any BTree-based folder structure.

Motivation

Currently, Plone has a content type for holding thousands of items that is based on a BTree structure called the Large Folder, that supports thousands of content items in an efficient way - and has no ordering support.

This content type is created for a radically different use case than the normal folder, and should have an interface and a behaviour that matches and optimizes this usage.

There are three main areas where Large Folders could use improvement:

  • Behaviour in the navigation tree
  • The interface when manipulating the contents of the folder (potentially containing thousands of items)
  • The view of the folder

Proposal

The changes proposed are:

Navigation tree changes

Large Folders should not expand in the navigation tree. The currently selected item should be there, but its sieblings should not be shown. This is an obvious change, since there could easily be thousands of items in the navigation tree.

Folder Contents view changes

The Folder Contents view of a Large folder should be search-based. Ideally, we want this to be a LiveSearch-like implementation of the table view that is the contents view of a normal folder.

Default view changes

The default view of a Large Folder should at the very least have batching — and preferrably have a search-based interface like the Folder Contents one, if possible.

Risks

We should evaluate what developers are available for this PLIP and go for the non-LiveSearch-like implementation if we don't have the available resources to do it properly.

Progress log

This is the second part of the folder contents updates; no bundle for the deadline here either since it needs a decision in the AJAX discussion. (There are of course parts that could have been done in the meantime, but it's always harder to motivate people when there's no UI on top ;)

Change History

comment:1 Changed 6 years ago by dukebody

  • Description modified (diff)

comment:2 Changed 5 years ago by rossp

  • Status changed from new to closed
  • Resolution set to wontfix

PLEASE READ THIS AND RE-OPEN VALID PLIPS!

As we launch the new PLIP process we'd like to see which PLIPs:

  • are still appropriate/needed
  • still have owners/proposers/champions
  • still have available implementers

If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.

comment:3 Changed 4 years ago by davisagli

  • Component changed from Infrastructure to General
Note: See TracTickets for help on using tickets.