Concepts - WINDEV et WEBDEV

Concepts

WebDev 10 - Concepts
Version 10 - (1) 06-06
Visit the download center at www.windev.com regularly to check for updates.
Free Technical Support email: freetechnicalsupport@windev.com.
This documentation is not contractually binding. Modifications may have been made to
the software the since this guide was published. Please consult the online help.
All product names or other trademarks mentioned in this publication are registered trademarks of their respective
owners.
© PC SOFT 2006: This publication may not be reproduced in part or in whole in any form without the express permission
of PC SOFT.

3
In what order should the guides be read ?
WebDev 10 is a powerful internet/intranet site development tool with everything you need
to design and create websites.
To learn quickly and efficiently how to use WebDev 10, we advise you to work in the following
order:
1
2
3
Read the "Basic principles".
This guide presents the main concepts needed to create a high-powered WebDev
site.
"Tutorial" (book + exercises).
The tutorial provides a first "hands-on" approach to WebDev, to familiarize yourself
with the main WebDev editors.
Test the examples.
Test the examples delivered with WebDev in the fields you are interested in (e-business,
scheduling, and so on).
The online help lets you find the syntax of a W-Language function quickly, obtain help on
the interface, and so on.
We hope you enjoy getting started with WEBDEV.
WebDev Concepts

4
WebDev Concepts

5
Summary
Part 1 - Internet: Main Concepts 9
What is a site? 11
Static, semi-dynamic and dynamic sites? 12
Types of dynamic sites 13
Types of pages 14
Comparing AWP pages and dynamic WebDev pages 18
Part 2 - Site Development 21
Developing a site with WebDev 23
Terminology: Site and project 24
Hard and software specifications 25
Server configuration 26
Custom-folders: Organize your project 27
Source Code Manager (SCM) 28
Project Monitoring Center 30
Project configuration 31
Multiple generation 32
RAD 33
RID 34
Code types 35
W-Language: straightforward and very powerful 37
Component 38
Part 3 - Displaying information in a page 39
Two site layouts: templates or framesets 41
Templates 42
Frameset: a split HTML page 43
Creating a page in the editor … 44
The following files are automatically created: 45
Choosing a control type for the information to display 46
What type of image to choose: dynamic, static, generated, … ? 48
Creating button effects: custom buttons 50
Repeating a control group 52
Displaying a file in a Table or Looper 53
Positioning controls in a page 54
Overlaying controls 55
CSS stylesheets: to simplify page layout 56
Centered or adapted sites? 57
10 ergonomy tips … 58
Multilingual site 62
Summary

6
Part 4 - Actions on a page 63
Displaying and sequencing pages 65
Preventing a return to a page 71
Choose a type of button / link 72
Button / link code run sequence 73
Uploading a file (image, etc.) to the server 75
WebDev and reports 76
Print Modes 77
Processing several pages in succession 78
Sending emails 79
Saving information on the web user’s computer with cookies 81
Protecting site access: passwords 82
Encrypting information circulating on the Web with SSL 83
Security advantage for dynamic sites: "Back" management 84
Secure payment with provider 87
Part 5 - Database 89
Types of files that can be accessed 91
Linking a control to its item 92
Hyper File Classic 93
Hyper File Client/Server 94
Queries 95
Embedded queries 96
Universal replication 97
3-tier architecture 98
Part 6 - Testing a site 99
Testing a site: elements to test 101
How to test a site? 102
Debugger 104
What the WebDev administrator is for? 105
Summary
Part 7 - Deploying a site 107
Deploying a static or semi-dynamic WebDev site 109
Deploying a dynamic WebDev site 110
Referencing a site 114
Implementing a dynamic WebDev site 115
Dedicated and shared servers? 116
Choice of server? 118
Installing a dynamic WebDev site with a specific configuration 119

7
Part 8 - Maintaining a site 123
Maintaining a dynamic WebDev site 125
Consulting hits statistics for dynamic sites 126
Retrieving data on a site 127
Part 9 - Appendices 131
Main new features in WebDev 10 133
You already know WinDev 135
W-Language functions specific to WebDev 10 136
List of WinDev 10 functions not available in WebDev 138
Summary

8
Summary

PART 1
Internet: Main Concepts

11
What is a site?
An internet/intranet site is a set of HTML pages stored on a Web server. They are set up
for a specific purpose (e.g.: describe a company, sell products, and so on).
A site is designed to be used by web users. They access it via an ordinary web browser.
With WebDev you can easily create internet/intranet sites, which can manage data or not.
Server
HTML page
Web users access the site and
display HTML pages
via a browser
Server at a host’s.
The HTML pages are stored on this server
Part 1: Internet: Main concepts

12
Static, semi-dynamic and dynamic sites?
There are several types of site:
- static sites.
- semi-dynamic sites
- dynamic sites.
The table below describes the differences between them:
Static site Semi-dynamic site Dynamic site
The page contents are set
once for all.
A static site cannot interact
with data.
Static WebDev site: the Web-
Dev engine is not required.
The page contents are built
from data found in the data files,
but they cannot change.
Static WebDev site: the Web-
Dev engine is not required.
Data displayed in the pages
can change.
Usually pages allow you to:
- run processes and/or calculations
by programming.
- display data stored in a database.
- display images and interactive
text.
Dynamic WebDev site: the
WebDev engine is required.
Examples of sites
The table below shows a few examples of static and dynamic sites:
Part 1: Internet: Main concepts
Static sites
- site presenting a company, …
- association site
- personal site
- site of a daily newspaper, …
Note : A dynamic site can include a static section (to present a company for instance).
With WebDev you can create:
- static pages.
- dynamic pages.
- semi-dynamic pages.
Dynamic sites
- product catalog and real-time order management
- travel booking site
- company stock management site (intranet), …

13
Types of dynamic sites
A dynamic site can display pages whose contents change. These contents are usually linked
to a database.
For instance, a dynamic site can manage travel booking in real-time. Bookings are saved
in a data file and can be displayed at any time.
WebDev offers two types of dynamic sites:
- dynamic WebDev site. This type of site requires a WebDev engine on the server. It can
support many databases.
- dynamic PHP site. This type of site requires a PHP engine on the server. It is recommended
for dynamic sites hosted by a public host. It only supports MySQL databases.
Dynamic site
PHP
Dynamic WebDev site
PHP site
Hyper File
ODBC
OLE DB
Native Accesses
Oracle Informix
SQL Server Progress
MySQL Sybase
DB2 Oracle Lite
XML AS/400
...
MySQL
Part 1: Internet: Main concepts

14
Types of pages
WebDev offers different types of pages to use in sites created with WebDev:
- Static pages. This type of page displays unchanging data.
- Semi-dynamic pages. These pages can display data from a database. They are generated
on the development computer along with their contents when the site is created.
Contents do not change once the corresponding HTM pages have been created.
- Dynamic pages. These pages display information from a database dynamically. The
contents vary with the record displayed.
When a dynamic page is displayed, the corresponding context is automatically saved
and updated on the server. The application context mainly has global variables, positioning
variables in data files, and so on.
- Dynamic AWP pages. These pages dynamically display information from a database.
The contents vary with the record displayed.
AWP pages may or may not use the application context. If they don’t use the application
context, they are independent.
- Dynamic PHP pages. These pages dynamically display information from a database.
They can only be used in a PHP site.
Part 1: Internet: Main concepts
The following pages illustrate the different types of pages.

15
Principle of the static page
Development
computer
DEVELOPMENT
Creation of a static page
with WebDev
(".WWH" file)
Server
DEPLOYMENT
HTML page
Web user’s
computer
LOOK-UP
Part 1: Internet: Main concepts
Static page viewed
in the browser

16
Principle of the dynamic page
Development
computer
DEVELOPMENT
Creation of a dynamic page
with WebDev (".WWH" file)
Server
DEPLOYMENT
HTML
page
WebDev
engine
Database
Part 1: Internet: Main concepts
Dynamic page running in the browser.
Data displayed in the pages changes
according to the web user’s action.
LOOK-UP
Web user’s
computer

17
Principle of the semi-dynamic page
DEVELOPMENT
Development
computer
Database
linked to project
Creation of a semi-dynamic
page with WebDev
(".WWH" file)
Generation of
static pages
(".HTM" files)
Server
DEPLOYMENT
HTML
pages
Static page (corresponding to semi-dynamic
pages) running in the browser.
The page displayed corresponds to the
information requested by the web user.
LOOK-UP
Web user’s
computer
Part 1: Internet: Main concepts

18
Comparing AWP pages and dynamic WebDev
pages
Dynamic page
When a dynamic WebDev page is displayed, the following operations are performed:
1. The page is called.
2. WebDev engine runs. This engine will remain on server until the end of application.
3. Application context created. This context will remain on server until the end of the application.
4. The WebDev engine runs the server code and builds the HTML page (from data found
in the database for instance).
5. When the engine has built the HTML page, the server sends the result to the web user
(browser).
Web user’s computer
Call to
display
MyPage1.htm
Call to
display
MyPage2.htm
Part 1: Internet: Main concepts
Server
WebDev
engine runs
MyPage1.htm
displays
Context
created
MyPage1.htm file
created
Context
MyPage2.htm
displays
MyPage2.htm file
created
WebDev engine
stops and the context
closes (end of
application, etc.)

19
AWP Pages
An AWP page is a binary file with the page’s HTML code and the server code (entered in
the code editor by the developer). This file must have an ".awp" extension to be interpreted
by the server.
When a browser (web user) wants to access a dynamic AWP page built with WebDev:
1. The server recognizes the file as AWP.
2. The server calls the WebDev engine to read the AWP file.
3. The WebDev engine runs the server code and builds the HTML page (from data found
in the database for instance).
4. When it has built the HTML page, the engine stops.
5. The server sends the result (HTML page) to the web user (browser).
Web user’s computer
Call to
display
MyPage1.AWP
Call to
display
MyPage2.AWP
Server
MyPage1.htm
displays
WebDev engine
runs
MyPage1.htm file
created
WebDev engine
stops
MyPage2.htm
displays
WebDev engine
runs
MyPage2.htm file
created
WebDev engine
stops
Part 1: Internet: Main concepts

20
Part 1: Internet: Main concepts

PART 2
Site Development

23
Developing a site with WebDev
Requirements
Create the project
Import existing files
Create the analysis
Development
- Project RAD
- Page RAD
- Queries
- Reports
- Source code
GO
Run the site test
Finals tests
Install the site
on a test computer
WDAdmin
Run the site test from
the administrator
WDTEST
SITE
Install the site
on a server
Run site test
Run stress tests
Part 2: Site development
Open the site

24
Terminology: Site and project
A WebDev project is a set of pages, controls, classes, components, and so on, used to
build a site for internet / intranet.
A WebDev analysis contains the description of data files.
A project is usually linked to an analysis.
An analysis can be linked to one or more projects.
Project 2
Classes
Pages and
controls
Style sheet
Analysis
Project 1
Project N
Classes
Style
sheet
Pages and
controls
Classes
Style
sheet
Pages and
controls
Part 2: Site development
To create a site called "whosgotlovelyeyes.com", create a project called "whosgotlovelyeyes".

25
Hard and software specifications
Web user
• a computer: PC, Mac, Unix, WebTV, console, and so on
• a browser: Internet Explorer, Netscape, and so on
• internet (or intranet) access
There are no modules to download. The system works immediately.
Server
Development computer
• 1 server: PC • 1 computer: PC
• 1 server operating system
(Windows or Linux): Windows 2000,
NT server, and so on.
• 1 Web server program : IIS,
Apache, and so on.
• 1 operating system: Windows 2000, NT,
98, 95, and so on.
• 1 Web server program: IIS, Apache, and
so on.
• 1 WebDev application server
(dynamic WebDev sites only)
• 1 WebDev "Development" program
• the site itself • the site currently developed
• the data *
• the data (optional) *
(dynamic site only)
* Data can be located on another computer on the network.
A UNIX or Linux machine can be used as a front-end server.
• at least one browser: Internet Explorer,
Netscape, and so on.
Part 2: Site development

26
Server configuration
For a dynamic WebDev site:
Web user’s
computer
Only a browser
required.
Connection to
WebDev site
Server
Web server (IIS,
Apache, etc.)
WebDev
Engine
WebDev site
Database
For a static or semi-dynamic site:
Part 2: Site development
Web user’s
computer
Only a browser
required.
Connection to
WebDev site
Server
Web server (IIS,
Apache, etc.)
WebDev site

27
Custom-folders: Organize your project
The WebDev project editor can be used to map the entire project.
With large projects, this representation may be difficult to read. You can make it easier
with a "Global View" and "Custom-Folders".
Custom-folders contain the elements you store there, usually a part of your site, such as
customer or supplier management, and so on.
Some elements can be shared among several "custom-folders". This makes it easier to
work on a part of a site.
Global view of project
Custom folder display
Details of a custom-folder
Part 2: Site development

28
Source Code Manager (SCM)
Overview
To make team development easier for you, WebDev now includes a Source Code Manager.
This enables several developers to work together on the same project at the same time.
Part 2: Site development
Elements found in the SCM can be shared:
- via a network
- via the internet
- in off-line mode. In this case, elements requiring specific attention should be checked
out of the SCM, for instance when connecting a laptop to the main system.

29
How Source Code Manager works
Here is an example of how the Source Code Manager works:
If an element (page, report, and so on) is already checked out, it cannot be checked out again.
When the elements have been modified, they must be checked back in to include them in the main
project. Indeed, the SCM database keeps an history of all the project elements since their creation.
Whenever an element is checked in, the main project version number is incremented by 1.
Part 2: Site development

30
Project Monitoring Center
The Project Monitoring Center helps you to organize and schedule a project from end to end. It lets
you know all the tasks to perform in a project, the developers working on it, the time frame required,
its state of progress, and so on.
Part 2: Site development
How Project Monitoring Center works
When the list of all the tasks in a project is complete, the Project Monitoring Center does
the rest. Entering the time spent is almost automatic, requires no specific action and engenders
no particular constraints.
When a project is opened, the Project Monitoring Center asks for or indicates the current
task. As soon as a task is performed, indicate that this task is over and specify the new
task.
A task can be linked to a project element (page, report, and so on). Whenever an element
is opened, the time spent on this element is counted and stored in Monitoring Center. Moreover,
you can go to the task list and automatically open the element related to the task
you want to perform from.
Developers can also view their task list directly in the "Project Monitoring Center" pane.

31
Project configuration
Project configurations enable you to create several different "targets" from the same project.
For example, from the same project, you can create:
- 2 or 3 executables that do not contain the same elements, with different names, and
so on.
- 3 or 4 components
- 2 Web services
- 1 .Net assembly
You can work on a specific configuration at any time: the elements that do not belong to
it are grayed in Project Editor.
WebDev Project
Project Configurations
Configuration 1 Configuration 2 Configuration 3
Site Library Component
...
You can generate all (or specific) project configurations in one go by multiple generation.
Part 2: Site development

32
Multiple generation
Project configurations enable you to easily define the "Targets" for your project. For the
same project, you can define executables, libraries, Web Services, .Net assemblies, and
so on.
To generate the result of each configuration, you can of course select them one by one
and generate the related program.
Another faster way is available: multiple generation. In one operation you select all the
configurations you want to generate, and the result is immediate.
Part 2: Site development
To run a multiple generation, use the "Workshop .. Batch Generation" option.

33
RAD
RAD (Rapid Application Development) can be used to create pages from:
- the analysis linked to the project,
- standard RAD models,
- custom RAD models,
- WebDev templates.
The generated pages contain the requisite code. They can be tested immediately with data
on the development computer.
Analysis
RAD model
RAD Pattern
Template
RAD
Full Application RAD
Page RAD
Example of page generated by RAD
Example of code generated by RAD
Part 2: Site development

34
RID
RID (Rapid graphical Interface Design) can be used to create pages from:
- the analysis linked to the project,
- standard RAD models,
- custom RAD models,
- templates.
The pages generated only contain the controls linked to the analysis items. The developer
must write all the code needed for these pages to work. You can enter your custom code
directly.
Analysis
RAD model
RAD Pattern
Template
RID
Full Application RID
Page RID
Part 2: Site development
Example of page generated by RID
This page does not contain any code.

35
Code types
Server code or browser code?
Two kinds of actions can be programmed in a WebDev site:
Web user’s
computer
1. Actions that can be
performed locally (on
the web user’s computer):
input check, and
so on.
Server
2. Actions requiring a return
to the server (dynamic
pages only):
information read in the
database, programmed
calculations/processes,
and so on.
To manage such actions, the WebDev code editor uses two different types of code:
- Server code (Yellow or Pink in the code editor): This code is written in W-Language (yellow)
or PHP (pink, only available in PHP pages). It is run on the server. This code is
available in dynamic pages only.
- Browser code (Green or Blue): This code is written in W-Language (green) or Javascript
(blue). When the page is saved, the code is automatically translated into Javascript and
included in the WebDev HTML pages. It is run locally (on the web user’s computer) and
requires no server action.
Server code in a PHP page: W-Language or PHP?
Codes run on the server are represented in the code editor by a yellow or pink line.
- Yellow line = W-Language: the code header is preceded by WL.
- Pink line = PHP: the code header is preceded by PHP.
Part 2: Site development

36
To switch from a yellow code (W-Language) to a pink one (Javascript), click the WL beside
the code header (or vice versa for PHP). When a PHP page is saved, the W-Language code
is automatically converted to PHP.
We advise you to develop in W-Language.
Browser code: W-Language or Javascript ?
Codes run on the web user’s computer (browser) are represented in the code editor by a
green or blue line.
- green line = W-Language: the code header is preceded by WL.
- blue line = Javascript: the code header is preceded by JS.
To switch from a green code (W-Language) to a blue one (Javascript), click the WL beside
the code header (or vice versa for JS). When the page is saved, the W-Language code is
automatically converted to Javascript.
Part 2: Site development
We advise you to develop in W-Language.
The icon bar at the bottom of the code window is used to manage events in addition to the
default ones:
Events are added to the codes in Code Editor by clicking the relevant code icon. Additional
events can be: double-click, key down, key pressed, key up, button down, mouse movement,
and so on.
Reminder: Browser code can be used in dynamic, semi-dynamic or static pages.

37
W-Language: straightforward and very
powerful
W-Language is the integrated WebDev language. You can use it to easily program all the
internet processes you need without having to know HTML, Javascript or PHP.
W-Language consists of simple orders, similar to everyday language for intuitive programming
(W-Language is compatible with WinDev, the leading IDE in France).
Here is a little example to show you how powerful W-Language is: checking an address
input:
In W-Language, you only need a few lines …
IF NoSpace(ADDRESS) = "" THEN
Error("Enter your address")
ReturnToEdit(ADDRESS)
END
In Javascript, the process is like this:
function EXE_NoSpace( szString , nPart )
{
var nFirst = 0;
var nLast = szString.length-1;
if (nPart & 1) while (szString.charAt(nFirst)==" ") nFirst++;
if (nPart & 2) while (szString.charAt(nLast)==" ") nLast--;
return szString.substring(nFirst,nLast+1);
}
// Click (onclick) BUTTON_OK
function _VALIDCDE_BUTTON_OK_CLI()
{
if((EXE_NoSpace(ADDRESS,3)==""))
{
alert("Please enter your address ");
return;
}
}
W-Language code is more reliable because it is easier to write, understand and maintain.
It is much more reliable. Upgrading is easier.
Use W-Language for all your processes.
Part 2: Site development

38
Component
A component is a suite of WebDev elements: pages, reports, analysis, and so on which implements
a specific feature. For example, a component can correspond to one of the following
features:
- Send faxes,
- Send emails,
- …
A WebDev component can be distributed to other WebDev developers (free of charge or
not). They can then simply integrate the feature offered by the component into their site.
The component will be included in the site and distributed along with it.
WebDev
project
Component
Development
Generating the component
.WDK file
Part 2: Site development
WebDev
Project
Use of component
Component imported
to WebDev projects
WebDev
Project
Use of component
WebDev
Project
Use of component

PART 3
Displaying information in a page

41
Two site layouts: templates or framesets
When you design a site, you can choose one of the following layout methods:
- site based on "templates": the pages use the same model. They are sequenced and
fully displayed in the browser. The principle of site development is simple: you just
create the template and use it in the pages.
- site based on "framesets": a frameset is use to freeze part of a site (such as the menu).
Pages are sequenced in a frame within the frameset.
These layouts are described in the following pages.
Advantages of templates
Templates help to:
- optimize the speed of page display in a site.
- keep down the number of generated HTML files (and hence the number to load on the
web user’s computer).
- simplify page creation.
- simplify page layout.
- simplify update of the site’s style book.
- simplify management of page destinations.
- and so on.
Part 3: Displaying information in a page

42
Templates
With WebDev, you can create templates. These contain all the graphics used by the site
pages.
Changes to a template are automatically applied to all the pages that use it.
A template ensures you comply with the style book defined for a site.
Part 3: Displaying information in a page
Defining a template.
The template is bordered
in yellow in the editor.
Using a template for several pages.
Elements belonging to the template are identified by a yellow square.
To create a template based on the current page, select the "File .. Save As Template" option.
To create a page based on a template, select the template that will be used when the
page is created.
Note: Elements linked to the template can be programmed in the template itself.

43
Frameset: a split HTML page
A frameset is a specific type of page, divided into several zones called "frames". An HTML
page is displayed in each frame.
A frameset is used to group several pages in a single window in the browser. A typical
example is the site menu in one frame and the site pages in another.
Framesets can be used to easily change the information displayed. The same frame can
display different pages depending on what the web user does.
Page
displayed in a
frame
Frame: where
a page is
displayed
Frameset displayed in the browser
Page of the
site itself
Part 3: Displaying information in a page
Schematic layout of the frameset in 3 separate frames

44
Creating a page in the editor …
To create a page with WebDev, you proceed as follows:
Create a page in the WebDev Page Editor.
Part 3: Displaying information in a page
Enter code lines (optional step).
Save the page.
Browser code
Server code

45
The following files are automatically
created:
Types of page available
AWP
PHP
Dynamic
WebDev page
Semi-dynamic
WebDev
page
Static WebDev
page
AWP Page
PHP Page
Generic
.HTM
WDL
Legend:
Page source file in WebDev format (.WWH)
.HTM .HTM .AWP .PHP
Files generated
.WWH: Page source format
This file contains the full description of the page (control,
browser code and server code). It is used by the editor
and stays on the development computer.
Generic .HTM
This file contains the full description of the page (control,
browser code and server code). Some of the parameters
are generic and will be filled dynamically when
the page is displayed.
.HTM: HTML page of the site
This file contains the control description in HTML and
the browser code (if the code was edited in W-Language,
it is automatically translated into Javascript) and is generated
from the WWH file. It is located on the server.
.WDL: project library
The library contains the server code of the project
pages and is generated when the dynamic site is
deployed. It is located on the server.
.AWP: AWP page
This file contains the description of the controls,
server code and browser code and is generated
from the WWH file. It is located on the server.
.PHP: PHP page
This file contains the control description, server
code and browser code in PHP format and is generated
from the WWH file. It is located on the server.
Part 3: Displaying information in a page

46
Choosing a control type for the information
to display
WebDev provides a wide range of controls:
You want to …
Display text, a title, and so on
Define a colored zone
Display a price, quantity, address, date, time, …
Select a value in a list (Country, City, and so on)
Select several values in a list (message recipients, files to
download, and so on)
Control type to use:
Static, HTML static
Cell, HTML table
Formatted Display Control
Radio button, Combo box, List box
Check box, List box
Part 3: Displaying information in a page
Display a graphic image (photo, and so on)
Display an animated image (animated Gif)
Display a page according to the zone clicked in an image
Display the file content in a table (list of customers, order
details, and so on)
Display a regularly refreshed image
Repeat the controls in a page (product catalog with photo,
and so on)
Use an existing HTML code
Use a Java applet (calendar, clock, and so on)
Enter information
Display ranked information (content of a directory, and so
on)
Display a Flash animation
Align controls (HTML table)
Program an action in a page (display a page, validate an
entry, and so on)
Image, Clickable image
Image
Clickable Image
Browsing or memory table, Browsing
or memory looper
Web Camera control
Looper
HTML control
Java control
Edit Control
TreeView control
Flash Control
Cell, HTML table
Button, Link control

47
You want to …
Display a page from another site in one of your pages
Display a bar chart, line chart or pie chart
Display a page from your site within one of your pages
Display an automatic menu (built as the site is browsed)
Display thumbnail images
Control type to use:
IFrame control
Chart control
Internal Page control
Map Path control
Thumbnail control
Part 3: Displaying information in a page

48
What type of image to choose: dynamic,
static, generated, … ?
Site pages are often illustrated with images.
You can use different types of images with WebDev. Each type is designed for a specific
use.
Part 3: Displaying information in a page
Here is a summary of their characteristics, and how to use them.
Our advice: always use homothetic images when images come from a database.

49
Static
Type of image
Image not changed when the site
is used (company logo for instance).
Image only changed in browser
code (image selected by an
Upload control).
Characteristics
The image linked to a static image must be selected in the
WebDev editor.
This image can be changed by programming in browser code
only.
Image formats recognized by WebDev are authorized.
When the page is saved, the image is automatically converted
to GIF or JPEG format and saved in the _WEB directory
(unless it is already in GIF or JPEG format).
When the WebDev site is deployed:
- the file linked to the image must be found on the server.
- if the image is changed in browser code, the new image
must be accessible and in a format the browser recognizes.
Dynamic
Image modified when the site is
used (product image in a form,
photo in a directory, and so on)
This is the most commonly-used
image.
Generated
Image drawn when the site is
used:
- charts (grXXX functions)
- drawings (dXXX functions)
A background image can be used.
From a database
Products image displayed in a looper
A dynamic image can be changed by programming in server
code or in browser code.
An image linked to a control by programming must be:
- in the _WEB directory.
- in a format recognized by the browser (GIF, JPEG or other).
Note: binary memos cannot be used.
A generated image is built when the dynamic WebDev site is
used.
It is not advisable to use this type of image to display existing
"image" files: your site is likely not to perform as well.
When the browser asks to display the image (e.g. when displaying
or refreshing the page), a temporary image of the current
drawing is made on server and saved in JPG format. This
image is the one displayed in the browser.
These images are saved in binary memos (memo) or text controls
(path).
It is best to use a Homothetically centered image: all the images
displayed are proportionately resized to fit the image control.
Part 3: Displaying information in a page

50
Creating button effects: custom buttons
A new button is gray by default. To customize it, you can use images. Images enable you
to define its shape and color ("Details" tab in the button description).
If only one image is linked to a button, it will be used whatever action the web user performs.
To create special effects, e.g. change color when the mouse cursor crosses the button, you
can link several images to it.
Rollover effect
For a rollover effect alone, link two images to the button: one for its "normal" status and
one for its "rollover" status.
Normal button
"Rollover" button
Part 3: Displaying information in a page
These images are specified in the "Details" tab of the button description window:
Notes:
- The "Catalog" button enables you to choose the two image types from the WebDev image
library.
- Use the option "Border Image/Background Image with 3 images" to easily manage the
width of the button image. When you do so, WebDev automatically divides the button
image into 3 images in order to get the same size of the button.

51
Pressed button effect
To create an effect of pressed button, you can link a specific image to it: this image contains
three drawings. Each one corresponds to a button status: normal, rollover, pressed.
In this case, the button status is managed by a special Java applet provided with WebDev
(just sit back and watch, WebDev does it all for you!)
Image with different button statuses: Normal, Pressed and Rollover
Specify the image file to use in the "Details" tab of the button description window ("Image"
option).
Note: Use the "Catalog" button to choose a 3-status image from the WebDev image library.
Uniform button styles
For your buttons to have the same style, define a specific style and use it for all of them.
Part 3: Displaying information in a page

52
Repeating a control group
Loopers are used to repeat a set of controls "n" times. When they are repeated, the controls
in the looper can display different information. This way, you can display database
records at every repeat.
Creating a looper in the WebDev editor
Part 3: Displaying information in a page
Looper displayed in the browser
A number of characteristics of each looper control can change when it is repeated: caption,
text color, and so on.
You can repeat by:
- column
- several columns. This is called a "Horizontal Looper".
When you create a looper, you can link it directly to a data file or a query. Its attributes are
automatically defined. No programming is required.

53
Displaying a file in a Table
or Looper
You can use a browsing table or browsing looper to display data from a data file. The file
structure is described in the data model editor, and the data could be edited in the site.
The file can be browsed to display data in the table or looper. The file is read for each row
displayed: when it is read, the record is displayed in a table row or in a looper row.
With WebDev, you create a browsing table or looper with the wizard. You choose the items
displayed, the file search key, etc. and the control is created with all the requisite code. A
pager displays automatically, to display the previous or next file records.
You can limit the number of records displayed in the control with a filter (HFilter function
used in the control initialization code).
There are several W-Language functions to handle:
- browsing tables. These functions start with "Table".
- browsing loopers. These functions start with "Looper".
To add a record, add it to the corresponding Hyper File file (HAdd function), then redisplay:
- the table with TableDisplay.
- the looper with LooperDisplay.
To delete a record, delete it from the corresponding Hyper File file (HDelete function), then
redisplay:
- the table with TableDisplay.
- the looper with LooperDisplay.
Part 3: Displaying information in a page

54
Positioning controls in a page
WebDev has two ways to optimize the position of controls in pages:
- positioning tables
- rulers and grid
Positioning tables
Positioning tables are the most common way of aligning controls in an HTML page. They
are also used to create page footers.
Part 3: Displaying information in a page
To view positioning tables, use the "Display .. View Positioning Table" option.
Rulers and grid
Like the snapping grid, alignment rulers are a simple way to align controls in a page.
Rulers can be displayed with the "Display .. Rulers" option.
The grid can be activated with the "Display .. Grid" option.

55
Overlaying controls
For effects of transparency or depth, you can superimpose your controls.
Each control has a "Control can be stacked" option ("Details" tab of the control description
window).
If you check this option, the control is unlinked from the positioning tables. You can move
and reposition it "on top of" another in the page.
Note: you define the control that will be on top, not the one under it.
For instance, to overlay a caption on an image, specify that the caption can be overlayed
and position it on the image.
In the editor
In the browser
Caution: Overlaying requires the web user to have a recent browser (Internet Explorer version
4 or later, Netscape 4.7 or later).
This type of browser is very widespread these days.
Part 3: Displaying information in a page

56
CSS stylesheets: to simplify page layout
Stylesheets are templates to give page controls the same appearance.
Stylesheets are used to define:
- the size and form of your texts, and the font,
- paragraph alignement, indent,
- text style (bold or italic), color,
And much more.
When you change a style characteristic, all the controls linked to the style are refreshed.
So you can change a site’s style book just by a few changes to the styles used.
For example: increasing the size from 9 to 15:
Part 3: Displaying information in a page
Caution: To use stylesheets (CSS), the web user’s browser must be able to support them
(Internet Explorer version 4 or later, Netscape 4.7 or later).
This type of browser is very widespread these days.
Note: you can use the "CSS" tab to edit CSS code directly. The code will be added to the
CSS stylesheet.

57
Centered or adapted sites?
Page layout is a critical element in building a site. To optimize it, you must not forget the
web user’s screen resolution.
For instance, if your site is created for a resolution of 1024 x 768 pixels, web users with a
resolution of 800 x 600 pixels will see a lot of scrollbars.
At the time this guide goes to press, we advise you to develop sites optimized for 800 x
600.
You can use two types of page layouts:
- centered: The pages are in the middle of the browser. If the web user’s resolution is
greater than the site’s optimal resolution, white margins will display on either side of
the page.
Resolution: 800 x 600 Resolution: 1024 x 768:
margins on either side of the page
- adapted: The pages are displayed in the usual way in the browser. If the web user’s
resolution is greater than the site’s optimal resolution, a white margin will display to
the right of the page.
Resolution: 800 x 600
Resolution: 1024 x 768:
the page "hugs" the left-hand side
Note: the type of page layout (centered or adapted) configured in a template will automatically
be used by the pages linked to it.
Part 3: Displaying information in a page

58
10 ergonomy tips …
1 Take care of your front door.
A site runs from a home page. This page is the "front door" to the site.
Take care with the appearance of the home page and simplify site launch: the logo or link
used to enter the site must be visible and easy to identify.
2 Introduce yourself.
When web users come to a site, they must be able to identify the person or company in
charge of it: give a name, a postal address, a web address, and so on.
Part 3: Displaying information in a page
Other helpful information:
- the date the site was onlined or last updated,
- its purpose, content and end,
- the person in charge of administrating the company, its registration number, …

59
3 Are your pages very long? Give the web user ways to go back to the top.
If your pages are very long (more than 2 screens), use buttons or links to go back to the
top quickly (to avoid using the scrollbar).
Top of page
End of page with a link to go back to the top
4 Harmonize the style and alignment of your buttons.
Check whether your buttons have the same appearance and check their alignment.
Non-aligned buttons with
different styles
Aligned buttons that look
alike
5 Avoid useless scrollbars.
To avoid useless scrollbars in frameset pages, select the "Automatic scrollbar" option in
the page description window ("Frame" tab). This will ensure a scrollbar is only displayed
when necessary.
Part 3: Displaying information in a page

60
6 Do you have lists with more than 20 elements to display? Use several pages to list
them (pager control).
Part 3: Displaying information in a page
7 Use 100% images or homothetically centered images
For your images to keep their proportions, choose:
- 100% images (for static or dynamic images or if the image is the same as the control
size).
- or centered homothetic images (for generated images or images of varied sizes from
a database): their size will be homothetically adapted to the zones defined for them
and they will stay in proportion.
100 % image if the
control size is the
same as the image
size, otherwise
Homothetic image
Stretched image
(not recommended)
Display mode
selected in the editor
(image description,
"General" tab)

61
8 Are you using images? Check whether they display properly in your pages.
Image in the editor
Image in the browser.
Display problem
If you have a display problem, check whether:
- the image exists,
- the image is saved in a format recognized by the browser (e.g. GIF or JPG),
- the image is in the _WEB project subdirectory.
9 Does the web user need to enter a quantity? Use a combo box to simplify the edit.
10 Do you offer a product catalog with an ordering option?
Give all the product details (name, reference, price, and so on), and include a button or
link to order it.
Part 3: Displaying information in a page

62
Multilingual site
WebDev makes it easy to create multilingual sites based on the same project.
A page in english …
… the same page in french
Part 3: Displaying information in a page
To create a multilingual site, select the languages supported by the project ("Project .. Project
Description", "Languages" tab).
You can then configure all the project elements in these languages. WebDev enables you
to configure:
- the different elements (captions, page titles, and so on).
- the display characteristics (edit mask and so on).
- the image files for the elements (button, image control, and so on).
All the elements (pages, reports, images, and so on) required are grouped into a single directory
per language.

PART 4
Actions on a page

65
Displaying and sequencing pages
A site is a set of pages linked together by buttons (or links). A click on a button displays a
new page.
To display a new page, there are two questions to ask:
1. where to display it (new browser, frame, and so on)?
2. what page to display?
Where to display a page?
A page is displayed in a specific "target": current page, new browser, and so on.
The target can be defined:
- in the page editor: no programming is required.
- in the code editor, in a button (or link) process.
Selecting a target in the page editor (most common method)
In a button, to define the target of the page to display:
- Display the button or link
description (right-click the
control, "Description" option).
- In the list of targets, select
a preset target or a frame
(for a frameset).
Note: Preset targets are described later in this manual.
Selecting a target in the code editor
When the target depends on a choice made by the web user, it must be selected by programming.
For example, if the web user does not enter a password, an error page displays
in a new browser; otherwise, the next page displays in the current browser.
The W-Language ChangeTarget function is used to change the action target by programming.
This function must be used in a browser code.
Part 4: Actions in a page

66
Choosing a target
When choosing a target for a button, link, clickable image, menu item, and so on, you can
select:
- a preset target: there are four of these:
- Current browser (_top for the initiated)
- Current frame (_self)
- Parent frame (_parent)
- New browser (_blank). You can choose the characteristics of the new browser (with
or without menu bar, status bar, and so on).
- a frame in the current frameset.
Note: in this diagram, the grayed area is where the page is displayed when the button is clicked.
Current browser (_top)
Click on
a button
Initial page
New page displayed in
the entire browser
Part 4: Actions in a page
Current frame (_self)
Initial page
Click on
a button
New page displayed in
the same frame

67
Parent Frame (_parent)
Click on
a button
Initial page
(2 nested framesets)
New page displayed in the
page with the
second frameset
New browser (_blank)
Click on
a button
Initial page
New page displayed in a new
browser window
Window used to define the characteristics
of the new browser
Part 4: Actions in a page

68
What page to display?
The page to display can be defined:
- in the page editor (no programming is required).
- in the code editor, in a button (or link, clickable image and so on) process.
Selecting a page to display in the page editor (most common method)
To define the page to display:
- Display the control description
window (right-click the
control, "Description" option).
- Select the page to display in
the list of actions.
Selecting a page to display by programming
You must select a page to display by programming when:
- several pages can be displayed (e.g. an error page if the password is not entered, or
the next page in the site)
- a specific action must be performed on the server (calculation, reading a record, and
so on).
There are W-Language functions to open a new page (or frameset). The main ones are: PageDisplay
(for pages) and FramesetDisplay (for framesets).
Part 4: Actions in a page

69
Displaying a dynamic page: creating its context
We know that WebDev can be used to create dynamic pages. The dynamic content is defined
dynamically when the page is run (i.e. when the page is displayed in the web user’s
browser).
For each dynamic page displayed in the browser, a "page context" is created on the server.
This context contains the page information (value of current variables, control contents,
and so on).
Web user’s
computer
Server
Page Context
Each dynamic page (displayed on the web user’s computer) is linked to a page context.
If the page can display different data (e.g. product form with browse buttons), the context
is modified and the page is refreshed whenever a new record is displayed.
Part 4: Actions in a page

70
Dynamic page display and update? PageDisplay or PageRefresh?
W-Language has two functions to display a dynamic page: PageDisplay and PageRefresh.
These are used to display or refresh a dynamic page. The concepts are completely different.
Displaying a page = new page
Displaying a dynamic page corresponds to opening a "new page" in the browser. E.g., the
"View_Product" page is opened to view an item selected in a table.
Note: if you "display" a page already opened, the page and its context are closed and reopened.
The page data are reinitialized.
Refreshing a page = redisplaying a page (faster)
Refreshing a dynamic page means you redisplay a page already opened in the browser.
The action is the same as with the "Refresh" button in the browser.
The dynamic page data is updated to match the contexts on the server. Only modified data
are redisplayed.
E.g.: In a business site, the page displaying the list of selected products is refreshed when
a new product is ordered.
Performance advice: To update data displayed in a dynamic page, use "PageRefresh".
With "PageDisplay", the page takes longer to load.
Part 4: Actions in a page

71
Preventing a return to a page
The browser "Back" button enables web users to go back to a page already seen. However,
it is not always a good idea to be able to go back to a page.
For instance, in a business site, if the web user goes back to an order validation page, he
might validate his order twice, and so place 2 orders.
To prevent a return to a page with the browser "Back" button:
1. Display the page in WebDev Page Editor.
2. Select "Display .. Selection Description". The page description window displays.
3. Display the "Details" tab.
4. Check "Prevent return to page with the browser "Back" button".
5. Validate.
Part 4: Actions in a page

72
Choose a type of button
/ link
Depending on the operation to run on the page
controls, there are several types of button / link
available.
The type of button/link is defined in the control
description window ("General" tab).
Here are some examples of typical ways to use buttons / links in a page:
- Send data from the current page to be processed on the
server
Example: Registration form: the link is used to check the validity
of the information entered and to display a confirmation
page. For this sort of process, use a "Send control
values to server". The page data are sent to the server for
processing.
- Perform a process on the server, without retrieving the current
page’s data
Example: Menu page made up of buttons: each button is
used to open a page on the site. For this sort of process, use
a "None" button.
Part 4: Actions in a page
- Perform a process in browser code
Example: Perform a simple calculation
locally, an edit check, and so on.
For this sort of process, use a "None"
button.
- Display a page external to the WebDev site
Example: Run a search engine with a button.
For this sort of process, use a "None" button.
- Reset the page controls
Example: Link used to clear the controls found in the current page.
For this sort of process, use a "Reset page controls" button.

73
Button / link code run sequence
Two click codes are linked to buttons / links:
- browser click code, entered in W-Language (or Javascript) in the code editor. This code
is included in the HTML page and run on the web user’s computer.
- server click code entered in W-Language (only for dynamic pages). It is run on the server.
The table below shows the codes run according to the type of button / link chosen, and
the relevant action.
The button / link appearance and target do not affect the sequence in which the codes
are run.
Browser click
code
Server click
code
Part 4: Actions in a page

74
Operation Sequence of codes run Notes
Submit
Page reset
Action:
None
Run button / link click code
Codes run:
1. Browser control click code.
2. Browser submit page code (if any).
3. Send the values in the page controls to update the
page context on the server.
4. Control server code.
Action: Display page
Codes run:
1. Browser control click code.
2. Browser submit page code (if any).
3. Send the values in the page controls to update the
page context on the server.
4. Control server code.
5. Display page.
Action: None
Codes run:
1. Browser control click code.
2. Display the initial page (reset or clear all page controls
and run the initialization code of each control).
Page context automatically
refreshed on
the server (dynamic
pages only).
Page context automatically
refreshed on
the server (dynamic
pages only).
Page automatically
displayed.
Part 4: Actions in a page
None
Action: None
Codes run:
Browser code only.
Action: Run button / link click code
Codes run:
1. Browser control click code.
2. Control server code.
Action: Display page
Codes run:
1. Browser control click code.
2. Control server code.
3. Display page.
Page automatically
displayed

75
Uploading a file (image, etc.) to the server
Uploading means sending a file from the Web user’s computer to the server.
A simple example: Creating a contact in an address book. The web user wants to link a
photo to the contact form. The photo is on his computer’s hard drive.
The UPLOAD control is used to select the image with the "Browse" button.
When the form is validated, the image file is sent to the server and copied on its hard drive
(UploadCopyFile).
The image is displayed in the contact form.
When the page is validated,
the uploaded file is copied
on the server hard drive.
Web server
In the web user’s browser
Host server
Note: The appearance of the "Browse" button is defined by the browser.
Part 4: Actions in a page

76
WebDev and reports
You can use the report editor for quality printouts.
A report is created as follows:
- data to print comes from a data source (file described in an analysis, Hyper File view,
query, memory zone or text file).
- a report groups, sorts and formats data.
A report can be:
- printed on a server printer (intranet site).
- displayed in the web user’s browser (HTML, PDF, and so on).
- emailed to the web user (PDF).
- …
Development
computer
Server
Part 4: Actions in a page
Report sources
Txt
Table Control
Memory
zone Control
Query
Text File
Data
Report
Printout on
server printer
HTML, XML
files, …
XLS, PDF
files, …
Text Files
XLS PDF
Txt
Browser

77
Print Modes
To print documents generated by your site (invoices, quotes, and so on), create reports
with the report editor.
To print these reports regardless of the configuration of the web user’s computer, we advise
you to offer at least two print modes:
- Printing in HTML format: the report is displayed in a new site page. It can be printed
with the browser "Print" button. No specific software is required.
- Printing in PDF format: this print mode requires Acrobat Reader on the web user’s
computer.The print operation is run from from this program.
Report in WebDev report editor
Printing in HTML
Printing in PDF
Part 4: Actions in a page

78
Processing several pages in succession
In a business site, ordering can be a process involving several pages:
- page 1: Selecting the products to order.
- page 2: Viewing the cart.
- page 3: Validating the order and entering the customer’s details.
Page 1: Selecting products
Page 2: Viewing the cart
Part 4: Actions in a page
Page 3: Entering the customer’s details
In this case, the data must be written to the files in the order validation button code: all
the order elements must be stored until the final validation. Do not write in the files during
processing.
Note: You can also use a transaction, but we advise you to store the order details.

79
Sending emails
Emails are used:
- for web users to communicate with each other: send messages to a site manager,
mailing-list site, and so on.
- to validate an order: a business site sends web users an email to validate their orders.
- to transfer data from one computer to another: new orders entered in a business site
are transferred by email to the company hq, and so on.
WebDev can be used to send emails from a site in 2 different ways.
1 From the web user’s computer
Use this method when an email is sent to a specific address: site author, technical support,
sales department, and so on.
The emailOpenMail browser function is used to open the web user’s messaging system.
Some parameters can be set as default: recipient address, …
Web user 3
Web user n
Web server
Web user 2
Emails between
web users Web user 1
This method uses the web user’s messaging system: there is no specific process in the
WebDev site.
Part 4: Actions in a page

80
2 From the server (dynamic pages only)
In this case, the server manages the emails. Emails can be sent:
- directly from the dynamic WebDev site (e.g., to transfer data by email or to validate
an order by email).
- by the email spooler (supplied with WebDev).
Web user N
Web server
Web user 3
Email server
(WebDev
administrator)
or
Emails sent directly
Web user 2
Part 4: Actions in a page
Web user 1
Use this method for custom email management:
- checking contents of emails sent by web users (e.g., "distribution list" site),
- checking the validity of the recipient address,
- encrypting information sent by email,
- validating a process, …

81
Saving information on the web user’s
computer with cookies
A cookie is a file saved by the WebDev site on the web user’s computer. It can be read at
any time from the server or the browser. Cookies are used to store recurring information
on the Web user’s computer.
For example, when a web user first comes to a site, information is requested (login, password,
and so on) and stored on his computer. At the next logon, the WebDev site reads
the information in the cookie created during the first visit and can greet the web user personally
on the first page.
1st logon
The WebDev site saves the
web user’s information.
A new web user
enters his name and password
Next logons
The WebDev site
reads the data
entered before on the
web user’s computer.
By default, the WebDev site displays the
information read in the cookie
To create cookies in a WebDev site, use the W-Language CookieWrite function.
To read cookies in a WebDev site, use the W-Language CookieRead function.
Part 4: Actions in a page

82
Protecting site access: passwords
Site access by password is required in two cases:
1. Protecting personal details
2. Restricting access to a site
To protect personal details
To access personal details again, the web user must enter a password. In a business site,
the web user defines a password to access details of previous orders.
In this case, site access management requires:
- an ID: At the first logon, the web user gives an identity and a password.
Then, the web user gives his ID and can access the relevant features (and history, and
so on).
- a system to enable a web user to retrieve a forgotten password.
WebDev has all the resources required to manage personal passwords.
Restricting access to a site
By default, a website can be accessed by anyone. But they are not all designed for the general
public: some features may be reserved to certain types of web user (site administrator
for instance).
Part 4: Actions in a page
In this case, the site manager assigns a password to each web user. This password cannot
be changed. It is used to access limited features.
E.g., in a business site:
- each salesperson will have a specific password and can access sales figures.
- each member of the marketing team will have a specific password and can put new
products online.
With WebDev you can handle all types of site access easily.

83
Encrypting information circulating on the
Web with SSL
By default, data exchanged between the user’s computer and the Web server are not protected.
Their confidentiality is not guaranteed.
There are several ways to ensure confidentiality. A common system is the SSL protocol (Secure
Socket Layer).
Implementing transactions secured by the SSL protocol
To set up SSL-secured transactions, you must complete the SSL formalities (purchase of
a certified SSL key from a specialist organisation). For more details, see the online help.
SSL-secured transactions in a WebDev site
Only sensitive data such as credit card numbers should be secured because the secure
mode is slower.
Secure transaction is implemented when a new page is opened with a button (or link). Use
the SSLActive function in a button (or link) browser code. When the secure page is opened,
all actions will be run in secure mode (i.e. encrypted).
Web user’s computer
Operations in secure mode
Server
SSLActive(True)
Click on a
button
Open the
page
Secure
page
SSLActive(False)
Click on a
button
Open the
page
Non-secure
page
To return to non-secured mode, use the SSLActive(False) function in the button (or link)
browser code to open a new page.
Part 4: Actions in a page

84
Security advantage for dynamic sites:
"Back" management
A browser is used to browse site pages with the "Next" ( ) and "Back" ( ) buttons
in its menu.
For each new dynamic page displayed in the browser, a page context is created specifically
to process it on the server.
When a dynamic page is used to display different data (page with file table, loopers or
"Form with browse" page, and so on), the page context on the server varies based on the
data displayed.
When the web user clicks the "Back" button, the browser does not inform the site or the
server. It goes back to the previous page without the corresponding context.
There is nothing specific to manage in a "Back" operation between pages.
Specific management is required when the same dynamic page displays different data.
Why does "Back" need managing? A simple example …
To understand why "Back" needs managing, let’s look at the example of a dynamic page
displaying a list of available DVD-ROM players.
Step 1: Display the list of DVD-ROMs
Part 4: Actions in a page
The context contains the list of elements displayed in this table: DVD-ROM players by
CREATIVE.

85
Step 2: Click the "Next devices" link.
"NEC" devices are displayed. The page context on the server is updated: it contains the list
of elements displayed in this table (DVD-ROM players by NEC).
Step 3: Click the browser "Back" button.
The dynamic page displayed in the browser corresponds to the page displayed in step 1.
But the browser has not informed the server that the web user has clicked BACK.
The page context on the server is still that of the "NEC" records.
If the web user selects an element in the table (DVD-ROM by "CREATIVE"), this will correspond
to the element in the context: a NEC element. The dynamic page displayed and the
page context on the server are desynchronized. The WebDev engine detects the desynchronization.
BACK button management is absolutely necessary.
Part 4: Actions in a page

86
How to manage "Back" operations?
To manage "Back" operations, you can use:
- the synchronization code of the dynamic page. This code is called when desynchronization
occurs.
- an hidden edit control (invisible control) to identify the record displayed in the browser.
- the option "Disable page synchronization for this control" in your buttons and/or links
("Advanced" tab in the button description).
Depending on the type of action that can be performed in a dynamic page, you can choose
and combine one or other of these options.
Detailed example of BACK management
A dynamic page is used to browse products in a site. The page buttons are:
- Back to main menu
This action does not require specific "Back" management. The button does not use
data files: desynchronization of the context and the page displayed has no effect.
- Delete the current product
This action uses a data file. The deleted record must correspond to the record viewed
by the web user. To manage "Back" in this case, use:
- a hidden control in the dynamic page: this control will contain the identifier of the
record actually seen in the browser.
- the synchronization code: this code updates the context (search for the record
viewed by the web user).
Part 4: Actions in a page
The actions performed in the synchronization code are:
1. Rereading the record corresponding to the identifier stored in the hidden control.
2. If the record is not found, an error page is displayed and the "Delete" button code
is not run.
3. If the record is found, the page context is automatically changed on the server
and the "Delete" button code is run.
Complete security!

87
Secure payment with provider
There are several providers of secure payment systems. Payments by credit card are validated
with the card center by the provider.
The payment steps are as follows:
Provider
server
Check
the card
number
Web Server
- WebDev application
server
- WebDev site
Web user’s
computer
1. The customer validates the order.
2. The WebDev site requests debit from the provider.
3. The provider asks for the card number.
4. The customer enters the card number.
5. After check, the provider sends an authorization number.
6. The order is accepted.
Part 4: Actions in a page

88
Part 4: Actions in a page

PART 5
Database

91
Types of files that can be accessed
WinDev, WebDev and WinDev Mobile offer simple access to the most common databases.
Windows
OLE DB
ODBC
Progress
AS/400
Linux
Client /
Server
XML
Mobile
Hyper File
Native
UDC
MySQL
Sybase
Classic
Native Accesses
Informix
Oracle
SQL
Server
DB2
UDC: Universal Data Connector (HReadSeek, HExecuteQuery, File, Item, Automatic file
link, SQLExec, an so on).
Part 5: Database

92
Linking a control to its item
To display information from a database in a page, you have to link the page controls to the
database items.
It is very easy to display and retrieve information:
- You define the link between a control and an item in the Page Editor when you describe
the control ("File" tab).
- The PageToFile function is used to update the record with the data displayed on the
page.
- The FileToPage function is used to update the data displayed on the page with the information
recorded in the file.
PageToFile
FileToPage
Part 5: Database
Database

93
Hyper File Classic
A WebDev Hyper File application can operate in Classic or Client/Server mode.
The characteristics of the Classic mode are:
- A site using Hyper File Classic is run on different browsers. A session is opened for every
site run.
- The data files are located in a directory accessible to WebDev site sessions (on the server
or another computer). Each session physically accesses the data files.
- The processes (query, read/add to file, and so on) are performed by each session.
Part 5: Database

94
Hyper File Client/Server
A WebDev Hyper File application can operate in Classic or Client/Server mode.
The characteristics of Client/Server mode are:
- A Client/Server Hyper File site is run on different user computers. A session is opened
on the WEB server for every site run.
- The data files are located on a server computer (Hyper File Server). Only the server physically
accesses the data files.
- All processes (query, read/add to file, and so on) are performed on the server.
Part 5: Database

95
Queries
A query is used to interrogate a database to view, insert, modify or delete data. The query
structure defines the data used.
A query can interrogate one or more files.
Queries can be created very simply with the query editor, without having to program.
Pages and controls in a
page ("Content" tab)
Query
The query result is used in the same
way as a file
Reports
Programming
(use in W-Language
functions)
Data from one or more files
(Hyper File, Oracle, and so on)
Queries
Part 5: Database

96
Embedded queries
Page controls can be linked to a data file, an existing query, and so on. They can also be
linked to a query created when the control is designed.
Looper linked to an embedded query
Embedded query: MyPage_1$Query
Part 5: Database
In this case, the query is embedded in the page and is in the related WPW file. If the WPW
file is transmitted, the embedded queries used by the page are also supplied.

97
Universal replication
Universal replication is used to update databases in the same or different formats (Hyper
File Classic, Oracle, SQL Server, and so on). You can for instance synchronize a Hyper File
Classic database and an Oracle database.
Universal replication uses a centralized model: all the databases synchronize with a master
database. The master database then propagates the modifications to the other databases.
Synchronization can be adapted to specific cases. For instance, you can retrieve only the
records concerning a specified product or records made on a particular date, manage conflicts,
and so on.
Such adaptations must be programmed by the HRplFilterProcedure function.
Part 5: Database

98
3-tier architecture
3-tier architecture is designed to separate the usual 3 tiers of an application: GUI, processes
and data.
An application will consist of 3 separate tiers:
- a presentation tier,
- a process tier,
- a data access tier.
The reason for separating them is to facilitate maintenance and future upgrades of the
application. This ensures higher security because database access is only authorized via
the process tier. It also helps to optimize teamwork and multi-target development.
Part 5: Database

PART 6
Testing a site

101
Testing a site: elements to test
The test is a crucial part of site development. It shows if the site works properly and is usable.
Here are some of the main points to test in a WebDev site:
- how it operates: page sequencing, how the code runs, and so on.
- its style: use different browsers (mainly Internet Explorer and Netscape Navigator) and
screen resolutions, resize the browser, and so on.
- specific Web features: printing, cookies, browser "Back" button, and so on.
- web user access management: logins and passwords, concurrent access to data files,
and so on.
- regression test when the site is updated: to validate modifications to the site and
check that unchanged features can still be accessed.
- stress test (for a site installed on a server): to validate the maximum number of hits on
the site at the same time.
Part 6: Testing a site

102
How to test a site?
There is a range of tools for testing a WebDev site:
- WebDev main editor.
- WebDev administrator. This module is required to run a dynamic WebDev site. Dynamic
sites can be tested on the development computer via a test page created by the
administrator.
- WDTestSite (stress site).
The table shows you when and how to use these test modes.
Test mode Type of test To run the test
Editor
You can run a test from the editor
to test:
- site features,
- the code used in processes.
There is a powerful debugger to
track every step of process execution.
- the way the site behaves with
different browsers (installed on
the development computer).
"Project .. Test Mode .. Test Project"
or "Project .. Test Mode .. Run
Project Test from the Home Page"
in the editor.
Note:
Web user rights (access, read and
write) are the same as the developer
rights.
WebDev
Administrator:
WD100ADMIN
(dynamic WebDev
site only)
You can run a test from the administrator
to test:
- site features,
- specific Web features (cookies,
and so on).
1. Run the WebDev administrator
("Programs .. WebDev 10 .. Web-
Dev Administrator" in the "Start"
menu).
2. Click "Test Page" ("Configuration"
tab").
Part 6: Testing a site
Note: This test runs the WebDev
site in the same conditions as those
of a web user.
The rights (access, read and write)
of the web user are the same as
the default rights defined in the
web server used.

103
WDTestSite
(dynamic WebDev
site only)
WDTestSite is used to perform
stress tests.
WDTestSite can run several simultaneous
connections to a WebDev
site. Each connection runs a set of
actions in the WebDev site (preset
scenario).
This test must be run on a WebDev
site installed on a deployment computer
that is ready for operation.
1. Create a test scenario (with WD-
TestSite).
2. Install WDTestSite and the scenario
on different computers to simulate
a large number of access
attempts.
3. Specify a number of connections.
4. Run the test scenario on each
computer.
Note:
Each computer runs a defined
number of connections. Each connection
runs a selected scenario.
Part 6: Testing a site

104
Debugger
To develop your code, a debugger is supplied with WebDev.
You can use the debugger to run your dynamic sites step-by-step, and view how the W-Language
code runs, variable contents, and so on.
To run the debugger, use:
- either a breakpoint set in the code editor: the debugger will automatically start when
the line preceding the breakpoint is run.
To set a breakpoint, click in front of the code line: a red bullet displays.
Part 6: Testing a site
- or the W-Language server keyword Stop in your W-Language code: the debugger will
automatically start when this code line is run.
- or the option "Project .. Test Mode.. Trace Project": the debugger starts at the same
time as the dynamic site test.

105
What the WebDev administrator is for?
The WebDev administrator is required to run dynamic WebDev sites.
When you develop a dynamic WebDev site, the administrator is mainly used to:
- test dynamic sites using a test page ("Configuration" tab, "Test Page" button)
- define the connection settings: disconnection time, and so on ("Configuration" tab)
- directly delete current test connections ("Connections" tab)
- change the web server used for your tests ("Configuration" tab, "Server" option)
- perform a diagnostic if a problem occurs when running a dynamic WebDev site ("Configuration"
tab, "Diagnostic" button)
- …
In deployment, the WebDev administrator is used to:
- manage WebDev accounts ("Configuration" tab)
- manage the configuration of the dynamic sites installed on the server: number of connections
authorized, and so on ("Sites" tab)
- customize the error messages of the dynamic sites installed on the server ("Configuration"
tab),
- …
Part 6: Testing a site

106
Part 6: Testing a site

PART 7
Deploying a site

109
Deploying a static or semi-dynamic WebDev
site
Principle
Static or semi-dynamic sites are deployed by FTP:
Development
computer
Host
Creation of setup
version by FTP
(WDDeploy)
Configuration of
FTP server
Onlining the site
(run link)
Information required for deployment
You cannot run setup without this information. Ask the provider for the information.
Information required for deployment, the host must give the developer the following information:
- Name of the web server where the site will be installed (or IP address)
- Login and password defined on the FTP server
When deploying by FTP, the developer must specify in WDDeploy:
- the information provided by the host
- the files to install
Part 7: Deploying a site

110
Deploying a dynamic WebDev site
Types of deployment
WebDev offers three ways to deploy a dynamic site:
- deployment by hard media (CD-ROM, and so on), with creation of a setup version on
CD-ROM for the host
Development
computer
Host
Creation of setup version
by developer on hard
media (CD-ROM, and so
on)
Installation of WebDev
site and setting
administrator
parameters
Onlining the site (run link)
- remote deployment from the development computer (file transfer by internet, FTP)
Part 7: Deploying a site
Development
computer
Creation of setup version
by FTP
Onlining the site (run link)
Host
Configuration of FTP
server and
account manager
(WD100ADMIN.EXE)

111
- remote deployment from an administration computer (file transfer by internet, FTP)
Development
computer
Web server
Creation of setup package
Configuration of FTP
server and
account manager
(WD100ADMIN.EXE)
Onlining the site (run link)
Package
transmission
Site setup
Administration
computer
Package execution:
Site setup on
server by FTP
Choosing a deployment method
The choice of deployment method mainly depends on the host constraints and on the location
of the deployment server (remote or onsite).
Setup by hard media is recommended if the Web server is easily accessible (e.g., on the
same premises as the development team).
Remote setup (by FTP) from the development computer is recommended if the development
computer is not easily accessible. There must be a standard FTP server on the development
computer. Before remote setup, the host must configure the FTP server and
the WebDev account manager.
Part 7: Deploying a site

112
Remote setup (by FTP) from an administration computer is recommended if the developer
does not know what the server characteristics are when the setup program is created.
The setup program here is called a "Package".
If a site is intended for several customers, you can create a single package and distribute
it to all of them.
The server settings (address, FTP account, and so on) are specified when the package is
run on the administration computer.
Deployment on hard media: information required
For deployment on hard media, the information on site setup and settings is given in the
setup preparation wizard and in the setup wizard.
To prepare setup, you must provide:
- the setup directory,
- the files to install,
- the setup generation directory.
For setup, you must provide:
- the data file directory,
- the site file directory.
After setup, you must configure the site characteristics (connection timeout, number of
connections, and so on) in the WebDev administrator (deployment version).
Part 7: Deploying a site

113
Deployment by FTP from the development computer: information required
You cannot run setup without this information. Ask the provider for the information.
Before deploying by FTP, the host must give the developer the following information:
- Name of the Web server where the site will be installed (or IP address)
- Login and password defined in the WebDev account manager
- Login and password defined on the FTP server
When deploying by FTP, the developer must specify in the wizard:
- the information provided by the host
- the files to install
- the name of the data file subdirectory
- the site connection settings
Notes:
- You can delay setup and run it at a specified date and time.
- Setup and update by FTP are secured by password and data encryption.
Deployment by FTP from an administration computer: information required
When you create the setup program, no specific information is required.
When you run the setup program (from an administration workstation), the host must specify:
- Name of the Web server where the site will be installed (or IP address)
- Login and password defined in the WebDev account manager
- Login and password defined on the FTP server
Notes:
- You can delay setup and run it at a specified date and time.
- Setup and update by FTP are secured by password and data encryption.
Part 7: Deploying a site

114
Referencing a site
To visit to your site, web users must be able to find it. So your site should be proposed whenever
a web user enters keywords relating to it in a search engine.
To simplify its referencing, WebDev enables you to include a home page in your site. This
home page is where you describe your site and its keywords.
Example of home page automatically created by WebDev:
Part 7: Deploying a site
You can include a home page in your site:
- when the project is created (in the project creation wizard).
- when the project is developed (option "Project .. Site Referencing (Home Page)").
Several home page templates are available.

115
Implementing a dynamic WebDev site
Your dynamic WebDev site can be accessed as soon as it is implemented. Implementing
a dynamic WebDev site means activating it.
A dynamic WebDev site can be activated in a number of ways:
- during setup by FTP: there is a check box to activate it automatically after setup.
- by the remote administrator (see “Maintaining a dynamic WebDev site”, page 125).
- by the WebDev administrator on the development computer ("WebDev site locked for
Update" option in "Sites" tab).
Part 7: Deploying a site

116
Dedicated and shared servers?
Hosts propose two types of servers to install your WebDev sites:
- shared server: server with resources shared by several customers (customer = hosted
company)
Shared features :
- WebDev Application Server
- operating system
- registry
- Web and FTP servers
Disk space
customer 1
Disk space
customer 3
Disk space
customer 2
Disk space
customer n
Part 7: Deploying a site
Characteristics:
The host provides a server for different customers.
The host:
- configures the FTP server.
- decides the maximum number of connections for all the dynamic sites of one customer
(with the WebDev account manager).
Setup and update of dynamic or static sites can be done by FTP.

117
- dedicated server: the server is reserved to one customer. The host only provides internet
access (IP address, cable, and so on). The machine is either rented by the host or
provided by the customer.
Computer dedicated
to customer:
- Web server and FTP server if
necessary
- operating system
- WebDev Application Server
- WebDev sites
Characteristics:
The host only provides Internet access (IP address, cable, and so on).
The customer must:
- provide (or hire) the server
- configure the server (system, and so on).
- install the Web server
- install and configure WebDev sites (by FTP or CD-ROM)
Part 7: Deploying a site

118
Choice of server?
The table below describes the advantages and disadvantages of the different types of servers.
Whatever server is chosen, a deployment license is required for each dynamic WebDev
site installed on it.
Each server hosts one or more dynamic WebDev sites.
Server Advantages / Disadvantages When to use this
server?
Shared
Main advantages:
- Lower cost
- Server administrated by the host
Main disadvantages:
- Memory resources shared by all the sites on
the server.
- If one site is down, all the sites on the server
are down.
- Standalone executables can rarely be used.
- Access to data is not secured: Non-authorized
persons could access data: the host, and
even other customers if the server is not configured
properly. Our advice: encrypt the data
files to prevent any unauthorized use.
A shared server is recommended
for:
- sites with few hits (up to
20 or 30 simultaneous
connections),
- sites requiring little memory
(no large calculations
on the server),
- sites in startup phase.
Part 7: Deploying a site
Dedicated
Main advantages:
- Server resources available for the site(s) installed.
- Custom management of data download:
- replication by email,
- WDREPLIC
- file copy by FTP.
Main disadvantages:
- High cost
- Server entirely administrated by the customer
in most cases.
A dedicated server is recommended
for:
- sites with many hits,
- sites requiring a lot of
disk space and memory,
- sites with sensitive data,
- dynamic sites.

119
Installing a dynamic WebDev site with a
specific configuration
1. Installing on a Web server run on Windows (95, 98, NT, 2000) or Linux
Internet
Windows server
Installed on the server:
- WebDev application server
- Dynamic WebDev site
- Windows Web server
Internet
Linux Server
Installed on the server:
- WebDev application server
- Dynamic WebDev site
- WebDev server run on Linux
Part 7: Deploying a site

120
2. Installing on a Windows server, with Internet access via UNIX
UNIX server
UNIX Web server
Static pages
Internet
Windows server
- WebDev Application Server
- Dynamic WebDev sites
- Windows Web server
Part 7: Deploying a site
1. Open a static page. The static page is located on the UNIX server.
2. Run a dynamic WebDev site (on the Windows server) via a link in the HTML static page.
3. The WebDev site operates in the usual way.
Note: the same configuration can be used for a Linux server.

121
3. Installing on a Windows or Linux server with Load Balancer
The Load Balancer system spreads the number of connections to a dynamic WebDev site
over several computers.
Internet
Load
balancer
Server
Server
Server
Data server
Solution 1: Install the dynamic WebDev site only on the data server.
This solution involves installing:
- the WebDev application server on each Web server,
- the dynamic WebDev sites and data files on the data server.
Part 7: Deploying a site

122
Solution 2: Install the dynamic WebDev site on all Web servers.
This solution involves installing:
- the WebDev application server and dynamic WebDev sites on each Web server.
- the dynamic WebDev site data files on the data server.
Part 7: Deploying a site

PART 8
Maintaining a site

125
Maintaining a dynamic WebDev site
Deploying a dynamic site is an important step in site development, but not the last: this is
where site maintenance starts.
Maintenance involves:
- Managing the dynamic sites: A remote WebDev administrator can be run from any
browser and any computer. This administrator is used to configure access to dynamic
sites, regular updates by FTP, and so on.
- Updating the dynamic sites: rectifications, new features, and so on.
You can upgrade dynamic sites by remote update (FTP) or by setup with physical media.
- Monitoring access to the Web server: A monitoring robot is used to regularly test access
to the Web server. If there is a problem (server and WebDev sites locked, and so
on), an email is automatically sent to the dynamic site manager. You can also restart
the WebDev engine or reboot.
Development
computer
Monitoring Robot
Monitoring the WebDev
engines (on the
development computer
for a shared server)
Update
WebDev site update
from the development
computer by FTP
Web server:
- WebDev administrator
- Dynamic WebDev site
- Web server
Monitoring Robot
Monitoring the WebDev
engine (recommended for
a dedicated server)
Remote administrator
Management of
dynamic WebDev sites
Part 8: Maintaining a site

126
Consulting hits statistics for dynamic sites
It is very important to have exact statistics on visits to your sites.
How do you find out who visited it, what pages they looked up, what applications they
used, what site they came from?
WebDev has a complete statistics tool for dynamic pages: WDStatistic. This tool can be
installed on any computer.
Here are some examples of statistics provided by WDStatistic: number of connections per
day, pages viewed, operating systems and browsers of web users, and so on.
Examples of statistics for dynamic sites:
Part 8: Maintaining a site

127
Retrieving data on a site
A business site enables web users to place orders, make bookings and so on.
There are several ways to retrieve this information.
Tip: process the retrieved data in a WinDev "Back Office" application.
1 Retrieving data from a site
1.1 By email:
Principle:
Web user
Server
- Dynamic WebDev site
- WebDev application
server
Company
HQ
1. The web user places an order on the site.
2. The WebDev site tells the web user that the order has been recorded and will be confirmed
by email.
3. The WebDev site sends an email to the company HQ with the order that was placed.
4. The company sends the web user an email to say that the order will be processed.
Advantages:
- Easy to implement.
- No additional executable program required on the server.
Disadvantage: Data retrieval only: no data update sent to the server.
This solution can be used with a shared server.
This solution is recommended for e-commerce sites with a limited number of orders.
Part 8: Maintaining a site

128
1.2 By FTP:
WebDev can be used for regular update of the WebDev site data files. The backup is sent
to the company HQ by FTP. Then you:
- retrieve the compressed backup of data files
- decompress the files (with a WinDev application)
- process the data in the files.
Advantages:
- Easy to implement.
- No additional executable program required by the host.
Disadvantage: All application data files are retrieved.
This solution can be used with a shared server.
2 Replication
Replication is used for updating remote databases with the same structure such as a Web-
Dev site database and the WinDev application database at a company HQ.
Part 8: Maintaining a site
For instance, a database for order input and stock management is used on a WebDev site
(online order) and at the company HQ (phone or mail order).
Replication is used to:
- send online orders to the company hq (one-way replication)
- send online orders to the company HQ, and send stock updates to the website (twoway
replication)
Caution: Replication constraints must be taken into account when the project is created.
There are several rules to follow when the analysis and the file items are described.
There are two types of replication:
- by email
- with WWReplic

129
2.1 Replication by email
An email engine is installed:
- on the server. This engine is supplied with WebDev.
- at the company hq.
An email is created whenever time the database is modify (addition, modification, deletion).
It contains the information required to update the remote database. It is sent and
processed by the email engine.
Company HQ
- Back Office
application (WinDev)
- Email engine
Data transfer by email
Web Server
- Front Office application
(WebDev)
- Email engine (supplied
with the WebDev application
server)
Advantages:
Data can be updated:
- from the server to the company hq.
- from the company hq to the server.
Requirements:
An email engine as a background task on the server and on the computer receiving the
emails at company HQ.
This solution is recommended for a site installed on a dedicated server (an executable
cannot always be run on a shared server).
Part 8: Maintaining a site

130
2.2 Replication with WDREPLIC
WDREPLIC is a tool used to update remote databases. It is supplied with WebDev and Win-
Dev.
Company HQ
- Back Office
application (WinDev)
- WDREPLIC
Data transfer
Web Server
Transfer directory
on the
Web server
- Front Office
application (WebDev)
- WDREPLIC
Part 8: Maintaining a site
Advantages:
Data can be updated:
- from the server to the company hq.
- from the company hq to the server.
Requirements:
- WDREPLIC must be run on the server for replication (e.g. by a BATCH process).
- Direct access and read/write rights in the transfer directory on the server.
This solution is recommended for an application installed on a dedicated server with direct
access.

PART 9
Appendices

133
Main new features in WebDev 10
Read this section if you already know WebDev 9.
WebDev 10 has many new features for developing dynamic WebDev sites or deploying
static WebDev sites.
It is fully compatible with WinDev 10 and WinDev Mobile 10.
• Project Editor:
•Source Code Manager (see page 28).
•Custom organization of the panes and tabs in the environment ("Project" pane, "Analysis"
pane, and so on).
•Custom Notes: for entering your own reminders on project elements ("New Custom-Notes"
option in the popup menu).
•FishEye: zoom on the part of the hovered project graph ("FishEye" icon).
•Detection of unused project elements with the option of deleting or archiving them
("Tools .. Clear Project Directory").
•Component images in custom-folders.
•Disabling of a warning ("Don’t display" option in the popup menu).
•Page Editor:
•New controls: Chart, iFrame, Internal Page, Site Map Path, Thumbnail.
•Improved site image management: you can manage the directory_WEB as you please.
•3-image mode for button images.
•Loopers with breaks, adaptable loopers.
•RID (Rapid graphical Interface Design): to create just the window interface based on the
project analysis (see page 34).
•Interactive zoom: zoom of a specific part of a page ("Display .. Toolbars .. Additional modules
.. Interactive zoom" option).
•Control "Details" tab: easy-to-understand visual options.
•Multilingual: description of the date, time, currency and numeric formats in a given language
("Languages" tab in the project description).
•AWP pages with automatic context.
•Page template GO available.
•Analysis of dependencies and broken links.
• Code Editor:
•Brick of Code: ability to enter reusable pieces of code ("Code .. Bricks of Code .. Manager
of Bricks of code").
•Function tooltip: displays return values.
•Assisted Input: proposes the page parameters.
•Completion: list of elements already handled.
•Automatic correction: proposes a list of possible corrections.
•Variables spell checker.
Part 9: Appendices

134
•Centralized error management.
•Automatic variables and controls prefixing.
•Debugger: multithread debugging, component debugging, code input available during
debugging, class and table edit, and so on.
•UML Editor:
•Automatic update of diagram when the code of a class or structure is modified.
• Modeling editor:
•New editor to easily model the steps of a process, organization of a service, sequence of
an operating mode, and so on.
• Database:
•HFDiff utility: compares the contents of two data files with the same structure.
•Hyper File Client / Server: supports transactions, logging and integrity constraints.
•3-Tier (see page 98).
•Hyper File Client / Server file administrator via the internet.
•Linux:
•Print functions available in Linux.
•New functions available (email, HTTPQuery, ScriptDisplay, ScriptExecute, and so on).
•3-Tier (see page 98).
•Hyper File Client / Server file administrator via the internet.
•PHP:
•Hyper File orders available in MySQL.
•More powerful PHP RAD.
•New functions supported (NetIPAddress).
•Hyper File Client / Server file administrator via the internet.
Part 9: Appendices
Programming
Main new programming features:
• Impact Study of Modifications.
• Creation of procedures by code selection.
• Search through language tables, selected rows or all rows in a table control (FOR ALL
instruction).
• New functions:
•Timing functions (ChronoXXX functions).
•Functions for managing HSL colors.
•...

135
You already know WinDev
What is different in WebDev:
- WebDev is used to create pages while WinDev creates windows.
- Different types of code can be entered: a W-Language code run on the server, a W-Language
code run on the browser, and a Javascript code run on the browser. If you create
a PHP page, an additional code displays: a PHP code running on server.
- There are new specific W-Language functions for the internet and intranet (see the list
on page 136).
- The W-Language functions that serve no purpose for internet and intranet no longer
exist (see the list on page 138).
- Some W-Language functions can only be used in an executable process in server code.
- Some W-Language functions can only be used in an executable process in browser
code.
- New types of controls designed for Internet/Intranet applications:
• Formatted Display Control
• Java Applet Control
• Cell Control
• Flash Control
• Clickable Image (Map Area)
• iFrame Control
• HTML Caption
• Link Control
• Horizontal Rule
• Internal Page Control
• Pager Control
• HTML Table Control
• Thumbnail Control
- Some types of control that serve no purpose for internet have gone: scrollbar, slider,
ActiveX, OLE Object, Tab, Spin, …
Part 9: Appendices

136
W-Language functions specific to
WebDev 10
(Details in the W-Language online help)
Part 9: Appendices
AddFavorite ......................................Adds a web address to a list of favorites.
ASPDisplay ........................................Calls an external ASP script and returns the result page in the current
browser window.
ASPExecute .......................................Calls an external .asp script and returns the result in a string. An http
query is run: you can use a POST or a GET method.
BrowserClose ....................................Closes the current window in the browser and stops the execution of
the current code.
BrowserIPAddress ............................Returns the IP address of the web user’s computer connected to the
WebDev site.
BrowserName ...................................Returns the name of the web user’s browser.
BrowserOpen ....................................Opens a new window in the browser.
ChangeAction ...................................Enables you to specify the action to take when the HTML page displayed
in the browser and the page context on the server are desynchronized.
ChangeTarget ...................................Changes the page target frame
ConnectionOccurrence ....................Returns the number of instances of the current WebDev site running
on the server.
ContextExist ......................................Lets you find out whether a page context exists on the server.
ContextClose ....................................Closes a page context.
ContextOpen .....................................Opens a new page context without returning the information to the
browser.
CookieWrite ......................................Writes a cookie on the web user’s computer the next time a WebDev
page is displayed in the browser.
CookieRead ......................................Retrieves the value of a cookie saved on the web user’s computer.
CurrentPage ......................................Returns the name of the page with the current W-Language code.
DynamicSiteDisplay .........................Displays a dynamic site (created with WebDev) in the web user’s browser
from a dynamic or static WebDev page.
EmailOpenMail .................................Opens the default messaging system on the browser computer.
EmailStatus ......................................Returns the status of an email sent in an SMTP session opened in
asynchronous mode.
FileDisplay ........................................Returns a specific file to the browser.
FileToPage ........................................Automatically initializes controls in a page with the values of the linked
items in the current record (loaded in memory) of the Hyper File
file.
FolderWeb ........................................Returns the path of the directory containing the images, Javascript files,
Java applet files and other files accessible from the browser, and
so on.
FramesetDisplay ..............................Displays a WebDev frameset in the Web user’s browser.
FramesetRefresh .............................Updates a frameset displayed in the web user’s browser according to
the context on the server.
FramesetUse ....................................Displays a WebDev frameset in the web user’s browser and closes all
the current page and frameset contexts.
fWebDir .............................................Returns the full physical name of the directory containing the images,
Javascript and Java files of the WebDev site.
grImageSize ......................................Defines the size of the image containg a chart.
ImageXPos ........................................Returns the horizontal position of the mouse cursor in relation to an
image control.
ImageYPos ........................................Returns the vertical position of the mouse cursor in relation to an image
control.
ImageZone ........................................Returns the number of the area clicked by a web user (clickable image
only).
JSMethod ..........................................Lets you execute a Javascript method on an element in the current page.

137
JSProperty .........................................Lets you access features specific to objects present in the current page.
PageAddress ....................................Get the internet address of a page.
PageDisplay ......................................Displays a page in the Web user’s browser.
PageExist ..........................................Checks whether the specified page is currently displayed in the web
user’s browser.
PageInitialization ..............................Resets (or not) the controls in the current page and runs the control
initialization processes.
PageParameter ................................Returns the value of a parameter passed to the current page.
PagePosition ....................................Scrolls a page to position a control in the visible part of it in the browser.
PageRefresh .....................................Refreshes a page displayed in the web user’s browser according to
the context on the server.
PageSubmit ......................................Validates the specified page and runs a button.
PageToASP .......................................Sends the data in the page currently displayed in the browser to an
ASP server.
PageToEmail .....................................Sends the data in the page currently displayed in the browser by
email.
PageToFile ........................................Automatically initializes the value of file items with the value of page
controls.
PageToJSP ........................................Sends the data in the page currently displayed in the browser to a JSP
server.
PageToPHP .......................................Sends the data in the page currently displayed in the browser to a
PHP server.
PageUse ............................................Displays a WebDev page in the web user’s browser and closes all the
current page contexts.
PHPDisplay .......................................Calls an external PHP script and returns the result page in the current
browser window.
PHPExecute ......................................Calls an external PHP script and returns the result in a string.
PreviousPage ...................................Returns the name of the previous page.
ScriptDisplay ....................................Calls an external script (.php, .asp. mhtml or .mht for example) and returns
the result page in the current browser window.
ScriptExecute ...................................Calls an external script (.asp or .php for instance) and returns the result
in a string. An http query is run: you can use a POST or a GET
method.
SemiDynamicPageDisplay ...............Displays a semi-dynamic page in the web user’s browser from a dynamic
or static WebDev page.
SiteAddress ......................................Returns the internet address of the connection to a dynamic WebDev
site located on the same server.
SiteMapPathAddLink (*) ..................Adds a link to the site map path.
SiteMapPathDeleteAll (*) .................Deletes all the links from the site map path.
SiteMapPathDeleteLink (*) .............Deletes a link from the site map path.
SiteMapPathInsertLink (*) ..............Inserts a link in the site map path.
SiteMapPathModifyLink (*) .............Modifies a link in the site map path.
SSLActive ..........................................Enables or disables the SSL secure mode.
UploadCopyFile ................................Saves a file uploaded by a web user on the server.
UploadFileName ..............................Find out the name of a file uploaded by a web user.
(*): New functions of WebDev version 10.
Part 9: Appendices

138
List of WinDev 10 functions not available
in WebDev (functions that serve no
purpose for internet / intranet)
Part 9: Appendices
ActiveXEvent AgentAdvice AgentBeep AgentChoice AgentCreate AgentHeight AgentHide
AgentInput AgentMessage AgentMove AgentParent AgentShow AgentTerminate AgentWidth
AgentXPos AgentYPos AnimationGetParameteter
AnimationSetMode AnimationSetParame-
AnsiToOem
AppliControl
AutomationEvent AutomationParameter AutoRunAdd AutoRunDelete Beep BuildAutomationVariant
BuildBrowsingTable
cdbAdd cdbCancelSearch cdbClose cdbCol cdbDateTimeToInteger cdbDelete cdbFound
cdbIntegerToDateTime cdbListFile cdbModify cdbNbCol cdbNbRec cdbOpen cdbOut
cdbRead cdbReadFirst cdbReadLast cdbReadNext cdbReadPrevious cdbReadSeek cdbRecNum
cdbReset cdbWriteCol ceConnect ceConnectionStatus ceCopyFile ceCreateShorcut ceDeleteFile
ceDeleteShortcut ceDir ceDisconnect ceFileDate ceFileExist ceFileSize ceFileTime
ceListFile ceMachineName ceMakeDir ceOEMInfo cePlatform cePowerStatus ceProcessorType
ceRegistryCreateKey ceRegistryDeleteKey ceRegistryDeleteValue ceRegistryExist ceRegistryFirstSubKey ceRegistryListValue ceRegistryNextKey
ceRegistryQueryValue ceRegistrySetValue ceRegistrySubKey ceRemoveDir ceRunExe ceSysDir ceWindowsVersion
ceWinEnum ceWinTitle ceXRes ceYRes ChangeAlphabet ChangeKeyboard ChangeSource
ChangeTemplate Clipboard ClipboardFormat ClipboardHeight ClipboardWidth Close ComboClose
ComboOpen Confirm ControlClone ControlDelete ControlInOutReason ControlOver ControlTab
CreateShortCut CurrentColumn CurrentField CurrentSubscript CurrentTitle CurrentWin CursorCapture
CursorDisplay CursorInUse CursorLoad CursorModify CursorPos CursorUnload DelayBeforeClosing
DeleteParameter DeleteShortCut dHorizontalSymmetry Dialog dInvertColor DisableAAF DnDAccept
DnDCacheData DnDCursor DnDEvent DnDForce DnDGetData DnDIsDataAvailable dResize
dRotation dSaveImagePNG dVerticalSymmetry EmailProgressBar EndEvent EndTimer EndTimerSys
EnumControl EnumMenu EnumSubElement Event ExecuteAAF ExeListDLL ExeListProcess
ExePriority ExeRunning ExeTerminate ExplorerAccept ExplorerRetrieve fAttributeReadOnly fDetectRemovableStorage
fGraphicFilter FieldExist FieldFirst FieldNoSpace FileToPalm fImageSelect fLongName
fLongPath fMoveFile FontSelect fSelect fSelectDir fShortName fShortPath
gAlignment gBackground gCircle gCoord GetActiveObject gFont gImage
gLine gPen gpwGetFileInfo gpwGetUserInfo gpwInitAnalysis gpwLogin gpwMenuDescribe
gpwOpen gpwOpenConnection gr3DSParameter grDestinationWnd gRectangle grMenu grMenuOption
grOverlayChart grPrint grTooltip grWndSize Handle hCopyFileReplica HelpFile
HourGlass HtmlNavigate HTTPProgressBar iCloseReport IconInstall Iconize iDocumentCanceled
iDocumentPrinted InitParameter Input Instance InternetConnected iParameterPreview iSelectFont
iWindowCancel KeyPress KeyPressed LargeFontFactor LDAPConnect LDAPDisconnect LDAPFind
LDAPListAttributes LDAPListChildren LDAPNbValue LDAPReset LDAPValue ListInfoXY LoadImage
LoadParameter LooperPosition LooperSelect LooperSelectCount LooperSelectMinus LooperSelectPlus LooperXYInfo
Maximize MCIBegining MCIClose MCIEnd MCIErr MCIExecute MCIHeight
MCIMsgErr MCINumTracks MCIOpen MCIPause MCIPlay MCIPosition MCIPositionFormat
MCIRetrieve MCISize MCIStart MCIStatus MCIStop MCIStop MCITrack
MCIVolume MCIWidth MCIWindowSize MCUActive MCUOpen MDIActive MDIEnumChild
MDIOpen MDIParent MDIWindowMenu MenuAdd MenuCaption MenuInvisible MenuIsMarked
MenuMark MenuSelectMinus MenuSelectPlus MenuState MenuUnMark MessageAddCell MessageDeleteCell
NetConnect
MouseXPos MouseYPos MultitaskRedraw NetClientMessageBox NetClientSendMessage
NetCloseRemoteAccess
NetDirList NetDisconnect NetDiskList NetEndServer NetEraseFile NetExecute NetGetFile
NetMsgError
NetOpenRemoteAccess
NetRemoteAccessInfo NetRemoteAccessList NetRemoteMessage- NetRenameFile NetSendBuffer
Box
NetSendFile NetSendMessage NetServerOption NetStartServer NextField NextSubscript NextTitle
NumHelp OemToAnsi OKCancel OLEActivate OLECopy OLECreateCopy OLECreateEmpty

139
OLELoad OLEPaste OLEPlay OLESave OLEServer Open OpenChild
OpenPopup OpenPopupMenu OpenPopupPosition OpenSibling OrderLine PalmAdd PalmClose
PalmDelete PalmFilter PalmInstall PalmListCategory PalmListUsers PalmLoad PalmModify
PalmNbRec PalmOut PalmPosition PalmRead PalmReadFirst PalmReadLast PalmReadNext
PalmReadPrevious PalmRefresh PalmReinit PalmReset PalmToString PalmUninstall Ping
PopupField PostMessage PreviousField Progress bar RegistrySeek Restore ReturnToCapture
RTFAdd RTFInsert RTFLoad RTFReplace RTFSearch RTFSelection RTFToText
RunReportsAndQueries
SaveParameter SchedulerAddTask SchedulerAddTrigger SchedulerDeleteTask SchedulerDeleteTrigger
SchedulerModifyTask
SchedulerModifyTrigger
SchedulerOpenTask-
Properties
SchedulerTaskStatus
SchedulerReset SchedulerTaskList SchedulerTaskProperties
SchedulerTriggerProperties
sClose ScreenFirst ScrollBarShow SelectColor SelectionColor sEndEvent SendKey
SendMessage sEscape SetFocus sEvent ShowToolTip sInEntryQueue sInExitQueue
SocketAccept SocketClientInfo SocketConnectInfrared
SocketCreateInfrared SocketCreateUDP SocketDeny SocketWaitForConnection
sOpen Sound sParameter sRead StreamAccept StreamConnect StreamDisconnect
StreamInfo StreamPlay StreamReject StreamStop StringToPalm StringToUTF8 sWrite
SysColor SysColorRes SysErrorMode SysGetDC SysIconAdd SysIconDelete SysIconize
SysIconModify SysInstance SysMetric SysNameExe SysReleaseDC SysSetFocus SysShutdown
SysValidHandle SysWinActive SysWinHandle SysWinShow SysWinTitle SysXRes SysYRes
Table TableAdjust TableFixColumn TableInfoXY TableInputInProgress TableInputSearch TableMode
TableMoveColumn TableSelectCount TableSelectToFile tapiAnswerCall tapiBlindTransfer tapiCallDuring tapiCalledID
tapiCallEnd tapiCallerID tapiCallIsBusy tapiCallIsOver tapiCallIsWaiting tapiCallStart tapiCapability
tapiCompleteTransfer tapiDevice tapiDeviceList tapiDial tapiError tapiHangUp tapiHold
tapiKeyPressed tapiListen tapiNoAnswer tapiOrigin tapiPlay tapiRecord tapiSendKey
tapiStop tapiStopCallDetection tapiUnhold telLineDial TextHeight TextWidth Timer
TimerSys ToClipboard ToolbarDock ToolbarPosition ToolbarUndock ToolTipColor TreeInfoXY
TreePosition TreeSelectMinus TreeSort_55 TwainCurrentSource TwainListSource TwainScanZone TwainSelectSource
TwainSourceHeight TwainSourceWidth TwainState TwainToBMP TwainToClipboard TwainToControl TwainToGIF
TwainToJPEG
USBDetectRemovableStorage
USBDisconnect USBFind USBListDevice USBProperty UTF8ToString
VideoCapture VideoChangeDriver VideoConfigure VideoDisplay VideoListDriver VideoStatus VideoStop
Warning WHelp WinAdaptSize WinAnimationClosing WinAnimationNext WinAnimationOpening WinBackgroundImage
WinChangeAlias WindowBitmap WindowCount WindowsVersion WinIconBarHeight WinInactiveEffect WinInHeight
WinInput WinInWidth WinInXPos WinInYPos WinOutHeight WinOutWidth WinOutXPos
WinOutYPos WinRedraw WinSize WinStatus YesNo
Part 9: Appendices