|
|
|
Controls are visual elements such as edit boxes, buttons, images, and text that allow users to manipulate data on an XPage. |
|
|
|
Add controls to XPages or custom controls, and then set properties for the controls in the Properties view. |
|
|
|
Repeats embedded controls by iterating through a data source. |
|
|
|
Add controls to editable areas in the custom control. You can set properties for these controls in the Properties view, just as you would set properties for any other controls that you add to XPages. You can also change the facet name of controls in editable areas if you are computing the value at ... |
|
|
|
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 ... |
|
|
|
Add user interface (UI) controls to the custom control. Then, you can select each UI control individually and set properties for it just as you would for a UI control inside an XPage. |
|
|
|
Create a new custom control to use in XPages. |
|
|
|
Add the custom control to an XPage. |
|
|
|
Set general properties for custom controls. You can add a description, and set options for displaying the custom control in the Controls palette. |
|
|
|
Set properties for the custom control as it relates to the XPage that contains it. You can set properties for its name and visibility status as well as for any additional properties that you defined when setting properties for the custom control design element. |
|
|
|
Define the editable areas that you want to include in the custom control. Editable areas are regions that users can modify when the custom control is placed on an XPage. All other regions that fall outside of editable areas are read-only and cannot be modified. |
|
|
|
Set properties for editable areas in the custom control. You can set properties for the name of the editable area as well as the facet name. You can also configure how and if the editable area is visible inside the custom control at run time. |
|
|
|
Organize custom controls in the Controls palette. You can put them in categories for easy access. |
|
|
|
Define your own properties for the custom control. You can specify default editors and values to use when setting properties for custom controls inside XPages. You can also write scripts that determine when properties are visible and considered valid inside XPages. |
|
|
|
The Controls palette contains the UI controls and custom controls used for designing the layout of XPages and determining how data will be entered and stored in the database. You can drag and drop controls from the Controls palette onto XPages. |
|
|
|
A custom control is a collection of controls that can be added to multiple XPages. When you update a custom control, every XPage that uses the custom control is automatically updated. |
|
|
|
This article describes how to create a basic user interface control for XPages; this includes creating the Java control, its tag and renderer. In particular, it describes in detail how to implement control properties. |
|
|
|
This article shows you step-by-step how to create a Java control for XPages in an NSF application |
|
|
|
Summary: Currently the IBM® Lotus® Domino® 8.5 XPage upload control allows you to upload a file into an XPage application. In certain cases, however, you may want to limit what types of files a user can upload. This article describes how to configure the upload control for your needs and how to ... |
|
|
|
This video shows the new user interface of IBM Lotus Domino Designer 8.5. To read a text version of this video, scroll to the Procedure section below the video in this wiki article. To watch the video, click the play button. object width"640" height"480" param name"movie" ... |