Nextmatch Header
<et2-nextmatch-header> | Et2NextmatchHeader
Plain nextmatch header caption. This is the webComponent counterpart of legacy
et2_nextmatch_header.
Overview
et2-nextmatch-header is the plain column header for a
Nextmatch list: a label that sits above a column and does nothing
else. It is also the base the rest of the header family builds on.
You rarely write one directly. Headers come from the columns of the rows template a Nextmatch is given, and the interesting ones are the variants that let the user do something to the column.
These examples are not live. A header only has meaning inside a Nextmatch - it reports itself to the list, and a filter header calls back into it to reload - and a Nextmatch needs a server to fetch rows from, which this documentation site does not have.
The family
| Widget | What the user gets |
|---|---|
et2-nextmatch-header
|
a label, nothing interactive |
et2-nextmatch-sortheader
|
click the label to sort by that column |
et2-nextmatch-header-filter
|
a selectbox that filters the list |
et2-nextmatch-header-account
|
the same, choosing an account |
et2-nextmatch-header-entry
|
the same, choosing a linked entry |
et2-nextmatch-header-custom
|
the same, wrapping a widget you name |
et2-nextmatch-header-customfields
|
the application’s custom fields as sortable headers |
How a filter header works
The four filter headers are all the same idea applied to different input widgets.
FilterMixin takes an ordinary input and adds the two things a Nextmatch column filter needs: it
finds the Nextmatch it lives in, and on change it calls that list’s applyFilters() so the rows
reload.
That is the whole abstraction, which is why the variants are so short - each is its own input widget with the mixin wrapped round it:
et2-nextmatch-header-filter = FilterMixin(Et2Select)
et2-nextmatch-header-account = FilterMixin(Et2SelectAccount)
et2-nextmatch-header-entry = FilterMixin(Et2LinkEntry)
et2-nextmatch-header-custom = FilterMixin(<the widget you name>)
So a filter header’s own attributes are the attributes of the widget it is built from. For
et2-nextmatch-header-filter, that means everything on
et2-select.
Usage
Headers go in the rows template’s column definitions, not in the Nextmatch element itself:
<template id="myapp.index.rows">
<grid>
<columns>
<column/>
<column/>
</columns>
<rows>
<row class="th">
<et2-nextmatch-sortheader id="name" label="Name"></et2-nextmatch-sortheader>
<et2-nextmatch-header-filter id="status" emptyLabel="All"></et2-nextmatch-header-filter>
</row>
<row>
<et2-description id="${row}[name]"></et2-description>
<et2-description id="${row}[status]"></et2-description>
</row>
</rows>
</grid>
</template>
See Nextmatch for how a rows template is put together, and Et2Filterbox for filters that live outside the column headers.
Inherited properties (21)
Et2Widget
| Name | Description |
|---|---|
accesskey |
Accesskey provides a hint for generating a keyboard shortcut for the current element. The attribute value must consist of a single printable character. |
actions |
Set Actions on the widget Each action is defined as an object: move: { type: “drop”, acceptedTypes: “mail”, icon: “move”, caption: “Move to” onExecute: javascript:mail_move” } This will turn the widget into a drop target for “mail” drag types. When “mail” drag types are dropped, the global function mail_move(egwAction action, egwActionObject sender) will be called. The ID of the dragged “mail” will be in sender.id, some information about the sender will be in sender.context. The etemplate2 widget involved can typically be found in action.parent.data.widget, so your handler can operate in the widget context easily. The location varies depending on your action though. It might be action.parent.parent.data.widget To customise how the actions are handled for a particular widget, override _link_actions(). It handles the more widget-specific parts. |
align |
Used by Et2Box to determine alignment. Allowed values are left, right |
class |
CSS Class. This class is applied to the outside, on the web component itself. Due to how WebComponents work, this might not change anything inside the component. |
data |
Set the dataset from a CSV |
deferredProperties |
Any attribute that refers to row content cannot be resolved immediately, but some like booleans cannot stay a string because it’s a boolean attribute. We store them for later, and parse when they’re fully in their row. If you are creating a widget that can go in a nextmatch row, and it has boolean attributes that can change for each row, add those attributes into deferredProperties |
disabled |
Defines whether this widget is visibly disabled. The widget is still visible, but clearly cannot be interacted with. Widgets disabled in the template will not return a value to the application code, even if re-enabled via javascript before submitting. To allow a disabled widget to be re-enabled and return a value, disable via javascript in the app’s et2_ready() instead of an attribute in the template file. |
dom_id |
Get the actual DOM ID, which has been prefixed to make sure it’s unique. |
full |
Take every column of a layout, the same as span="all". Boolean rather than a bare
marker so it can be driven from content the way the rest of the template can -
full="@is_wide" resolves through the array manager like any other boolean attribute.
That does mean it needs a value: write full="true", since an empty
full="" resolves to false and removes the attribute again. Reflects for the same
reason grow does.
|
grow |
How much of a layout’s leftover space this widget should take. Only means anything inside a
container that has a layout (see Et2LayoutController): a bare grow or
grow="1" takes an equal share of whatever the non-growing children left over,
grow="2" takes twice what a grow="1" sibling does. It has to reflect.
The layout stylesheet matches the [grow] attribute - CSS cannot see a property - and
transformAttributes() only calls setAttribute() for an attribute the element already carries or a
property declared as reflecting. Widgets built from a .xet are created with
document.createElement() and handed their attributes as an object, so they carry none at that
point: without this declaration grow="1" lands as an inert JS property and nothing in
the layout ever matches it.
|
hidden |
The widget is not visible. As far as the user is concerned, the widget does not exist. Widgets hidden with an attribute in the template may not be created in the DOM, and will not return a value. Widgets can be hidden after creation, and they may return a value if hidden this way. |
id |
Get the ID of the widget |
label |
Header caption text. |
noLang |
Disable any translations for the widget |
parentId |
Parent is different than what is specified in the template / hierarchy. Widget ID of another node to insert this node into instead of the normal location |
span |
How many of a layout’s columns this widget should take.
span="all" is every column wherever the widget landed, span="end" /
span="*" is from its own column to the end of its line. Only means anything inside a
container that has a layout, and only for the column layouts -
stack gives every child the full width anyway. The same name is also read straight
off the XML node by the legacy <grid> widget, for the unrelated job of counting
table cells to merge; that path never looks at the widget, so declaring it here does not disturb
it. Reflecting it does mean a legacy grid’s span="all" cells now carry the attribute
too, which matches nothing outside a layout. Reflects for the same reason grow does.
|
statustext |
Tooltip which is shown for this element on hover |
styles |
WebComponent * |
options |
Get property-values as object |
supportedWidgetClasses |
et2_widget compatability |
LitElement
| Name | Description |
|---|---|
updateComplete |
A read-only promise that resolves when the component has finished updating. |
Methods
| Name | Description | Arguments |
|---|---|---|
setNextmatch()
|
Store owning nextmatch for later interactions (sorting/filtering hooks). |
nextmatch: NextmatchInterface
|
Learn more about methods.
Inherited methods (21)
Et2Widget
| Name | Description |
|---|---|
checkCreateNamespace() |
Checks whether a namespace exists for this element in the content array. If yes, an own perspective of the content array is created. If not, the parent content manager is used. Constructor attributes are passed in case a child needs to make decisions |
clone() |
Creates a copy of this widget. |
createElementFromNode() |
Create a et2_widget from an XML node. First the type and attributes are read from the node. Then the readonly & modifications arrays are checked for changes specific to the loaded data. Then the appropriate constructor is called. After the constructor returns, the widget has a chance to further initialize itself from the XML node when the widget’s loadFromXML() method is called with the node. |
getArrayMgr() |
Returns the array manager object for the given part |
getArrayMgrs() |
Returns an associative array containing the top-most array managers. |
getChildren() |
Get child widgets Use |
getInstanceManager() |
Returns the instance manager |
getPath() |
Returns the path into the data array. By default, array manager takes care of this, but some extensions need to override this |
getRoot() |
Returns the base widget Usually this is the same as getInstanceManager().widgetContainer |
loadFromXML() |
Loads the widget tree from an XML node |
loadingFinished() |
Needed for legacy compatability. |
parseXMLAttrs() |
The parseXMLAttrs function takes an XML DOM attributes object and adds the given attributes to the _target associative array. This function also parses the legacyOptions. N.B. This is only used for legacy widgets. WebComponents use transformAttributes() and do their own handling of attributes. |
set_label() |
Legacy compatibility wrapper. Legacy code paths can call set_label() directly. |
setArrayMgr() |
Sets the array manager for the given part |
setArrayMgrs() |
Sets all array manager objects - this function can be used to set the root array managers of the container object. |
setInstanceManager() |
Set the instance manager Normally this is not needed as it’s set on the top-level container, and we just return that reference |
_handleClick() |
Click handler calling custom handler set via onclick attribute to this.onclick |
destroy() |
et2_widget compatability |
set_class() |
Set the widget class |
set_disabled() |
Wrapper on this.disabled because legacy had it. |
set_statustext() |
supports legacy set_statustext |
Parts
| Name | Description |
|---|---|
base |
Header caption element. |
label |
Header label text. |
Learn more about customizing CSS parts.