Show Advanced KnowledgeHide Advanced Knowledge

KS Listing Panels with Selection

1 Initial Problem

This feature wiki page discusses options to enable the selection of items in standard listing panels. A solution for this is necessary to move the repository objects list to the kitchen sink.

Views that should make use of this:

Object Selection in Repository Lists

Calendar Selection in Secondary Panel

2 Conceptual Summary

Killing, Alexander [alex], 20 May 2019:

We need to extend the Standard Panel Listing to include Checkboxes (or similar visuals that indicate selections) and "Select All" checkboxes.

On the repository administration pages, we are neither inside a standard form nor inside a filter, so we have another sort of container for inputs (we need a new type of "NamingSource" for the checkboxes).

The repository administration screen currently contains a lot of things in its main HTML form, mostly

• Multiple object lists
• All side "Secondary Panels"

We do not have a KS component on this level yet and it may take some time to figure out how this will work conceptually.

Maybe it is another option to inject a NamingSource into the Listing Panels and their Items from the consumer side for now.

3 User Interface Modifications

3.1 List of Affected Views

• Repository > Container > Manage
• Calendar > Calendar Selection Secondary Panel

3.2 User Interface Details

The implementaition of the lists should move to the KS Standard Listing Panels. There might be no major visual change for the end user.

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: {Please add your name.}
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.