Ticket #11104 (closed PLIP: wontfix)

Opened 6 years ago

Last modified 5 years ago

Extending plone.app.content

Reported by: rnix Owned by: limi
Priority: minor Milestone: 4.x
Component: User Experience and Interface Version:
Keywords: Cc:

Description

Proposer: Robert Niederreiter, rnix Seconder: None as yet

Motivation

Plone folder_contents view displays item sorting ordered by 'getObjectPositionInParent'.

Now, when managing content, most of the time the user might be interested in newly created items prior to items in order.

So, when having lots of items in a folder current implementation forces the user to scroll and/or navigate through batch.

Assumptions

Having folder_contents sortable by column and the default behavior configurable would solve this issue.

Proposal & Implementation

Behavior of folder_contents Table:

  • Sorting will be invoked by klicking table head of corrensponding column
  • Sorting will be reversed on klicking an already soreted column table head
  • Item sorting column gets disabled (greyed out?) as soon as 'sort_on' changes to anything else than 'getObjectPositionInParent'

Configuration:

  • Configuration is done due to folder controlpanel view
  • Flag wether table head sorting is enabled at all
  • Default sort column selection, defaults to 'getObjectPositionInParent'

Deliverables

  • Extend plone.app.content.browser.tableview.Table, plone.app.content.browser.tableview.TableKSSView and corresponding table.pt
  • Adopt tests in table.txt
  • Extend plone.app.content.browser.foldercontents.FolderContentsTable
  • Add properties page to properties tool (extending propertiestool.xml in plone default profile?)
  • Create controlpanel view for properties
  • Add feature documentation at appropriate location

Risks

As long as base behavior not change no problem is expected (this sure depends on the quality of possible customization)

Participants

Robert Niederreiter, rnix

Progress

Nothing done yet

Change History

comment:1 Changed 6 years ago by esteele

  • Milestone changed from 4.1 to 4.x

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.

Note: See TracTickets for help on using tickets.