|
ILIAS
trunk Revision v11.0_alpha-1862-g4e205cb56d4
|
|
ILIAS
trunk Revision v11.0_alpha-1862-g4e205cb56d4
|
Inheritance diagram for FilterInputsTestNoUIFactories: Collaboration diagram for FilterInputsTestNoUIFactories:Public Member Functions | |
| __construct (I\Symbol\Factory $symbol_factory, I\Popover\Factory $popover_factory, I\Legacy\Factory $legacy_factory,) | |
| symbol () | |
description: purpose: > Symbols are graphical representations of concepts or contexts quickly comprehensible or generally known to the user. More... | |
| popover () | |
description: purpose: > Popovers can be used when space is scarce i.e. More... | |
| legacy () | |
description: purpose: > legacy components are used as provisional elements in the UI framework while there are no sophisticated components yet replacing them. More... | |
| Public Member Functions inherited from NoUIFactory | |
| counter () | |
description: purpose: > Counter inform users about the quantity of items indicated by a glyph. More... | |
| button () | |
description: purpose: > Buttons trigger interactions that change the system’s or view's status. More... | |
| card () | |
description: purpose: > A card is a flexible content container for small chunks of structured data. More... | |
| deck (array $cards) | |
description: purpose: > Decks are used to display multiple Cards in a grid. More... | |
| listing () | |
description: purpose: > Listings are used to structure itemised textual information. More... | |
| image () | |
description: purpose: The Image component is used to display images of various sources. More... | |
| legacy () | |
description: purpose: > legacy components are used as provisional elements in the UI framework while there are no sophisticated components yet replacing them. More... | |
| panel () | |
description: purpose: > Panels are used to group titled content. More... | |
| modal () | |
description: purpose: The Modal forces users to focus on the task at hand. More... | |
| progress () | |
description: purpose: > A Progress component is designed to represent the users advancement within a certain process or task. More... | |
| dropzone () | |
description: purpose: > Dropzones are containers used to drop either files or other HTML elements. More... | |
| popover () | |
description: purpose: > Popovers can be used when space is scarce i.e. More... | |
| divider () | |
description: purpose: > A divider marks a thematic change in a sequence of other components. More... | |
| link () | |
description: purpose: > Links are used navigate to other resources or views of the system by clicking or tapping them. More... | |
| dropdown () | |
description: purpose: > Dropdowns reveal a list of interactions that change the system’s status or navigate to a different view. More... | |
| item () | |
description: purpose: > An item displays a unique entity within the system. More... | |
| viewControl () | |
description: purpose: > View Controls switch between different visualisation of data. More... | |
| breadcrumbs (array $crumbs) | |
description: purpose: > Breadcrumbs is a supplemental navigation scheme. More... | |
| chart () | |
description: purpose: > Charts are used to graphically represent data in various forms such as maps, graphs or diagrams. More... | |
| input () | |
description: purpose: > In opposite to components with a purely receptive or at most navigational character, input elements are used to relay user-induced data to the system. More... | |
| table () | |
description: purpose: > Tables present a set of uniformly structured data. More... | |
| messageBox () | |
description: purpose: > Message Boxes inform the user about the state of the system or an ongoing user task. More... | |
| layout () | |
description: purpose: > Layout components are components used for the overall construction of the user interface. More... | |
| mainControls () | |
description: purpose: > Main Controls are components that are always usable, depending only on overall configuration or roles of the user, not depending on the current content. More... | |
| tree () | |
description: purpose: > Trees present hierarchically structured data. More... | |
| menu () | |
description: purpose: > Menus let the user choose from several (navigational) options. More... | |
| symbol () | |
description: purpose: > Symbols are graphical representations of concepts or contexts quickly comprehensible or generally known to the user. More... | |
| toast () | |
description: purpose: Toasts are temporary messages from the system published to the user. More... | |
| player () | |
description: purpose: > The Player component is used to play and control a media source. More... | |
| launcher () | |
description: purpose: > The Launcher starts an object, a process or a workflow. More... | |
| helpTopics (string ... $topic) | |
description: purpose: > Help Topics can be attached to certain components. More... | |
| entity () | |
description: purpose: > An Entity displays information about entities within the system, when the purpose is to represent the entity itself. More... | |
| prompt () | |
description: purpose: > A Prompt requires a user to make some inputs to the system, like making choices, acknowleding an important information or filling out a form. More... | |
Protected Attributes | |
| I Symbol Factory | $symbol_factory |
| I Popover Factory | $popover_factory |
| I Legacy Factory | $legacy_factory |
Definition at line 28 of file FilterInputTest.php.
| FilterInputsTestNoUIFactories::__construct | ( | I\Symbol\Factory | $symbol_factory, |
| I\Popover\Factory | $popover_factory, | ||
| I\Legacy\Factory | $legacy_factory | ||
| ) |
Definition at line 34 of file FilterInputTest.php.
References $legacy_factory, $popover_factory, and $symbol_factory.
| FilterInputsTestNoUIFactories::legacy | ( | ) |
description: purpose: > legacy components are used as provisional elements in the UI framework while there are no sophisticated components yet replacing them.
composition: > Legacy component regularly contain rendered HTML.
rules: usage: 1: > Legacy components MUST only be used to ensure backwards compatibility with existing UI elements in ILIAS or to implement temporal and provisional
Implements ILIAS\UI\Implementation\FactoryInternal.
Definition at line 54 of file FilterInputTest.php.
References $legacy_factory.
| FilterInputsTestNoUIFactories::popover | ( | ) |
description: purpose: > Popovers can be used when space is scarce i.e.
within List GUI items, table cells or menus in the Header section. They offer either secondary information on object like a preview or rating to be displayed or entered. They display information about ongoing processes composition: > Popovers consist of a layer displayed above all other content. The content of the Popover depends on the functionality it performs. A Popover MAY display a title above its content. All Popovers contain a pointer pointing from the Popover to the Triggerer of the Popover. effect: > Popovers are shown by clicking a Triggerer component such as a Button or Glyph. The position of the Popover is calculated automatically be default. However, it is possible to specify if the popover appears horizontal (left, right) or vertical (top, bottom) relative to its Triggerer component. Popovers disappear by clicking anywhere outside the Popover or by pressing the ESC key. rivals: > Modals: > Modals hide all other content while Popovers do not prevent interaction with other parts of the current context. rules: usage: 1: > Popovers MUST NOT contain horizontal scrollbars. 2: > Popovers MAY contain vertical scrollbars. The content component is responsible to define its own height and show vertical scrollbars. 3: > If Popovers are used to present secondary information of an object, they SHOULD display a title representing the object. interaction: 1: > A Popover MUST only be displayed if the Trigger component is clicked. This behaviour is different from Tooltips that appear on hovering. Popovers disappear by clicking anywhere outside the Popover or by pressing the ESC key. style: 1: Popovers MUST always relate to the Trigger component by a little pointer. accessibility: 1: > There MUST be a way to open the Popover by only using the keyboard. 2: > The focus MUST be inside the Popover, once it is open if it contains at least one interactive item. Otherwise the focus MUST remain on the Triggerer component. 3: > The focus MUST NOT leave the Popover for as long as it is open. 4: > There MUST be a way to reach every control in the Popover by only using the keyboard. 5: > The Popover MUST be closable by pressing the ESC key. 6: > Once the Popover is closed, the focus MUST return to the element triggering the opening of the Popover or the element being clicked if the Popover was
Implements ILIAS\UI\Implementation\FactoryInternal.
Definition at line 49 of file FilterInputTest.php.
References $popover_factory.
| FilterInputsTestNoUIFactories::symbol | ( | ) |
description: purpose: > Symbols are graphical representations of concepts or contexts quickly comprehensible or generally known to the user.
composition: Symbols contain a graphical along with textual representation describing, what the graphic is depicting. rules: accessibility: 1: Symbols MUST have labels which then might be used to display some alternative text (e.g. as alt attribute). 2: The label of the Symbol MUST NOT be displayed, if the Symbol has a purely decorative function (as e.g. in
Implements ILIAS\UI\Implementation\FactoryInternal.
Definition at line 44 of file FilterInputTest.php.
References $symbol_factory.
|
protected |
Definition at line 32 of file FilterInputTest.php.
Referenced by __construct(), and legacy().
|
protected |
Definition at line 31 of file FilterInputTest.php.
Referenced by __construct(), and popover().
|
protected |
Definition at line 30 of file FilterInputTest.php.
Referenced by __construct(), and symbol().
1.8.13 (using Doxyfile)
