KS-Entry: Modal

1 Guideline

• Name: Modal
• DOM, LESS, JS / Screenshot*: Abstract
• PHP Class: ilModalGUI
• PHP Example:
• External Library: 
• Status of Entry: Proposed
• Status of Implementation: to be implemented
• Description*:
  • Purpose: The Modal forces users to focus on the task at hand.
  • Composition: A Modal is a full-screen dialog on top of the greyed-out ILIAS screen. The Modal consists of a header with a close button and a typography modal title, a content section and might have a footer.
  • Effect: All controls of the original context are inaccessible until the Modal is completed. Upon completion the user returns to the original context.
  • Rival elements: Modals have some relations to popovers. The main difference between the two is the disruptive nature of the Modal and the larger amount of data that might be displayed inside a modal. Also popovers perform mostly action to add or consult metadata of an item while Modals manipulate or focus items or their sub-items directly.
• Background:
  • http://quince.infragistics.com/Patterns/Modal%20Panel.aspx

• Feature Wiki References:
  • DR 5.2 - Pushing Modals
  • DR 5.1 - Issue 02: Keep Drop-Downs in Viewport / Overlay handling
• Rules:
  • The main purpose of the Modals MUST NOT be navigational. But Modals MAY be dialogue of one or two steps and thus encompass “next”-buttons  or the like.
  • Modals MUST NOT contain other modals (Modal in Modal).
  • Modals SHOULD not be used to perform complex workflows.
  • Modals MUST be closable by a little “x”-button on the right side of the header.
  • Modals MUST contain a title in the header.
• Relations
  • Is A: KS-Entry: Overlay
  • Children: KS-Entry: Round-Trip Modal, KS-Entry: Interruptive Modal, KS-Entry: Lightbox Modal

2 Todo for ILIAS 5.2

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

4 Components that are not compliant with the Guideline

• …

5 Discussion

...