This document describes the properties of a page. If you want to see what pages are for and what kind of widgets can be placed on them, please read the Pages overview documentation.
The name of the page. You can change the name via the project explorer.
This property can be used to store developer documentation. End-users will never see this documentation.
The class property allows you to specify a cascading style sheet (CSS) class for the page.
The style property allows you to specify custom cascading style sheet (CSS) rules for this page. In general, it’s preferable to use a CSS class instead.
The canvas width property defines the width in pixels of the page in the page editor. It is purely used for editing purposes; this property has no effect on the actual application.
Default value: 800
The canvas height property defines the preferred minimum height in pixels of the page in the page editor. It is purely used for editing purposes; this property has no effect on the actual application.
Default value: 600
The title of the page that is shown using the page title widget. If the page is shown in a pop-up the title appears in the title bar of the pop-up. The title can be overridden from places where forms are opened to make it possible to reuse a page for different purposes. For example, a Grid New Button and an Edit button can refer to the same page but override the title to ‘New’ and ‘Edit’ respectively.
The layout that this page is based on.
See also Module Security.
Pop-up Size Properties
The pop-up size properties are only relevant if the page is shown as a pop-up, as opposed to in content.
Width (in pixels)
Specifies the pop-up width in pixels. When set to 0, the width is determined automatically.
Default value: 0
Height (in pixels)
Specifies the pop-up height in pixels. When set to 0, the height is determined automatically.
Default value: 0
Specifies whether the pop-up is resizable (Yes) or fixed-size (No).
Default value: Yes
Mark as used
You can search for unused items (Ctrl+Shift+F, Search for = Unused items) in the Modeler. Pages that are only used from Java code will be listed as unused because the Modeler cannot look inside Java source code.
By setting the propery ‘Mark as used’ to ‘Yes’ you specify that the document is used implicitly and the Modeler will no longer list it when searching for unused items.
Default value: No