Feature Wiki

Information about planned and released features

Tabs

KS-Entry: Default Button

Page Overview

[Hide]

1 Guideline

  • DOM, LESS, JS / Screenshot*:
  • Less Variables:
    • Color: btn-default-color
    • Background: btn-default-background
    • Border: btn-default-border
  • PHP Class:  ilLinkButton (ilButton), ilSubmitButton (ilButton)
  • PHP Example:
  • External Library: Bootstrap Button
  • Status of Entry: To be revised
  • Status of Implementation: to be implemented
  • Description*:
    • Purpose: The Default Button is the standard Button to be used in ILIAS. If there is no good reason using another Button instance in ILIAS, this is the one that should be used.
    • Composition: The Default Button uses the Primary Color as background.
  • Background:
  • Context*:
  • Rules:
    • Usage:
      1. Default Buttons MUST be used if there is no good reason using  another instance.
    • Ordering:
      1. The most important Default Button SHOULD be first in reading direction if there are several Buttons.
      2. In the Toolbar and in Forms special regulations for the ordering of the Buttons MAY apply.
    • Responsiveness:
      1. The most important Default Button in Multi-Action Bars MUST be sticky (stay visible on small screens).
  • Relations:
    • Is A: Button
    • Must use: Text
    • May use: Text, Glyph
  • Todo in ILIAS 5.1:
    • Less:
      1. Currently default buttons are rendered using a custom less mixin which uses, lighten (brand-primary, 15%) to color the background and border of the button. This is misleading, we have a variable btn-default-bg/border for that.
      2. Currently white is used for the button color, this is misleading since there exists a less variable bt-default-color for that.
    • In the exercise the “List all Submission” button opens a view and should be displayed as the link it actually is.  
    • In the Data Collection standard buttons as “Delete” or “Save” are appended with other text this should be changed to plain “Save” and “Delete”.  
 
 

2 Status

  • Effective from release: Release 5.2
  • Approved by Jour Fixe at: JourFixe-2016-06-21
  • Implementation status: partly implemented
  • Funding for streamlining existing features: Universität Bern
  • Implementation of guideline: { all developers | name of responsible developer }

3 Components that are not compliant with the Guideline

  • …

4 Discussion

JourFixe, ILIAS [jourfixe], June 20, 2016: Highly appreciated and scheduled for 5.2.

Last edited: 21. Jun 2016, 12:36, Kunkel, Matthias [mkunkel]