Page Builder

 

 

In this topic ...

Quick Tips

Specifying Inputs

 

Related Topics ...

Overview: Creating Pages

HTML Guidelines

Use the Page builder to create a page that contains HTML or JSP code. The page you create can be public and thus accessible to other models, or private and display only within the context of it's containing model.

The Page builder is useful for building simple HTML pages. We can create a page by pasting or entering HTML or JSP code directly into the Page builder. The code you enter must be properly formatted. Use the Page builder to construct simple pages.

 

Quick Tips

  • Creating pages to be inserted into another -- If you intend to insert the page into another, be sure to enclose all text within an <html /> tag, so that those contents are preserved. When you insert one page into another, the <html/>, <body/>, and <form/> tags on the page to be inserted get removed.

  • Create simple UIs with Page builders -- Build up your application's UI by creating simple pages using the Page builder. For complex pages, consider importing one or more pages into the model with  the Imported Page or Imported Directory builder.

 

Specifying Inputs

The Page builder takes the inputs described in the table below. For help on inputs common to many or all builders such as those in the Properties and HTML Attributes input groups, see Using the Builder Call Editor.

Input Name Description
Name Enter a name for this builder call. The designer tool displays this name in the builder call list.
Page Contents (HTML) Enter valid HTML or JSP syntax to create a page (see example). Verify the page contains an HTML tag that wraps the contents of the page, such as <html /> or <body />.

Example:

<html> <head><title>This is a Page</title></head> <body> <p><b>Author Info</b><br /> Author: Jdoe<br /> E-mail: jdoe@company.com<br /> Phone: x1234<br /> </p> <hr /> <p>This is a page that incorporates JSP.<br /> Time is: <%=(new java.util.Date()).toString()%> <br /> Below is a placeholder for a control: <br /> <span name="firstBuilder" /> </p> </body> </html>

Make URLs Absolute Enable to force the conversion of any relative URL on this page to an absolute URL
Public Enable this check box to make the page public. A public page will be accessible to other models and available to be imported.
Overwriting
Rename Existing This input is useful in cases where you want to change the behavior of code that was placed in the WebApp by a high-level builder or by an Imported Model.

For example, you might want to do this if you have a Domino View & Form builder in your model, and you want to use a different class for one of the LJO's that Builder adds to the WebApp. The Domino View and Form Builder does not provide an "LJO Class Name" input. But, we can place a new LJO Builder in the model and give it the same name as that assigned by the Domino View and From Builder, thus replacing the existing LJO and specifying new class.

  • Enable - When checked, this input will cause the Builder to replace an existing WebApp object with a new object. The Builder will locate the existing WebApp object (variable, LJO, etc.), rename it, and then create a replacement object.

Note that This input is available on the following low-level Builders that create WebApp objects: Action List, Imported Page, Linked Java Object, Linked Model, Method, Method Call, Page, Variable and Schema.

Advanced
Fully Parse Page Normally, the factory runtime parses only nodes with a name attribute and certain special nodes, such as form, body, and head. Other nodes are left unparsed. The advantage of partial parsing is that it is more efficient, both in time and memory, and it makes the parser somewhat more tolerant of poorly-formed HTML. Many odd constructions of HTML that are tolerated by browsers but are not, in fact, legal HTML, can be overlooked by the more tolerant parser.

Check this option to have the page fully parsed. This is especially useful to use advanced PageLocations on the page or when using XPath references in your PageLocations.