Further Improvement of Content Style Editor

1 Initial Problem

Kunkel, Matthias [mkunkel], October 16, 2017: Could we please offer a better support of defined colour schemes? It would be great if these colours could be easy be accessible everywhere where now a colour picker is placed. Because if you define colours for your skin you want to use them easily (and not working with two open tabs as workaround).

New Colour Picker

Zenzen, Enrico [ezenzen]

• If you change the title of a color, this change should be applied to all Style Classes. At the moment the change is not applied and all Style Classes lose their color. Users have to adjust the color values for each Style Class.
• When deleting images from a Content Style, a confirmation dialog is missing.

Tödt, Alexandra [atoedt] 

1. Lables in component and style editor are not the same: In the tab Styleclass in the sub-tab Questions the lables of the variables do not map to the actual settings in the question editor i.e. in the test. This should be corrected. 
   • in the question editing form the lable is Question.
   • in the style editor the lable is title. This is misleading / obscure to users who want to style questions. 
2. relative Sizes in Default Content Style: Question title, Question text and Answer options may get an even better visual balance. Maybe Answers sould be bigger but not as big as Question Text (we have been there and it was bad). If the Content Stlye is to be changed please make sure to get the Jour Fixes blessing.

Kunkel, Matthias [mkunkel],

• ad 2.3: This would be the perfect moment to introduce the option for multiple link styles. If you use white or light text colours on dark backgrounds you cannot use links in the text at the moment.

2 Conceptual Summary

{ Please add a brief summary on how you would like the problem to be solved. }

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of all views (screens) of ILIAS that should be modified, newly introduced or removed. }

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

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

8 Funding

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

• …

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