Start page
Start page

Start page / Template development / Forms / Input components / LIST (new)

FS_LISTAvailable from FirstSpirit Version 4.2

The input component FS_LIST enables lists to be created on the basis of FirstSpirit data of different origin and type.

The type parameter in the DATASOURCE tag is used to define which data FS_LIST will access:

<FS_LIST name="IDENTIFIER">
<DATASOURCE type="DATATYPE">
...

The following data types are available:

Type

Creation and management of

Replaces

DATABASE

Data set lists

CMS_INPUT_CONTENTLIST, CMS_INPUT_TABLIST

INLINE
(<TEMPLATES source="sectiontemplates"/>)

Section lists

CMS_INPUT_CONTENTAREALIST

INLINE
(<TEMPLATES source="linktemplates"/>)

Link lists

CMS_INPUT_LINKLIST

PAGE

List of the sections on a page

CMS_INPUT_SECTIONLIST

SERVICE

Lists with data from external modules / components

 
   

Depending on the application case, diverse functions and types of display can be configured for FS_LIST. The tags and parameters that can be used by FS_LIST are listed and documented separately by data type on this page's sub-pages. They can also be accessed using the links in the table above.

Important The syntax of FS_LIST was revised with Version 4.2R4. Therefore, uses of FS_LIST created with a FirstSpirit version lower than 4.2R4 must be adjusted in line with the syntax given below.
Important Important note about the nesting of FS_LIST input components
FS_LIST input components can be used in a FS_LIST input component (“nesting”, see for example this page too). If too many FS-LIST input components are nested this can result in problems concerning the usability for editors and the maintainability in development as well as in loss of performance. Experience has shown that nestings with more than 3 levels should be avoided as far as possible!

Especially it is advised not to use language dependent input components in a language dependent FS_LIST input component with type INLINE / SECTIONTEMPLATES(see also parameter useLanguages). Particularly in combination with rules, this can lead to configurations which make storing impossible!

Examples

An example of the input component FS_LIST in Version 4.2R4 and higher:

<FS_LIST name="IDENTIFIER" rows="5">
<DATASOURCE type="database" useLanguages="no">
<ACTIONS>
<ACTION name="ADD"/>
<ACTION name="REMOVE"/>
<ACTION name="UP"/>
<ACTION name="DOWN"/>
<ACTION name="GOTO"/>
<ACTION name="EDIT"/>
</ACTIONS>
<COLUMNS>
<COLUMN show="no">#identifier</COLUMN>
</COLUMNS>
<LAYOUT>
<ADD component="toolbar" constraint="top"/>
<ADD component="overview" constraint="center"/>
<ADD component="stackedview" constraint="bottom"/>
</LAYOUT>
<table>TABLETEMPLATE</table>
</DATASOURCE>
<LANGINFOS>
<LANGINFO lang="*" label="Selection of data sets"/>
</LANGINFOS>
</FS_LIST>

An example of the input component FS_LIST up to and including Version 4.2R2:

<FS_LIST name="IDENTIFIER" hFill="YES">
<LANGINFOS>
<LANGINFO lang="DE" label="TEXT" description="TEXT"/>
<LANGINFO lang="*" label="TEXT" description="TEXT"/>
</LANGINFOS>
<SOURCES>
<TEMPLATE name="IDENTIFIER_SECTIONTEMPLATE"/>
</SOURCES>
</FS_LIST>

See also the example project.

© 2005 - 2014 e-Spirit AG | All rights reserved. | Last change: 2013-07-04