Show more for Deck of Card

1 Initial Problem

The Members' Gallery uses the Deck of Cards. In courses with many members, it may take a long time to display the Members tab because all the cards have to be loaded first.
The possibility to show only a part of all cards should help here, so that the member gallery can be loaded faster.

2 Conceptual Summary

The UI element Deck of Cards is to be given the option of a "Show more" button. This will cause a certain number of cards to be loaded and displayed. If one scrolls to the end of the list, a "Show more" button is displayed, with which further cards can be displayed with a click.

Alternative: In the timeline of a group, reloading is currently possible without actively clicking on a button. If you are at the bottom of the page, the next content is reloaded.

3 User Interface Modifications

3.1 List of Affected Views

• Course > Members > Membergallery
• Group > Members > Membergallery
• kann auf jedem Deck of Cards eingebaut werden.

3.2 User Interface Details

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. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Seiler, Yvonne [yvseiler] (Universität Bern)
• 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.}

8 Funding

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

• Universität Bern

9 Discussion

10 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}.