The Tasks window contains a list of compiler errors and warnings. Compiler errors preclude successful web project compiling and must be eliminated. Development states, which cannot be compiled cannot be released because the corresponding web application do not run.
Compiler warnings relate to missing extensions, or to messages concerning accessibility. If compiler warnings are the only type of message that is generated, the development state will be successfully compiled nonetheless.
If individual messages are displayed hierarchically, it means that the errors indicated occur at various places in the web project. This can happen, for example, in connection with a missing extension that is referenced by a number of nodes. In such cases, the error need only be eliminated once.
To call up the relevant node in the definition tree view, double-click a table entry; Web Designer will then automatically go to the Node editor window. This behavior applies if the error is in the node. If the error occurs when the resulting code is compiled, you can double-click the error to display the Generated code (read only) view in the definition tree view.
|Display error message.
This button is only active when an error message has been highlighted in the list. By clicking this button a detailed error description is displayed. You can send an email message in the default email program using the Send as Mail button. The error message is automatically transferred to the email.
By clicking this button, errors can be shown or hidden.
By clicking this button, warnings can be shown or hidden.
Web SQL expressions can be created and executed in the query window. However, in order for this to occur the compilation must be successfully completed. This window integrates a toolbar of its own. The query window is divided into three sections.
NOTE: A WCF connection must be created for this function.
On the left, the currently available session collections are shown. The internal currently selected session is preset in the toolbar selection. Individual collections are bundled under the modules or components in which they were originally defined. The number of rows within the collection is shown next to the collection.
If you mark a database object in the hierarchy, the following context menu items are available. Which menu items are shown, depends on the database object you have marked.
|Show definition object||Takes you to the definition object in the definition tree view and marks the nodes with a color.|
|Show collection data (this entry is only available for a selected collection)||This displays an expression for the query in the SQL input box. More information about the collection is displayed below the SQL input box.|
|Show last used WHERE clause (this entry is only available for a selected collection)||This displays the last WHERE clause in the SQL input box. More information about the collection is displayed below the SQL input box.|
On the right-hand side of the window is an SQL query window. Here you can enter a query statement to be executed. The results of the query are also displayed in the part of the window.
To select another session
This displays a list of active sessions.
To view the current module
Only the module selected in the currently selected session is shown.
Note: If you click again, all module sessions are re-displayed.
To view the collection contents
The collection contents is displayed on the right side of the query window.
Sends a query.
The entered Web SQL expression is executed by clicking . If more than one such expression has been formulated, mark the expression that is to be executed. Only one expression at a time can be executed.
The expression being executed is evaluated against the module or component currently selected in the tree structure. Use Web SQL syntax for inputting the expression to be executed.
If the queried collection is a part of a component, the suffix must be appended to the collection name. the suffix displayed on the left side of the query window must be added to the collection name.
If an asterisk (*) is inserted in an expression as a placeholder for the columns that are to be displayed, only those columns that are needed (referenced) in the module are displayed.
To reopen a closed query window
This function is a debugging extension and is only available in debug mode. The evaluable Web SQL properties of an XML node for a specific control can easily be evaluated at runtime.
The Label node type, for example, has Text and Tooltip text Web SQL properties. Identifier and Value are additional Web SQL properties that are stored as HTML attributes and are Web SQL-evaluable.
|NOTE: If Web SQL expressions are not available during runtime, these expressions are extracted from the XML definition. If the runtime code no longer corresponds to the XML definition, a different result may be obtained from Web SQL expression evaluation.|
In the steps below, the evaluation is described using the Label node type as an example.
To evaluate the Web SQL expression of a property
The database object, represented as an XML node, is marked in the properties view.
The evaluable Web SQL properties belonging to the XML node are determined in the background and are listed as entries in the context menu. These entries are selected in the next step.
All the corresponding modules are listed in the tree structure in the query window and the definition for the selected Web SQL property is displayed in the SQL input box.
The results are shown below the SQL input box.
In the query window, you can use a filter to display information concerning one database object only, such as a component. This function can be applied to Module or Component database objects. By default, this filter is not enabled. If the information you require appears in several components or modules, you can open another database object with the filter enabled in the definition tree view. The information concerning the newly selected database object is displayed in the query window.
This function is available in debug mode.
To narrow the display in the query window to a specific database object
|NOTE: Before using this function, select the relevant database object and the corresponding property. For more information, see Evaluating the Web SQL Expression of a Property.|
The information displayed in the query window concerns the open component or module only.
|NOTE: If there is no information relating to the selected database object or if the selected document is not a component or module, the icon is shown next to the filter.|