- These tags are common tags for displaying Content Items. For most Content Types - there are special tags provided by other files. + These tags are common tags for displaying Content Items. + For most Content Types there are special tags provided by other + files.
- The content-item element with the attribute mode set to
- detail or without the attribute inserts the HTML representation of the
- detail view of the current content item. The content item can either be the greeting
- item or normal item.
+ The content-item element with the attribute <
+ code>mode set to detail or without the
+ attribute inserts the HTML representation of the detail view of
+ the current content item. The content item can either be the
+ greeting item or normal item.
- The HTML representation of a content item is defined using special templates
- with the contentitem-layout element as root. Usually these templates
- are located in the templates/content-items folder. Which template is
- used for a particular content item is defined by the conf/templates.xml
- file. In this file there is a content-items element below the
- templates element. The association between templates and
- content items is described by the content-item elements in the
- content-items element. The content-item has four
- optional attributes (at least on must be present) which are used to limit the
- content items for which a template is used. The four attributes are:
+ The HTML representation of a content item is defined using
+ special templates with the contentitem-layout
+ element as root. Usually these templates are located in the
+ templates/content-items folder. Which template is
+ used for a particular content item is defined by the
+ conf/templates.xml file. In this file there is a
+ content-items element below the
+ templates element. The association between
+ templates and content items is described by the
+ content-item elements in the
+ content-items element. The
+ content-item has four optional attributes
+ (at least on must be present) which are used to limit the
+ content items for which a template is used. The four attributes
+ are:
oid
content-section
category and content-type
- attributes.
+ The name of the content section to which the item belongs.
+ Can be used in combination with the category
+ and content-type attributes.
category
content-type
@@ -116,7 +125,9 @@
- The content-item with the mode attribute set to
- link insert the HTML representation of a content item. In this case
- the content item to show is provided using by a XSL parameter which has to be
+ The content-item with the mode
+ attribute set to link insert the HTML
+ representation of a content item. In this case the content item
+ to show is provided using by a XSL parameter which has to be
provided by a surrounding tag like related-link.
- The content-item element with the mode attribute set to
- list inserts the HTML representation of the the list view of a content
- item. The list view is primarily used in object lists.
+ The content-item element with the mode
+ attribute set to list inserts the HTML
+ representation of the the list view of a content item. The list
+ view is primarily used in object lists.
- As for the detail view, the HTML representation of the list view of a conten item is
- defined using special templates with the contentitem-layout element as
- root. Usually these templates are located in the
- templates/content-items folder. Which is used for a particular content
- item is defined in the conf/templates.xml file. In this file there is
- a content-items element below the templates element.
+ As for the detail view, the HTML representation of the list view
+ of a conten item is defined using special templates with the
+ contentitem-layout element as root. Usually these
+ templates are located in the
+ templates/content-items folder. Which is used for a
+ particular content item is defined in the
+ conf/templates.xml file. In this file there is a
+ content-items element below the
+ templates element.
- There three attributes which can be used to define in which cases a specific - template is used: + There three attributes which can be used to define in which + cases a specific template is used:
style attribute to the content-item attribute
- in the application layout file.
+ Used to select a specific style for the list view of the
+ item. To select a style add a style attribute
+ to the content-item attribute in the
+ application layout file.
category
+ Root element for the layout templates describing a content item + layout. +
++ Show the title of the current content item. +
+- Provides a link to content item itself. Useful if a content item is shown using a - portlet and you want to create a link to the normal detail view of the item. + Provides a link to content item itself. Useful if a content item + is shown using a portlet and you want to create a link to the + normal detail view of the item.
+ Generic tag to test if a content item has a specific property.
+ The tags enclosed by if-property are only
+ processed if the content item has a property with the provided
+ name.
+
+ Generic tag to show the value of the property with the + specified name. This tag can be used if there are no special + tags for a content type. +
+
+ Generic tag for showing date properties. The format of the
+ date is configured using one or more date-element
+ inside this tag.
+
+ The tags in these file are used to create the HTML + representation of the FormItem (and the FormSectionItems used + by the FormItem). +
++ Outputs the description of a FormItem. +
++ Outputs the components (the controls) of a form. Unfortunately + is not yet possible to customise the HTML of the form + components. +
++ The tags in these file can be used to output the special + properties of the file storage item. +
++ Outputs the description of a file storage item. +
++ Outputs the link to download the file associated with the + file storage item. The tag has an optional attribute to decide + if the link should force a download or not. +
+
+ If set to stream the file will be opened
+ in the approbriate program or browser plugin if available.
+ If not set or set to download the link
+ should cause a downlaod.
+
+ The real behaviour depends on the configuration of the + browser used to to view the site. +
+
+ If set to true the name of the file associated
+ with the file storage item is included into the link.
+
+ The tags in these file are used to create the HTML representation + of types derived from GenericOrganzationalUnit, for example + SciProject, SciDepartment or SciInstitute. +
++ The informations about a organizational unit are provided + in several sections (tabs). +
++ Root element for outputting the available tabs of organizational + unit. +
++ This tag encloses the HTML for a individual tab. It also + passes the URL for viewing the tab to the enclosed elements. +
++ Outputs the name of the avilable tab. +
+
+ This tag is alternative for tab-name. It uses
+ the tab name and the type name of the orga unit to lookup
+ the label in the localisable texts of the theme. More
+ specifially it looks for a text in in
+ texts/$orgaunit-type-name.xml with the name of
+ the tab as id.
+
+ Enclosing tag for several other tags for displaying informations + about a organisational unit. The tag passes several informations + to the enclosed tags. +
+
+ Encloses the tags for displaying the informations from the
+ current tag. The immediate sub elements of this tag can only
+ be tab. The name attribute of the
+ tab elements defines for which tab the layout
+ enclosed by a tab element is used.
+
+ Generic tag to output a property in a tab of a orga unit. +
+
+ Outputs the content of the current tab as text. If the
+ disable-output-escaping attribute is set
+ to true the content is shown as it is. Otherwise
+ some characters are escaped.
+
+ Disable output escaping? +
+
+ Outputs the value of the addendum property
+ of an orga unit.
+
+ Root tag for showing the list of members of an orga unit. +
++ Encloses the layout for an individual member entry. +
+
+ Outputs the status of the current member. The text itself
+ is retrieved from texts/$orgaunit-type-name.
+
+ Outputs the role of the current member. The text itself
+ is retrieved from texts/$orgaunit-type-name.
+
+ Shows the contact entries associated with a member. +
++ +
++ Root tag for outputting the contact associated with an orga unit. +
++ Outputs the person associated with orga unit contact. +
++ Outputs the contact entries of the orga unit contact. +
+conf/css-files.xml to determine for which CSS an
- <link> element should be added to the HTML output. For a full
- explanation please refer to the CSS files section.
+
+ Invokes the foundry CSS loader. The CSS loader will parse the file
+ conf/css-files.xml to determine for which CSS an
+ <link> element should be added to the HTML output. For a full
+ explanation please refer to the CSS files section.
+
+ If you are using LESS for
+ your stylesheets you can include the LESS JavaScript compiler to
+ compile your LESS stylesheets on the fly to CSS. To do that
+ you must first set the less-onthefly setting
+ in conf/global.xml to true.
+ In the conf/css-files.xml each CSS file entry
+ which is created from a LESS file must have a less
+ attribute with its value set to true. Also for
+ these files the file extension (.css) should be
+ omitted.
+