|
|
|
|
|
|
|
|
|
|
- Transforming a page in Session mode into an Active WEBDEV Page
- Programming tips
- Pro tip
- Limitations regarding the content and the programming of Active WEBDEV Pages
- Displaying an Active WEBDEV Page
- Installing the Active WEBDEV Pages on a server
Creating and distributing Active WEBDEV Pages
Transforming a page in Session mode into an Active WEBDEV Page To transform a page in Session mode into an Active WEBDEV Page: - Open the description of the current page ("Description" in the page context menu).
- On the "General" tab, in "Type of page", select "AWP".
- Validate.
Where will the Active WEBDEV Page be saved?Once a dynamic page has been transformed into an Active WEBDEV Page, the page will be generated in AWP format in the <Project Name>_WEB directory of the project (in each subdirectory corresponding to the languages supported by the project). - The server code must be found in the initialization events (initialization of page or controls).
- The contexts must be managed programmatically. The page must be positioned in the database (according to the parameters received in the URL for example). For more details, see Displaying an Active WEBDEV Page from another page.
- Updating an AWP page: Updating an AWP page triggers all WLanguage events present in the page.. For example, if the Active WEBDEV Page allowed for an addition, refreshing the page will make that addition again.
- WLanguage Events: The order of execution of WLanguage events when a Button field is clicked, for example, is as follows:
- "Initialization" event of the project,
- "Global declarations" event of the page,
- "Initialization" event of the controls in the page,
- "Initialization" event of the page,
- "Click" event of the clicked Button control
Whenever an action is performed in the Active WEBDEV Page, the corresponding HTML page is entirely rebuilt on the server.
- Links: Links can be built programmatically (URL property used on Link fields).
- Links and buttons: Links and buttons without "submit" are preferable. A "<a href>" link is generated in the page.
Limitations regarding the content and the programming of Active WEBDEV Pages - First page of a project: An AWP page cannot be the first page of a project in Session mode.. An Active WEBDEV Page can be the home page of a project.
- WLanguage trace functions: Only output to a file (constant trFile) is available.
- Dialog boxes Dialog boxes displayed by the functions Confirm, Error, Info are not taken into account if a page is displayed in the same processing with the function PageDisplay.
- Global elements used in the project When modifying a global element in the project (global procedure, query, class, etc.), it is necessary to recompile the project to take these modifications into account in the stand-alone AWP pages concerned.
- Rulers RAD-generated rulers cannot be used in AWP pages. Indeed, these controls use the project context (that does not exist in the Active WEBDEV Pages). These controls must be replaced with a programmed pager. Each link of the pager must display a page with specific data (page based on a query with parameters for instance).
All the records can also be displayed in a cell with scrollbar.
The pager in AWP mode automatically manages the method for passing parameters, without programming. This type of pager allows you to reference all the linked pages and it avoids having to use cookies to store the current search. - Table control Table fields are restricted (for example, file tables with link control columns no longer work). They can be replaced with a looper (since links are built dynamically with the URL property).
- Image field: An AWP page cannot use generated images.
- Element in memory (list box, combo box, looper): The content of these elements is volatile. The content of these elements should be systematically filled in the initialization code of the page.
- The value of the read-only controls is lost and it must be recalculated whenever the page is displayed.
- AWP page size: In large projects (with many classes, global procedures or queries), the AWP pages generated will be relatively large.
- Global server variables Project server global variables revert to their default values each time the page is accessed in the case of stand-alone AWP pages. However, you can use DeclareAWPContext or hidden controls associated with the desired value.
- WINDEV or WEBDEV components: components manipulated by an AWP page are not found. They must be moved to the <ProjectName>_WEB directory.
- Data file localization: Data files must be localized in the project initialization code, for example with the code line:
HSubstDir("?", fDataDir())
- relative URL: Relative URLs programmatically built into the project home page must not be used.
Displaying an Active WEBDEV Page An Active WEBDEV Page can be displayed from a static page or from a dynamic page of a WEBDEV website. An Active WEBDEV Page can be displayed: - or via the WEBDEV interface: simply select the AWP page to be displayed when describing the link.
- through programming.
Installing the Active WEBDEV Pages on a server To install Active WEBDEV Pages on a server, you can: - use the standard setup of a site in Session mode. AWP files are classified in the "Static HTML files" category.
- use WDDeploy or any other FTP client to install the file directly on the desired site.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|