|
|
|
You can optionally save scripts that contain errors. For compilation and execution, the latest script without errors is used. For editing, the latest script is used. |
|
|
|
The triggering of a Client event sends its JavaScript code plus the XPage context to an interpreter on the user's client. |
|
|
|
The editor provides styles, indentation, brace completion, and quotation mark completion. |
|
|
|
The Outline tab provides a hierarchical outline of the variables and functions defined in the script. |
|
|
|
A modal editor appears in its own window. Edits are not applied until the window closes. |
|
|
|
Content assist proposes coding alternatives based on the objects available in the current context. |
|
|
|
Syntax errors are detected for server scripts. |
|
|
|
An embedded window appears as part of the current context and allows immediate editing. The window can be maximized and minimized, then restored with controls at the top right of the window. |
|
|
|
The Reference tab provides a list of global objects and system libraries. |
|
|
|
You can set preferences to control the JavaScript editor. |
|
|
|
The Schema tab provides a list of data elements organized by data source. |
|
|
|
For a client event, everything happens on the client using the JavaScript™ processor available there. There is no back and forth with the server. |
|
|
|
All programming on an XPage is in JavaScript™ which can be employed server-side or client-side. |
|
|
|
A property value can be the return value of a script. |
|
|
|
A server event responds to a request from the client. For example, when the user clicks the Delete document button, the client sends a request to the Domino® server. The server performs the action, updating the data source, then sends a response to the client. |