http://www.bea.com/servers/portal/weblogic-portal/8.0
element look-and-feel-content

Documentation

Defines a look and feel to replace the existing look and feel.

A Look and Feel is made up of two parts referenced by a single XML file: skins and skeletons. Skins contain the graphics, styles, and JavaScript code that determine the look of a desktop. Skeletons control the physical boundary rendering of all portal components.

Properties

This component is not nillable.

Model

<look-and-feel-content
  default-window-icon = xs:string
  default-window-icon-path = xs:string
  definition-label = xs:string
  description = xs:string
  markup-name = xs:string
  skeleton = xs:string
  skeleton-path = xs:string
  skin = xs:string
  skin-path = xs:string
  title = xs:string>

</look-and-feel-content>

default-window-icon

The path to an image file (icon) that displays in the upper-left corner of the window. The path name must be relative to the root of the portal Web application.

Type:

xs:string

Use:

optional

Form:

unqualified

default-window-icon-path

The path to the default window icon's directory. The path name must be relative to the root of the portal Web application. If the portal that you want to extend is based on a BEA template, then the value for this attribute is "/images/".

Type:

xs:string

Use:

optional

Form:

unqualified

definition-label

A unique definition label for this look and feel.

Type:

xs:string

Use:

optional

Form:

unqualified

description

An optional description of this look and feel. Some IDE components can display this description. It does not display to your portal customers.

Type:

xs:string

Use:

optional

Form:

unqualified

markup-name

Used only for portals that support customization. If a portal supports customization, then this value must match a markupName attribute defined in a *.laf (look-and-feel) file in the portal Web application. At request time, the system will find the appropriate .laf file and use the look-and-feel settings in that file, overriding what has been set in the .portal file or extension.

Type:

xs:string

Use:

optional

Form:

unqualified

skeleton

The name of the skeleton that this look and feel will use. For example: "classic". When you deploy the portal extension, this name is appended to the path value that you specify in the "skeleton-path" attribute.

Type:

xs:string

Use:

optional

Form:

unqualified

skeleton-path

The path to the skeleton's parent directory. The path name must be relative to the root of the portal Web application. If the portal that you want to extend is based on a BEA template, then the value for this attribute is "/framework/skeletons/".

Type:

xs:string

Use:

optional

Form:

unqualified

skin

The name of the skin that this look and feel will use. For example: "classic". When you deploy the portal extension, this name is appended to the path value that you specify in the "skin-path" attribute.

Type:

xs:string

Use:

optional

Form:

unqualified

skin-path

The path to the skin's parent directory. The path name must be relative to the root of the portal Web application. If the portal that you want to extend is based on a BEA template, then the value for this attribute is "/framework/skins/".

Type:

xs:string

Use:

optional

Form:

unqualified

title

The title for this look and feel. Some IDE components can display this title. It does not display to your portal customers.

Type:

xs:string

Use:

optional

Form:

unqualified

Source

<xs:element name="look-and-feel-content">
  <xs:complexType>
    <xs:attribute name="title" type="xs:string">
    </xs:attribute>
    <xs:attribute name="description" type="xs:string">
    </xs:attribute>
    <xs:attribute name="definition-label" type="xs:string">
    </xs:attribute>
    <xs:attribute name="skin" type="xs:string">
    </xs:attribute>
    <xs:attribute name="skin-path" type="xs:string">
    </xs:attribute>
    <xs:attribute name="skeleton" type="xs:string">
    </xs:attribute>
    <xs:attribute name="skeleton-path" type="xs:string">
    </xs:attribute>
    <xs:attribute name="default-window-icon" type="xs:string">
    </xs:attribute>
    <xs:attribute name="default-window-icon-path" type="xs:string">
    </xs:attribute>
    <xs:attribute name="markup-name" type="xs:string">
    </xs:attribute>
  </xs:complexType>
</xs:element>