Skins are a way to provide branding and navigation for ATG Self Service. The skin provides the entire HTML surrounding the current view.
Skins use a
SkinDefintion
item descriptor to provide the data for theindex.jsp
pageThe
index.jsp
page uses thestyle
attribute as the name of aSegmentOption
that is included in the<head>
sectionThe
index.jsp
page uses thejavascript
attribute as the name of aSegmentOption
that is included in the<head>
sectionThe
index.jsp
page uses thelayoutUrl
attribute to include the skin in the<body>
section. ThelayoutUrl
is included using a<dsp:include>
tag.The skin may define additional segment options using the
additionalOptions
attribute. The Skin Settings page in Service Admin uses thehint
attribute of theSegmentOption
to determine which editor to place in the page. Valid values forhint
are:null
,int
,string
,longstring
, andBoolean
.The skin JSP page should include the
view.jsp
page to render the actual view.The skin needs to provide navigation for the application. The skin should have access to an object that lists all the currently available views.
The skin author is responsible for providing the JSP page to be rendered, defining the SkinDefinition
instance in the repository, and setting up the SegmentOptions
in the repository. The skin author must create at least a SegmentOption
for style
and a SegmentOption
for javascript
, even if the default value is empty. The skin author can define additional options that are used by the skin and these should be created in the repository.
Authoring a skin is a developer task. Configuring the SegmentOptions
for a skin should be done in the Service Admin > Skin Settings page.