Introducing a undo and redo button in ILIAS Page Editor

1 Initial Problem

It is very tedious and only possible via a long click path to undo or redo actions in the ILIAS page editor .
Users are used to work with "undo" and "redo" buttons. These buttons do not exist in the ILIAS page editor yet.

2 Conceptual Summary

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

These mockups show the Undo and Redo buttons displayed as standard buttons in English.

Using the standard buttons

These mockups show the Undo and Redo buttons displayed as standard buttons in German. Usually only "Rückgängig" is used without "machen", which means there is definitely enough space in the slate for the buttons.

Using the standard buttons (German)

These mockups show the Undo and Redo buttons displayed as a Pagination Viewcontrol. When expanded, the version data could be displayed there, as currently shown in the history.

Using the Pagination Viewcontrol

These mockups show the Undo and Redo buttons displayed as a Mode Viewcontrol. However, the use of Mode here is very questionable. A new Viewcontrol might need to be created for this representation.

Using the Mode Viewcontrol (or a new one)

This mockup shows the Undo and Redo buttons displayed as a Section Viewcontrol. If standard buttons cannot be used, this would currently be the favorite option, assuming the introduction of a new Viewcontrol for forward/backward or undo/redo is not considered.

Using the Section Viewcontrol

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

8 Funding

9 Discussion

10 Implementation

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

Test Cases

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.