Feature Wiki

Information about planned and released features

Tabs

KS-Entry: Toast

1 Guideline

DOM, LESS, JS / Screenshot*:

  • PHP Class:
  • PHP Example:
  • External Library:
  • Status of Entry*: to be revised
  • Status of Implementation*: to be implemented
  • Description*:
    • Purpose: Toast Popovers inform users about communicational events in the broadest sense: i.e. about a request for contact, an invitation to chat or a relevant user logging-in.
    • Composition: Toast Popovers contain a header with a title. The content section displays text along with some action-links  if available.
    • Effect: Toast Popovers are displayed as soon as available. Their display time is composed of the time to live (TTL) and time to show (TTS). TTL defines the time information about the event and is stored on the server to be displayed by clients before being discarded. Time to show defines the timespan for which the message is displayed on the client's screen. They disappear if the page is refreshed.
    • Rival elements:
      1. System Feedback: System Feedback inform about the action of the current user or the state of the stytem while the Toast Popovers inform about communicational events.
  • Background:
  • Context*: Contact invitations are currently displayed as Toast Popovers.
  • Rules*:
    • Style:
      1. Toast Popovers MUST contain a header containing a title and a text body.
      2. Toast Popovers MAY contain action-links for processing requests.
      3. Toast Popovers MAY contain links for processing requests.
    • Interaction:
      1. Toast Popovers MUST disappear on page reloads.
    • Ordering:
      1. Up to two Toast Popovers are to be displayed in a column. More than two Toast Popovers MUST be stacked underneath each other displaying the oldest one on the bottom. If a new message is discarded before an old one, the old ones need to shift one step up in the list.
      2. Toast Popovers MUST NOT conceal functionality but be placed at an empty space. Relations
    • Is A: KS-Entry: Overlay
  • To do for ILIAS 5.2:
    • get rid of the strange icon
    • different Toasts look differently: Online Now, Chat Request for contact. Different colours, and build. They should have one shared look.

2 Status

  • Effective from release: { not approved yet | x.y }
  • Approved by Jour Fixe at: { link to Jour Fixe agenda }
  • Implementation status: { implemented completely | partly implemented | needs implementation }
  • Funding for streamlining existing features: { name of organisation }
  • Implementation of guideline: { all developers | name of responsible developer }

3 Components that are not compliant with the Guideline

4 Discussion

...

Last edited: 31. Mar 2016, 19:54, Amstutz, Timon [amstutz]