A page is similar to a form, but unlike forms, pages only display information; forms both collect and display information. Pages can contain text, computed text, and embedded Domino objects such as views, outlines, navigators, folder panes, and a date picker. Pages can also include graphics, image maps, HTML, horizontal rules, tables, sections, links, actions, and applets. However, you cannot place fields on a page.
Using HTML to Create Input Forms
Despite the fact that you cannot place a field directly on the page as a design object, you can actually use a page to create an HTML Input form that can include fields. You simply have to code the page by hand using HTML that creates a form with FORM METHOD=post and fields with the INPUT tag. Be sure to set the page property Web Access, Treat Page Contents as HTML. If you use the Domino URL http://host/database/form?CreateDocument in the HTML, you can actually create and save a document.
As mentioned in the chapter introduction, pages have their origins in HTML, and they help bridge the gap between HTML and Domino. Pages are also meant to replace special forms such as $$ViewTemplate used in R4. x to display views and folder panes to Web clients . Embedding elements such as view applets and outlines on a page replaces the functionality of $$ViewTemplate forms and is more flexible. In addition, pages can be viewed in both Notes and Web clients with reasonably consistent display and function from one client to the next .
Pages combine the best elements of Web and Notes development without the hassle of HTML coding. For example, to add a clickable graphic image with HTML, you have to enter HTML code specifying the reference, URL, and alternative text for a graphic image. In the Page Designer, you simply import or paste the image onto the page and use the properties box to set the URL, text wrap, and alternative text for the image. You'll see how that works later in this chapter. For now, envision having to write the following HTML to produce a single image in a Web banner:
] [<a href="/home.nsf/webOpenMail?OpenAgent&Login"> $FILE/mail9.gif" alt="Web Mail" border=0></a>]
This kind of coding, common in R4. x, displays a mailbox GIF (mail9.gif) in the banner (or header) frame of a frameset that, when clicked, requests the user to log in and runs an agent that then opens the user 's mailbox. The first line ensures that the mail opens in its own window instead of in a frame contained within this frameset. The second line opens (runs) the agent ( ?OpenAgent ) and forces the user to login with the &Login argument. Next, the image file is referenced (it's stored in a view called Files), and alternative text of "Web Mail" is set.
In Notes and Domino 6, you can embed the image from an image resource (you can also import or paste an image) and set a few properties. Remember that Domino generates the HTML on the fly for you, so you don't have to write the actual HTML code.
Part I. Introduction to Release 6
Whats New in Release 6?
The Release 6 Object Store
The Integrated Development Environment
Part II. Foundations of Application Design
Advanced Form Design
Using Shared Resources in Domino Applications
Using the Page Designer
Adding Framesets to Domino Applications
Automating Your Application with Agents
Part III. Programming Domino Applications
Using the Formula Language
Real-World Examples Using the Formula Language
Writing LotusScript for Domino Applications
Real-World LotusScript Examples
Writing Java for Domino Applications
Real-World Java Examples
Enhancing Domino Applications for the Web
Part IV. Advanced Design Topics
Accessing Data with XML
Accessing Data with DECS and DCRs
Security and Domino Applications
Creating Workflow Applications
Analyzing Domino Applications
Part V. Appendices
Appendix A. HTML Reference
Appendix B. Domino URL Reference