Page History
...
The first two items in the above list are due to technical restrictions in the browser, where item 2 is a design decision based on the restriction mentioned under item 1.
The reasons behind item 3 & 4 are of technical nature and are likely to be resolved in a future version of Servoy.
...
Solutions
...
Ironing out the differences
...
The solution to item 1 & 2 is to not use windows in combination with the Web Client: due to the fact that popups were abused on the web, every browser now comes with popup blockers that are enabled by default. Due to this, the defacto standard for web applications in general is a single window interface.
...
plugin.windows
plugins.dialogs
...
Tips & Tricks
...
Getting the active window
...
The currentcontroller object is a pointer to the topmost Form in the active window and thus can be used to retrieve the active window:
| Code Block |
|---|
currentcontroller.getWindow()
|
...
Checking if a Form is visible in the UI
...
The controller object of a Form has two useful functions to check if the Form is included or visible in the UI:
controller.getWindow()
If controller.getWindow() returns null, the Form is not included in the UI
controller.getFormContext()
...
Traversing the Window hierarchy
...
When having a reference to a JSWindow instance, the .getParent() of the JSWindow object can be invoked to get the parent window. Returns null for the topmost window in the hierarchy
Controller.getFormContext() returns a JSDataSet with the context in which a
Single Window Interface
Multi Window Interface
...
application.isFormIndialog
application.showForm???
application.setToolbarVisible
controller.getFormContext()
controller.getWindow()
| Wiki Markup |
|---|
controller.show(\[windowName\]) |
| Wiki Markup |
|---|
controller.showRecords(data, \[windowname\]) |
JSWindow
plugins.window
Overview
Content Tools
Activity