 |
|
|
|
||
|
||
|
||
| Novell Portal Services Overview and Gadget Development | ||
|
||
| April 2003 | ||
|
||
| DeveloperNet University Course | ||
|
|
||||||
|
||||||
|
||||||
|
Interfacing Content to Gadgets
There are several ways of bringing content into the portal. Some of which include:
- HTML--Any URL generating HTML can be linked into the portal (HTML, ASP, JSP, scripting, etc.).
- XML--Any URL streaming XML data can be formatted with a stylesheet at the portal and included.
- Java--Any backend service that can be accessed via a Java API can be presented in the portal.
More on NPS Gadgets later on in the course.
Page Layout
Page Layout is the basic building block of NPS. Pages may contain gadgets; may be assigned to a user, group, container, or attribute; and also may be inherited by an authenticated user via such assignments.
At this point, a few definitions may be in order.
- Object Schemes-- Gadgets inherited through assignment.
- Themes-- Static portal framework. They provide a common look and feel to the web site.
Every portal has a Default Theme which provides the following services:
- Authentication
- Personalization
- Portal Administration
Figure 9 shows a sample layout, Novell's i-login.
Figure 9: Sample Layout.
Stylesheets
XSL stylesheets, or referred to in NPS as "skins", are used to control the formatting (general look and feel) at both the Theme and Gadget level. If you are creating Gadgets yourself, you must provide a XSL stylesheet (skin). A few links to help you with this are:
Although this course is designed to introduce and discuss NPS, it is not designed to be an XLM, XSLT primer. We will keep this course focused to NPS. This completes the NPS overview section of the course. For additional information about NPS, you may want to look at the following links:
- http://www.novell.com/products/portal
- http://www.novell.com/download/
- http://www.novell.com/documentation/
- http://www.novell.com/coolsolutions/psmag/index.html
- http://developer.novell.com/ndk/npssdk.htm
|
|||||||||||||||
