The preview window shows how a specific web application will look and respond in the browser. This means that the preview window can be used to test out the entire functionality of all buttons, links and so on. The displayed view is rendered using Internet Explorer, which is installed in the current client. However, please note that other browsers or other versions of the same browser may generate views that differ from the preview. Hence it is advisable to perform an extensive layout test of the web appli- cation with the previously predefined browser versions.
A preview window can only be generated insofar as (a) the user does not log on to Web Designer through a system account; or (b) a person is selected following log on through a system account. This is necessary due to the fact that when a view is rendered, Web Designer assesses person-related de- pendencies (for example which person is allowed to view which menu item) and displays the results of
38
this assessment. This means that a realistic function test can only be realized in the preview window using such a person-related display.
The preview function also writes data to the database or deletes database objects if this function is ac- tivated by the user. Hence caution should be exercised when testing this function.
The preview window integrates a toolbar of its own, most of whose functions are used to manage de- bugging mode. When the debugger is activated, program functions are realized step by step rather than dynamically, thus enabling you to see which program step is actually being realized and the results yielded by the step. In addition, with the debugger activated, you can navigate at will to the query or data schema window.
Preview Window Toolbar
Functions of the Toolbar in the Preview Window
ICON FUNCTION or or
Demomode
The preview window switches to full screen mode; and all other Web Designer windows are covered. The resolution defined for the pre- view window is disregarded here. This button is only active with the window in a docked state.
or
View html source
This button, which is activated following successful compilation, opens a popup window containing the html source code generated by Web Designer. This function allows for debugging directly in the source code.
or
Recompile
This button, which is activated following successful compilation, allows for recompilation (for example after a change has been made in the definition tree window) without the need to select a person beforehand. The preview window is generated for the previously selected person.
In this process, the Compiler factors in all module and component changes that have been effected thus far in connection with the selected web project. Such changes need not be saved beforehand. or
Suppress execution
This function, which prevents any action from being executed in the preview window, is useful in cases where a specific definition tree node has been found in the properties window using the <Show def- inition object> function. When the function is activated, the object is underlined in blue.
or
Enable debugger
This field allows you to toggle the debugger on and off. “Debugger” is underlined in blue when the function is activated. All actions are executed in succession (for example one node at a time) when the debugger is deactivated.
If the debugger status is deactivated in “Paused” state, click the <Re- sume execution> button to resume debugging.
39
In addition to a toolbar, the preview window also has a foot bar. Apart from the functions shown in the following figure, the currently displayed Web Designer form is indicated on the left side of the status bar.
or or
Single step
The <Single step> button is only activated when the debugger is activated. When single step mode is activated (a state indicated by blue underlining), each time an action is realized the program stops at each executed step in the definition tree. When single step mode is deactivated, the action is realized until the next break point (break points are inserted in the definition tree at action nodes above the context menu).
or
Resume execution
This button is activated with the debugger deactivated insofar as any program steps remain to be carried out, for example no user entries are anticipated. Clicking this button launches realization of the next program step.
or or
“Slow Motion”-Debugging
If this button is enabled, the program is automatically run through a step at a time. This mode can be switched on or off during execu- tion. This saves the user from having to click so often.
or
Abort execution
This button is activated with the debugger deactivated insofar as any program steps remain to be carried out, for example no user entries are anticipated. Clicking this button cancels realization of the current program step.
or
Debug - step into
The debugger realizes all steps until the next action node.
Portion of the Preview Window Status Bar
Functions in the Preview Window Status Bar
ICON FUNCTION Status
Done here means that compilation and rendering of the current project state have been completed and that entries can be made in the relevant pages. Pixel lines
The pixel line count indicates the dimensions of the window area that are available for the display of rendered html code. This information obviates the need for scrollbars during programming in cases where the amount of avail- able browser space is known. This in turn is affected by the screen resolution and the number of menu bars displayed in the browser.
Functions of the Toolbar in the Preview Window
40