|
|
|
|
|
|
|
|
|
|
- Overview
- Control in a dynamic page
- Creating an internal page and associating it with a control
- Create an internal page
- Creating an "Internal page" control
- Remarks
- Differences between an Internal Page control and a page template
- Limitations
- Refactoring
- Creating an internal page from a page (and conversely)
The Internal Page control
Control in a dynamic page The "Internal Page" control is used to include a page (and its code) in a control of another page. At runtime, the page to merge ("Internal Page") will be dynamically merged with the host page. The "Internal page" control enables you to dynamically share the same section of the interface in one or more sites. The page to merge (internal page) can also come from a component. Caution: Do not confuse "Internal Page control" and "Internal page": the "Internal page" control is a type of control while the "Internal page" is a type of page. Creating an internal page and associating it with a control Create an internal page To create an internal page: - Click
 in the quick access buttons. The new element window appears: click "Page" then "Page". The page creation wizard starts. - Click "Internal Page" and select "Blank".
- Validate to create the internal page.
An internal page corresponds to a specific type of page. The internal page contains no border, no title bar and no background image. It is intended to be displayed in an "Internal page" control. This type of page is also called "Source page". Creating an "Internal page" control To create an "Internal page" control: - On the "Creation" tab, in the "Containers" group, click "Internal page".
- In the target page, click at the desired location to create the control. The control appears in the editor.
To view the characteristics of the control, select "Description" in the context menu. This allows you to select the internal page that will be displayed in the "Internal Page" control when initializing the target page. Differences between an Internal Page control and a page template - Using an "Internal page" control is recommended for teamwork. Modifying an internal page does not cause all the pages that use it to refresh (unlike templates).
- Using an "Internal page" control is recommended if the controls to display in the target page must be grouped. The templates are used to define the page outline. With the templates, the controls found in the template can be used anywhere in the page.
Limitations - No internal page coming from a component can be used in a static page. Only the internal pages of the project are allowed.
 The same internal page cannot be used twice in the same page.
Refactoring WEBDEV allows you to automatically create an internal page and an Internal Page control from a selection of controls. - Select the controls that must be used in the internal page.
- On the "Modification" tab, in the "Transformations" group, expand "Refactoring and swapping" and select "Create an internal page from the selection".
Creating an internal page from a page (and conversely) WEBDEV allows you to create an internal page from a page (and conversely). To create an internal page from the current page, go to the "Home" tab, "General" group, expand "Save" and select "Save page as an internal page". To create a page from the current internal page, go to the "Home" tab, "General" group, expand "Save" and select "Save internal page as a page". |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|