Renamed to elm-messenger/messenger-core. That is where the repository lives now. It has not been published as a package under the new name.
Versions published as linsyking/messenger-core still install under that name. 34 versions of 52 come from the new location (see their notes). 7 versions could not be recovered and cannot be installed.
Unavailable. Nobody can download this version any more, with elm or with the Lamdera compiler: Software Heritage has not archived the repo; no fork with tag 14.0.0 found (17 same-name repos checked); no cached copy. Use another version.
A component is an object that you may put in your layers.
These are components that you users can create with custom basedata.
Basedata is the data that components with the same type can share.
For example, you may want a game component to have some common properties like position, velocity, etc.
In this case, your basedata would be a record with these properties.
ConcreteUserComponent
Generate abstract user component from concrete component.
Update a list of abstract user components.
Update a list of abstract user components with block indicator.
It block is True, this function will not update anything.
Update a list of abstract user components with targeted msgs.
Generate render list for one list of components.
Useful when there are several component lists.
The output should be used as the input of viewComponentsRenderList.
View the render list of components.
Useful when there are several component lists.
The input should be generated by several genComponentsRenderList.
View one list of abstract components.
Used when there is only one list of components
Component init type sugar
Component update type sugar
Component updaterec type sugar
Component view type sugar
The second entry is the "z-index" of the component.
Component matcher type sugar
Component storage type sugar
Level component storage type sugar
Abstract component