IBM WebSphere Portal 6.0.X：主题与皮肤开发详解

1星 | 下载需积分: 0 | PDF格式 | 397KB | 更新于2025-01-07 | 160 浏览量 | 举报

在IBM WebSphere Portal 6.0.X版本中，主题和皮肤的开发是提升用户体验和个性化设计的关键要素。本文档由Ryan Wilson（WebSphere Portal Level 2 Support）和Jim Barnes（WebSphere Portal Level 2 API Team Lead）共同撰写，旨在为WebSphere Portal开发者提供深入理解，介绍6.0.X版本新特性，如主题扩展和主题策略，以及如何利用这些功能来定制界面的外观和感觉。首先，主题和皮肤是决定门户用户界面外观的核心组件。6.0.X版本引入了全新的设计元素和布局选项，使得开发者能够创建更具吸引力和交互性的用户体验。这些新的功能允许设计师通过扩展主题来实现自定义功能，比如添加动态元素或响应式设计，以适应不同设备和屏幕尺寸。为了实现这些功能，开发者需要掌握一些基础技术。熟悉Java Server Pages (JSP) 和 servlet 开发实践至关重要，因为它们是构建Web应用的基础。此外，了解WebSphere Portal的XML访问概念，包括如何使用XML配置文件来管理主题和皮肤，也是不可或缺的。掌握WebSphere Application Server的管理技巧有助于确保主题和皮肤在服务器端的正确部署和优化。 HTML和Cascading Style Sheets (CSS) 的运用在主题和皮肤开发中尤为重要。WebSphere Portal将设计返回到浏览器时，以HTML格式呈现，而CSS则负责定义页面的样式和布局。开发者需要熟练运用这两种技术来控制网页的视觉效果，如颜色、字体、间距等，以实现一致且美观的界面。本文档的结构清晰，包括目录，详细介绍了各个部分，如主题和皮肤的构成、文件组织、CSS类和ID的使用、以及如何通过主题策略来统一管理多个皮肤。对于希望进一步提升WebSphere Portal设计能力的开发者来说，这是一份非常有价值的参考资料，它不仅提供了技术指导，还涵盖了最佳实践和设计理念。通过学习和发展IBM WebSphere Portal 6.0.X的主题和皮肤，开发者可以增强门户的个性化和功能性，提升用户的满意度和工作效率。无论是新手还是经验丰富的开发者，都能从中获益良多，为他们的项目增添更多的创新和专业性。

<portal-navigation:navigationUrl type="link|expand|collapse|launch"

varname="node_name" var="variable_name"/> This tag is always used within the navigation

loop tags to render links to various navigation nodes. Link and Launch are very similar; the other

two are used when that page has a child node and you want to expand the list to see the child

nodes. To create the link, you add code such as <a href="<portal-navigation:navigationUrl

type='link' />"><portal-fmt:title/></a>

<portal-navigation:url> This tag lets you create links to the screens, commands, or home

attributes from within your theme.

<portal-navigation:urlGeneration> This tag lets you create links directly to various portal

resources, either pages or portlets, and is very similar to the URLs you can create via the URL

generation API. The WebSphere Portal information center and various technotes go into further

detail in creating these links.

<portal-navigation:urlParam name="parameter_name" value="parameter_value"> With

this tag, you can add various parameters to the URL. If you have targeted a portlet, the

parameters can then be retrieved by the getParameter method of the portlet request for a

standard portlet. If the URL tag that is the holder for this parameter tag targets just a page, the

parameters are available to all portlets written to the IBM Portlet API on the page, but they will

not be available to JSR 168-Compliant portlets.

2.6.2 Format tags

<portal-fmt:title varname="scripting_variable"/> When used inside a navigation loop tag,

this tag pulls the page’s title based on the locale, while allowing you to pull the title for any item

that supports the localized interface.

<portal-fmt:description varname="scripting_variable" /> This tag pulls the description for

the object that supports the localized interface.

<portal-fmt:text key="key" bundle="bundle"> This tag returns the given text in the specified

language. Java Standard Tag Library (JSTL) should be used instead of these tags, where

applicable.

<portal-fmt:textParam> This tag can be used only within the text tag. If the key in the bundle

file has a place holder in the format of {0}, then this tag can be used to substitute a value for the

place holders. For example, the file nls.engine contains

welcome = Welcome {0}!

Then, in the JSP file, you can put this snippet:

<portal-fmt:text key="welcome" bundle="nls.engine">

<portal-fmt:textParam>World</portal:textParam>

</portal-fmt:text>

The value for {0} will be replaced with World.

<portal-fmt:user attribute="value"/> This tag returns any attribute as defined in IBM

WebSphere Member Manager (WMM) for the current user.

2.6.3 Logic tags

<portal-logic:if attribute="value"> This tag checks a variety of conditions that might exist,

including loggedIn, nodeInSelectionPath, portletMaximized, and portletState. You can use this

tag to change various aspects of the theme to be conditional.

<portal-logic:pageMetaData/> This tag accesses the metadata for the page.

<portal-logic:unless> This tag is the opposite of the <portal-logic:if attribute="value"> tag

above but works on the same conditional states as that tag; that is, if the condition is true, the

ontent of the tag is not written to the HTML output and instead the content is rendered.

<portal-logic:urlFindInSkin file="file_name"> and <portal-logic:urlFindInTheme

file="file_name"> These tags let you build URLs that point to the files as they exist in either the

theme or skin without having to hard-code the URL. You can have the URL for all your images

use this tag and place the images in your theme directory, after which WebSphere Portal will

find them and generate the correct URL.

Using this tag lets the portal engine determine the correct URL path for the image and write that

to the HTML output. An example is

<portal-logic:urlFindInTheme file="images/toolBar/help.gif"/>

where the .gif file exists at the following location on the file system:

wps.ear\wps.war\themes\html\IBM\images\toolBar

2.6.4 Other items affecting theme rendering

When using the default theme as the basis for your new custom theme or when developing your

own theme, using the guidelines found in the information center, you must be mindful of the

theme policy. The theme policy affects how parts of the WebSphere Portal-provided tags

render. Theme policies can cause these tags to change and can leave you with a theme other

than the default theme. For example, some of the theme policies instruct the theme not to

render the theme extensions, so the theme extension tags do not render any output when

called.

Another item affecting rendering is the color palette. You can select various color palettes based

on several factors to change what color scheme the theme uses. For example, you can use the

same theme but a different palette to deploy across different business units.

Finally, you can extend your theme by using the theme extensions framework. These items are

examined in detail later in this document.

Special Notes:

• When you want to modify the look and feel of palettes, be aware that these are separate

portal pages, and they have their own assigned themes. If you want to modify properties

such as the colors and images, you must make sure to edit the correct theme. The

pages on which the palettes are use the IBM theme by default.

• To change the icon for the portlet, you must define the name of the .gif file in the

configuration parameters for the portlet. The parameter name is "portlet_Icon_name",

and the value can be just the name of the file, "my_weather.gif". Check the "My

Weather" portlet as a guide, if you still have it installed.

• The image file must be located in the <theme>/images/palette/portlets directory. After

making the change in the configuration of the portlet, you may need to log out and open

a new browser before you see the new image.

3 Theme policy

The theme policy is a new concept that was introduced with version 6.0 of WebSphere Portal.

This policy controls how various parts of the theme are displayed on the page. Using various

theme policies, you can have one theme but have several looks to your portal.

The only way to update a given theme policy is through the XML configuration interface. You

can apply this policy by using either the properties portlet or the XML configuration tool. As with

many other aspects of themes, you need only set a theme policy on a page if it needs to be

different than the parent policy. Once this setting is set on a page, it is handled through the

process of inheritance, cascading down through any children pages, until it gets to a page with

an explicit definition.

The theme policy contains several attributes, each one controlling a single aspect of the page.

For example, the Boolean renderBreadCrumb attribute controls whether the breadcrumb

displays, and the breadCrumbMaxLevels attribute controls the number of steps listed in the

breadcrumb trail when it displays.

The theme policy can control whether any theme extensions are run and rendered into your

theme. Be mindful of this control when setting the renderExtensions attribute to false, as it can

cause all the theme extensions to fail.

Table 1 lists all possible theme policy attributes and their type.

Table 1. Theme policy attributes

Attribute Type Function

renderMainMenu Boolean If true, the main menu is rendered.

renderTopNavigation Boolean If true, top navigation is rendered.

renderMainMenuActions Boolean If true, the main menu actions are rendered.

renderSelfCare Boolean If true, Selfcare is rendered.

renderBreadCrumbTrail Boolean If true, the breadcrumb trail is rendered.

render renderSearch Boolean If true, search is rendered.

renderToolBar Boolean If true, the toolbar is rendered.

renderContentPalette Boolean If true, the portlet palette is rendered.

renderPeoplePalette Boolean If true, the people palette is rendered.

renderContextMenus Boolean If true, context menus are render.

renderSideNavigation Boolean If true, side navigation is rendered.

renderTaskBar Boolean If true, the task bar is rendered.

剩余52页未读，继续阅读

sunxingtao

粉丝: 11
资源: 35

IBM WebSphere Portal 6.0.X：主题与皮肤开发详解

IBM Websphere Portal主题与皮肤开发详解

IBM WebSphere Portal v5.1 指南：构建企业级入口

IBM WebSphere Portal8主题定制实战指南

Liferay Developer's Guide ６．０．X版本

Csharp.6.0.and.the.NET.4.6.Framework.7th.Edition.1484213335.epub

ZipGenius Suite v6.0.3.1140

DotNetBar6.0.0.5示例

Next Suite VCL v.6.0.60 D6-XE10.2

IBM WebSphere Portal

IBM WebSphere Portal主题与皮肤开发教程

最新资源

Liferay Developer's Guide　６．０．X版本