Designing pages
Pages and forms are similar in certain ways. A page is a database design element that displays information. Pages can be used anywhere in your application that you have text, graphics, or an embedded control, such as an outline, to present to the user. A page or form can contain the following:
Elements to use on a page |
Description |
---|---|
Actions |
Actions automate tasks for the user. Add actions to the menu in the Notes® client, or add actions with buttons or hotspots on a page, Xpage or form. For more information, see the topic Actions in the chapter "Adding Automation to Applications."
|
Applets |
Use Java™ applets to include small programs, such as an animated logo or a self-contained application, in a page, Xpage or form. For more information about including Java™ applets, see the chapter "Including Java™ Applets in Applications."
|
Attachments |
Attach files to a page or form so users can detach or launch files locally. |
Computed text |
Use computed text to generate dynamic text based on formula results. |
Embedded elements |
You can embed the following elements in a page, Xpage or form: a view or folder pane, navigator, outline, date picker, or Instant Messaging Contact List. Use these elements alone or combine them to control how users navigate through your application.
|
Graphics |
Place a graphic anywhere on a page, Xpage or form. Use graphics to add color to a page, Xpage or form or to create imagemaps.
|
Horizontal rules |
Add horizontal rules to separate different parts of a page or form, or to make a page or form more interesting visually. |
HTML |
If you have existing HTML or you prefer using HTML to using the formatting tools Domino® Designer offers, you can import, paste, or write your own HTML on a page or form. You can also convert pages and forms to HTML. |
Imagemaps |
An imagemap is a graphic you enhance with programmable hotspots. Hotspots, in the form of pop-up text, actions, links, and formulas, perform an action when clicked by a user. Use imagemaps as navigational structures in an application. |
JavaScript™ libraries |
You can find and insert JavaScript™ libraries into a page, Xpage, form or subform. For more information on inserting JavaScript™ libraries, see the topic "Inserting a JavaScript™ library" in this chapter.
|
Layers |
Layers let you position overlapping blocks of content on a page, form, or subform. Layers give you greater design flexibility because you can control the placement, size, and content of information. For more information on layers, see the topic "Layers" in this chapter. |
Links |
Add links to take users to other pages, views, databases, or URLs when they click on text or a graphic. |
OLE objects and custom controls |
Designer supports objects that are linked and embedded (OLE) as well as custom controls, sometimes called OCX controls. Including a linked or embedded object on a page or form lets you use a page or form as a gateway to another application. For example, an Employee Information page or form can include an OLE object that links to a Word Pro® file where the employee annual performance reviews are stored. Notes/FXTM 2.0 fields create a two-way exchange between Notes® and a supporting application by allowing field data to be shared and updated from either application. For more information on including OLE objects and custom controls on a form, see the chapter "Including OLE Objects in Applications." |
Sections |
A section is a collapsible and expandable area that can include objects, text, and graphics. |
Style Sheet (CSS) shared resources |
You can find and insert a cascading style sheet (CSS) as a shared resource on a page, form, or subform. For more information on style sheets, see the topic "Creating style sheets as shared resources" in this chapter. |
Tables |
Use tables to summarize information, align text and graphics in rows and columns, or position elements on a page, Xpage or form. For more information on creating programmable tables, see the topic "Creating programmable tables" in this chapter.
|
Text |
Use text anywhere on a page, Xpage or form and apply text attributes, such as color, size, and font styles to the text. For complete information on creating and formatting text, see Notes® Client Help.
|
For information on creating and formatting tables, see the topic Creating tables in the Notes® Client Help.
How pages compare to XPages and forms
Pages, XPages and forms all display information to users. Pages and forms can be viewed in the Notes® client or over the Internet, while XPages are viewed only over the Internet. Forms and XPages also let you collect information. Fields, subforms, layout regions, and some embedded controls can be used on forms, but not pages. A page is best suited for displaying information, while a form is more suitable for gathering information.
Using pages in composite applications
Composite applications incorporate a number of different components in the same user experience. If you are creating a page to use as a composite application component, be aware that it may be positioned in different areas of the screen, and combined with multiple other components.
For more information about the elements of composite applications, refer to the IBM® Composite Application wiki at http://www-10.lotus.com/ldd/compappwiki.nsf.