This guide focuses on the aspects of creating applications using XPages technology.
HCL Domino® Designer provides the means to populate an XPage with controls and other artifacts, and to associate an XPage with data stores.
Controls are visual elements such as edit boxes, buttons, images, and text that allow users to manipulate data on an XPage.
Specified here are the XPages controls.
HCL Domino® Designer supports applications development for the HCL Domino platform using XPages, forms, views, and other elements such as controls.
This section contains tutorials and information about tutorials.
HCL Domino Designer provides features for administering and managing your work and related files while developing your application projects.
XPages run in Domino® server and Notes® client environments. From Domino Designer, you can preview XPages in both environments.
You can add controls and text to an XPage using the Design or Source editor. The Controls palette provides a source for controls.
An extension point is provided to let you override design time tooling for the Core and Extension Library controls that are shipped with Designer.
Properties define XPages and controls.
Events are actions that a user might perform such as clicking a button or removing focus from an edit box. Event handlers are actions that you (the designer) perform in response to events.
A facet defines a region in a control for the placement of other controls.
Dojo widgets are prepackaged JavaScript™ code, HTML, and CSS declarations that enhance the appearance and use of controls in both a browser and the Notes® client.
Inserts a break in text.
Displays a button that the user can click to perform an action.
Provides a custom control with an area that can be edited when embedded in an XPage.
Displays a box that can be selected or cleared.
Displays multiple boxes that can be selected or cleared.
Displays a list of items one of which can be selected.
Contains cells arranged as rows and columns associated with a data source. Each cell can contain other controls (including tables) and text.
Displays a picker for selection of date and time values in an edit box.
Acts as a division or block of content in HTML. Contains other controls and text.
Responds to user actions such as clicking a control.
Downloads a file to the local file system.
Uploads a file from the local file system.
Displays an image.
Inserts a reference to another XPage.
Hides data from the user.
Displays an input field for entering data formatted as rich text.
Displays an input field for entering one line of data.
Displays an input field for entering multiple lines of data.
Displays text.
Opens a URL, a control (anchor link), or another XPage.
Displays a list of items one or more of which can be selected.
Displays error messages for one control.
Displays error messages for all controls on a page.
Pages data for a container control where its data cannot be displayed in one window.
Specifies a pager control within the common pager.
Serves as a container for other controls and text with common data sources and properties.
Combines text in a paragraph format.
Handles a platform event.
Displays a button that can be selected or cleared. When grouped only one button in the group can be selected.
Displays multiple buttons that can be selected or cleared. Only one button in the group can be selected.
Repeats embedded controls by iterating through a data source.
Outputs a client script.
Serves as a collapsible container for other controls and text
Provides an item for user selection, for example, in a check box.
Provides one or more items for user selection, for example, in a check box.
Combines text, typically for the application of properties.
Serves as a collection of containers for other controls and text.
Contains cells arranged as rows and columns. Each cell can contain other controls (including tables) and text.
Displays a value.
Automatically fills in its parent control as users type a succession of characters that match a specified suggestion.
Defines the top-level container control, that is, the XPage itself.
Displays data from documents in rows and columns.
Specified here are the XPages properties.
A custom control is a collection of controls that are stored as a single object. Similar to the way a subform can be placed on more than one form, a custom control can be created once and added to multiple XPages. When you update a custom control, every XPage that uses that custom control automatically gets updated with the changes. This saves you design time because you do not have to update each XPage separately.
The XPages Extension Library provides additional controls ready to use. The controls include an application layout object, an improved dialog, pickers, in place forms, Dojo components, dynamic content, and much more. The controls support enhancements to the Domino(r)® templates.
The data store for XPages is Domino®. You can access the data store through Domino forms and views.
You can enhance your design with images, styles, and themes.
The XPages Extension Library supports Bootstrap, a Responsive Web Design (RWD) framework. This support comes in the form of an XPages Responsive Bootstrap plugin that you can use in your XPages applications.
You can create composite applications from XPages.
XPages uses JavaScript™ for programming while the forms-based design elements use the formula language, LotusScript®, Java™, and JavaScript.