Feature Wiki
Information about planned and released features
Tabs
KS-Entry: Form Subsettings
Page Overview
[Hide]1 Guideline
- Name: Form Subsettings
- DOM, LESS, JS / Screenshot*:
![](./data/docu/mobs/mm_47566/form-subsettings.png?il_wac_token=f74ea90c8cf6a7a126816376f9833d2b76f2af89&il_wac_ttl=5&il_wac_ts=1725752718)
- PHP Class: ilFormGUI, ilSubEnabledFormPropertyGUI
- PHP Example:
- External Library: Inspired by Bootstrap forms-horizontal
- Status of Entry*: to be revised
- Status of Implementation*: to be implemented
- Description*:
- Purpose: Settings can be nested allowing for settings-dependent further configuration.
- Composition: Subsettings are underneath the Setting they depend on. The Subsetting is indented to visually confirm said dependence.
- Effect: Subsettings are revealed after enabling the selection control of a setting. If the setting is not enabled, the subsetting remains hidden.
- Background:
- Context*:
- Feature Wiki References:
- http://www.ilias.de/docu/goto_docu_wiki_wpage_3495_1357.html
- Rules:
- Usage:
- There MUST NOT be a nesting of more than one subsetting (see Jour Fixe comment in feature wiki reference). The only exception to this rule is the required quantification of a subsetting by a date or number. These exceptions MUST individually accepted by the Jour Fixe.
- Composition:
- Subsettings MUST bear an identifier.
- Interaction:
- Subsetting MUST NOT be enabled by any other form element than a checkbox or a radio input group.
- Ordering:
- Subsettings of a setting can be stacked. The most relevant subsetting MUST be the first subsetting in the stack. The least relevant comes last in the stack.
- Usage:
- Todo in ILIAS 5.1:
- Sometimes the subsettings have a identifier but only state the options, sometimes not, see example test-settings.
- Relations
- Is A: Form
- Must use: Form Titled Sections
2 Status
- Effective from release: Release 5.2
- Approved by Jour Fixe at: Dec 21, 2015
- Implementation status: partly implemented
- 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
Jour Fixe, Dec 21, 2015: Highly appreciated and schedule for 5.2.
Last edited: 8. Apr 2016, 12:26, Amstutz, Timon [amstutz]