
	Remark	If the UAC is enabled in Windows, a specific window may be displayed. This window indicates that the WD250Admin.exe program will be run on the current computer. Grant the authorization. This program corresponds to the local WEBDEV administrator that is used to run the test of sites developed with WEBDEV. Its features will be presented later in this tutorial.

Open the "PAGE_Registration" page in the editor: double-click its name in the "Project explorer" pane.


	Remark	The "Project explorer" pane allows you to display in the environment a list of all the elements found in the project. These elements are grouped by theme: Pages, Procedures, ... To display the "Project explorer" pane: On the "Home" pane, in the "Environment" group, expand "Panes". In the list of panes that is displayed, select "Project explorer".

This page contains edit controls and a "REGISTER" Button control. The "REGISTER" Button control must do two things:
1. Check that all controls have been filled.
2. Save the values of controls in the database.

Let's see the WLanguage code associated with the Button control:
1. Select the "Register" Button control.
2. Display the popup menu of the control (right click) and select "Code".
3. The code editor is displayed with the different events linked to the Button control. To see all the events associated with the Button control, press the Page Up key.


	Remark	The code editor allows you to write the WLanguage code of your processes. The code editor presents the events associated with each control, which means the events on which a specific process can be run. Remark: Events are displayed in the order in which they will be run. For example, the events associated with the Button control are: Initialization. Browser click. Server click.

Let's study the WLanguage code displayed: the server code and the browser code are identified by different colors:
- The browser code, that will be run on the computer of Web user, is displayed in green.
- The server code, that will be run on the server, is displayed in yellow.

In our example, all input checks are performed in browser code (green code). For example, the EDT_LastName control must not be empty. The corresponding code is as follows:

// Check whether the "EDT_LastName" control is equal to empty string
// (excluding spaces and punctuation)
IF EDT_LastName ~= "" THEN
// The control is empty, display an error message to
 // the user
Error("Type your last name")
// Return in edit into the "EDT_LastName" control (without running
// the rest of code)
ReturnToCapture(EDT_LastName)
END

This check is performed in browser code because there is no need to go back to the server to check that the controls are filled.

This is used to avoid useless round trips and to reduce the wait for the Web user: the navigation is more fluid.

Once the browser code was run, the page sends the values typed to the server. Then, the server runs the server code. In the server code, you have the ability to process the information received.

In our example, the information received is added into the database via the following code:

// Reset the customer structure
HReset(Customer)
 
// Get the values of controls in
// the customer structure
ScreenToFile()
 
// Add the customer into the database
HAdd(Customer)

This operation cannot be performed in browser code because the database is common to all site users and therefore it is located on the server.

Close the code window (click the cross in the top right corner).

Close the page displayed in the editor (click the cross in the top right corner).

Páginas

sábado, 5 de setembro de 2020

DICAS 3069 -WEBDEV TUTORIAL 3-Licao 1.2-14-09-2020 16hrs-Web development and WEBDEV - PARTE B

https://youtu.be/fg9Dv-3rXFk

Nenhum comentário:

Postar um comentário

Teste

Marcadores