IBM®
Skip to main content
    Country/region [select]      Terms of use
 
 
    
     Home      Products      Services & solutions      Support & downloads      My account     
 
developerworks > Dashboard > IBM Lotus Domino Web Application Development > ... > Domino design elements > A design elements overview
developerWorks
Log In   View a printable version of the current page.
Overview Spaces Forums Blogs Podcasts Wikis Exchange
A design elements overview
Added by brunogrange, last edited by jservais on Apr 01, 2008  (view change)
Labels: 
(None)

 This is a community wiki. Be sure you are logged in to edit, comment, and add pages. Not a member yet? It's free and simple. Click Login in the upper right corner and Register.
View a PDF of the original wiki content produced in March 2008 by Lotus and IBM Redbooks.
Table of contents | Previous | Next

The Domino application design is composed of several different types of design elements, each one with a different function over an application. In this section, we discuss the  design elements that are available on the Web with Domino Designer Release 8.


Frameset

A frameset is an element that displays a set of frames that enables designers to improve the usage of the users' screen. A frame is a small portion of a frameset that is used to display a design component in a specific space of the application screen. By using framesets, designers can create relationships between frames, combining navigation, linking and data display on a same screen. The frameset design element allows designers with no experience on HTML to create Web site framesets in an intuitive tool. For more information, refer to Frameset design elements.

Pages

Pages are the best design available in Domino Designer to display information for the user. With pages, designers can store rich text data, including images and formatted text, and some programmatic components, including buttons and actions. In a Web environment, programmers can take advantage of the available rich text converter, which translates the Notes design entered on a body into HTML. For more information, refer to Page design elements.

Forms

Just like pages, forms enable designers to display information on a page. Everything that can be done with a page can be done with a form. Between forms and pages, forms allow the collection of data of the unique information from the user. To achieve data storage, forms offers a variety of fields of different data types, each of them representing a column in the Lotus Notes database model. When working on the Web, Lotus Domino creates the proper HTML tags for fields and forms on its pages automatically, enabling programmers to code applications much faster. Using forms also enables running several event driven computations. For more information, refer to Form design elements.

Views

Views are the most used way to allow users to navigate into applications' data collected on forms. They are basically used to display a selection of documents from a Lotus Notes database. Views can be sorted, customized and searched. On the Web, views can be formatted in template forms to allow user interaction, search and navigation over the database records. For more information, refer to View design elements.

Folders

Folders are containers that store documents. From the design point of view, folders are similar to views. The main difference between views and folders is that views have a selection of documents, while a folder remains empty until a set of records is moved to it. Folders can be used to display database data on the Web just like views. For more information, refer to Folder design elements.


Agents

Agents are Lotus Notes programs that can run a variety of computations. They run from several application-based events, from user triggered events to scheduled tasks. Agents can do simple tasks, from moving database data, to running complex computation like running Java programs. Agents can be called on several background tasks on the Web, including on forms events and using Domino URLs with arguments. For more information, refer to Agent design elements.


Web Services

A Web service is a self-contained, self-describing, modular application, based on XML, that can be published to and invoked from the Web. Lotus Domino Web Services are based on the WSDL language and SOAP protocol W3C standards. By using Web Services, programmers can modularize enterprise services in a standardized programming model, reducing application maintenance effort and improving reuse.

On Lotus Domino release 8, programmers can also create Web Services consumers to use available Web Services implementations from the Lotus Domino Designer IDE. For more information, refer to Web service design elements.


Outlines

Outlines are simpler to implement navigation on a Lotus Notes application. By using an outline, designers can allow user to access key functionalities from their applications on an intuitive navigation model. Outlines can have diverse entries and can be embedded in pages and forms. Outlines can be also placed in framesets, improving the usage of an application screen. On the Web, outlines help programmers promote navigation and action invoking without needing HTML experience. For more information, refer to [outlines].

Shared resources

You can designate many items, such as graphics, fields, subforms, and even programs, as shared resources. Shared resources allow simple access to a set of code used  repeatedly over an application, enabling reuse and reducing the application maintenance effort. In the following sections, we discuss the shared resources that are available on a notes application.

Image resources

Image resources are graphic files that can be used across a Lotus Domino application. The use of image resources helps application standardization and reduces the database file size by preventing the usage of repeated images files across an application. Image resources can be invoked on the Web by using embedding through Domino URLs. For more information, refer to Image resource design elements.

Shared fields

Shared fields have their properties defined in an unique field design, and reused across the database in any form or subform. The use of shared fields helps to reduce the effort on application maintenance. Shared fields can be used in conjunction with a variety of reserved fields on the Web to help Web-pages programming and look and feel, including <head> tags definition and current session information through CGI variables. For more information, refer to Shared field design elements.

Non-NSF file resources

Non-NSF file resources allow programmers to host non-Notes binary files in an NSF database for any kind of usage. These resources are also available on the Web through Domino URLs, by allowing programmers to host Web components, such as animations and plug-ins on a central repository, just like a common Web server file system. For more information, refer to [Non-NSF file resources].

Subforms

A subform is a collection of designs, such as fields, graphics, buttons, and actions that a designer may reuse in more than one form. They can be invoked programmatically depending on a document or environment property. Subforms can be used on the Web to hold different sections of a page, just like other server-side scripting languages like PHP or Microsoft ASP includes. For more information, refer to Subforms design elements.

Script libraries

A script library is a repository to store code that can be shared in an application by using LotusScript, JavaScript, and Java or in other applications using JavaScript and Java. Script libraries allow centralization and reuse. On Web applications, JavaScript libraries can also be accessed through Domino URLs, simplifying the access for cross-organizational routines. For more information, refer to JavaScript library design elements and LotusScript library design elements.

Shared Java files

For big Java applets using various files, it is most efficient to store some of the related files as shared resources in the database. When setting up files as shared resources, all the applets can use a single copy of a file, instead of each applet storing its own copy. Therefore, in case of an update, only one file is updated. For more information, refer to Applet design elements.

Shared actions

Shared actions can be used on forms, subforms, pages, and folders of views that have common user activated tasks. On the Web, shared actions can be displayed using HTML or Java applets. For more information, refer to [shared actions].

Cascading style sheets

Cascading style sheets (CSS) can be hosted on a Domino environment for Web pages design information. For more information, refer to Styles and CSS primer.


Composite application components

Composite applications are aggregations of multiple components brought together for a business purpose. Composite applications can be used on a Domino Web application to bring "portalization", and enabling the use of "portlet" like components. For more information, refer to [composite application components].


Navigators

Navigators are graphical components that help users navigate through specific parts of an application. Navigators are not a recommended design element for Web applications, since they were surpassed by other components that bring better and more efficient results. For more information, refer to [navigators].


Additional topics in this section

Docs Adding HTML to a design (IBM Lotus Domino Web Application Development)
Docs All Domino URLs (IBM Lotus Domino Web Application Development)
Docs CGI variables (IBM Lotus Domino Web Application Development)
Docs Changing the content type of a design element (IBM Lotus Domino Web Application Development)
Docs Common design properties on Web applications (IBM Lotus Domino Web Application Development)
Docs Styling text for the Web (IBM Lotus Domino Web Application Development)
Docs Working with the DOCTYPE (IBM Lotus Domino Web Application Development)


    About IBM Privacy Contact