1. Introduction
The HomeServer AjaxVisu provides you with a browser-based operating interface for
Gira HomeServer or FacilityServer. The visualisation is realized in HTML with the latest Ajax
technology.
1.1. General notes
The information, data, values, etc. contained in these documents may be changed
without prior notification. The illustrations are likewise subject to change.
Subject to technical modifications!
Subject to technical modifications!
Note: Current information on the Gira Website
As the software for the device purchased by you is being continuously
further developed and updated, information in this manual may no longer be up-to-date.
The latest product information is always available on the Gira website:
Http://www.gira.de
Current software updates and documentation for your product are also available.
Http://www.gira.de
Current software updates and documentation for your product are also available.
1.2. System requirements
The following is required for using the AjaxVisu:
- HomeServer or FacilityServer.
- Expert software from Version 2.2.071114 (from 14/11/2007 or newer)
- HomeServer or FacilityServer firmware from Version 2.2.071114 (from 14/11/2007 or newer)
- Operating device with Internet browser (e.g. Windows PC or Apple computer)
1.3. Area of application
The HomeServer AjaxVisu expands the existing HomeServer/FacilityServer
visualisation functions. Any other use of the device and software is not permitted. Gira shall
assume neither legal responsibility nor a warranty of any kind for errors and damage resulting
from the improper use of the device and/or the related software.
The areas Menu and Query are not included in the scope of the
application.
2. AjaxVisu
2.1. Sample project
A sample project is included with the HomeServer/FacilityServer Expert
software. The name of the sample project is:
Sample-yyyymmdd-av.de
Here "yyyymmdd" stands for the date of the respective file.
Sample-yyyymmdd-av.de
Here "yyyymmdd" stands for the date of the respective file.
2.1.1. Scope of sample project
The sample project has a resolution of 1024 x 768 in the full-screen mode.
The following visualisation masks are available:
- UTC
- Buddy list
- Value entry
- Date+Time entry
2.1.2. Several projects
If you work on several project simultaneously and transfer them alternately
to the HomeServer or FacilityServer, make sure you do the following:
Note
Empty the cache of your browser each time before changing
projects!
As you use the same file names for different projects, however the contents
of these files may differ, incorrect displays in the browser may result if the browser
accesses the cache instead of the current page and attempts to display the page of the
same name from a different project.
2.2. HSAjaxFramework (tool)
HSAjaxFramework is a Windows tool that starts the MS Internet Explorer (IE). In
the process, no control element of the IE, e.g. navigation buttons etc., are displayed.
The window position, window size, edge width and window display can be set with parameters.
HSAjaxFramework can be run in two different ways: With or without parameters. The <key> described below can be transferred as a parameter. When run without parameters, a selection mask appears.
When a URL is entered in the selection mask, HSAjaxFramework is started in the full-screen mode.
The window position, window size, edge width and window display can be set with parameters.
HSAjaxFramework can be run in two different ways: With or without parameters. The <key> described below can be transferred as a parameter. When run without parameters, a selection mask appears.
When a URL is entered in the selection mask, HSAjaxFramework is started in the full-screen mode.
2.2.2. Location and scope
HSAjaxFramework can be found under tools\hsav.
All parameters that can be set are created in the definition file list.hs
(XML format).
Use a text editor for this purpose.
Use a text editor for this purpose.
The file consists of the following parameters (XML tags):
Parameter definition list.hs
Parameter definition list.hs
| Parameter | XML tag | Description |
|---|---|---|
| Section | <device> | A HomeServer or FacilityServer is defined within this XML tag. Several HS/FS can be defined in this file; each one with its own <device> XML tag. |
| Unique key | <key> | The program can be run with this parameter. Then all other parameters are
automatically taken into account. Example: Code listing for <key> |
| Window size | <windowstate> | 0 = normal 1 = maximised |
| Window heading | <border> | 0 = without border (entire screen, no Windows bar) 1 = with border (window has a heading line and the Windows bar is visible) |
| Window display | <ontop> | 0 = normal 1 = window always in the foreground |
| Description | <text> | Designation of the HS/FS for the selection list in the program |
| URL for run HS/FS | <url> | Please note here that characters not compliant with XML must be masked. For example: "&" must be written as "&". |
| Horizontal window position when called | <pos_x> | Position at which the left-hand upper corner of the window is located. (Right/Left) Is only taken into account if <windowstate>=0. |
| Vertical window position when called | <pos_y> | Position at which the left-hand upper corner of the window is located. (Top/Bottom) Is only taken into account if <windowstate>=0. |
| Window width | <width> | Is only taken into account if <windowstate>=0. |
| Window height | <height> | Is only taken into account if <windowstate>=0. |
2.2.3. Example <key>
Source code list.hs:
<?xml version="1.0" encoding="ISO-8859-1"?>
<devices>
���<device>
������<key>Gira</key>
������<text>Gira sample project</text>
������<url>http://192.168.0.11/opt/hsav-gira_en/startgast.htm</url>
������<windowstate>1</windowstate>
������<border>1</border>
���</device>
</devices>
<devices>
���<device>
������<key>Gira</key>
������<text>Gira sample project</text>
������<url>http://192.168.0.11/opt/hsav-gira_en/startgast.htm</url>
������<windowstate>1</windowstate>
������<border>1</border>
���</device>
</devices>
2.2.4. Parameter transfer
The program can also be started with a parameter transfer.
If no parameter is transferred, a selection mask appears.
Figure 2.1: Selection mask for parameter transfer
Figure 2.1: Selection mask for parameter transfer
Description of elements of selection window
| Parameter | Digit | Description |
|---|---|---|
| Window heading | Item 1 | Name of the program with the version number. |
| Radio button | Item 2 | Click here to select an HS/FS from the list. |
| "Key" column | Item 3 | Unique code for the designation of an HS/FS. This value can also be transferred to the HSAjaxFramework as a parameter when running. |
| "Description" column | Item 4 | Brief description of the HS/FS. |
| Radio button | Item 5 | Click here to view a URL in the input field.
Examples:
|
| OK button | Item 6 | Click here to confirm your entries. |
2.3. Start-up
2.3.1. Setup
Existing projects can be expanded with the HomeServer AjaxVisu without an
additional design. Open the menu item Setup in Expert. Create the following two
symbols in the Project settings mask (see Fig. 2.2). The image ID is decisive for
the definition.
Figure 2.2: Creating two symbols under "Project settings"
- Image ID: XXPAGE
- Image ID: XXPOPUP
Figure 2.2: Creating two symbols under "Project settings"
Note: Do not create by copying or duplicating!
Please note that the two symbols cannot be created by copying or
duplicating another symbol!
2.3.2. User rights
To be able to use the HomeServer AjaxVisu, the users in question have to be
granted access under
Users / User rights / Interface / Client program
.
Users / User rights / Interface / Client program
.
2.3.3. Page size
If the area of a standard visualisation page is to be limited, this is
possible with the XXPAGE symbol. If this symbol is set on a visualisation page, it defines
the lower right-hand corner. All information which lies outside the limited area is not
shown.
Figure 2.3: Example for the setting of the page size
Create the symbol as described above:
Image ID: XXPAGE
Designation (name): "Ajax_Page_Size".
The symbol can be used as an option. If this symbol is not used, the browser shows the entire area of the visualisation page.
Using a small, square symbol is advisable. The upper left-hand corner of the symbol defines the page size. The size and colour of the XXPAGE symbol are not significant, as it of course lies outside the defined display area.
Figure 2.3: Example for the setting of the page size
Create the symbol as described above:
Image ID: XXPAGE
Designation (name): "Ajax_Page_Size".
The symbol can be used as an option. If this symbol is not used, the browser shows the entire area of the visualisation page.
Using a small, square symbol is advisable. The upper left-hand corner of the symbol defines the page size. The size and colour of the XXPAGE symbol are not significant, as it of course lies outside the defined display area.
2.3.4. Mask size and visualisation area
The largest HTML mask included with the sample project is 331 pixels wide
and 240 pixels high.
If you define the size of the visualisation area with the XXPAGE symbol to be smaller than the size of the HTML masks, the HTML masks cannot be completely shown.
If you define the size of the visualisation area with the XXPAGE symbol to be smaller than the size of the HTML masks, the HTML masks cannot be completely shown.
2.3.5. Popup page
The HomeServer AjaxVisu offers popup visualisation pages.
If a visualisation page is to be laid over the visualisation page to be called (popup), it is possible with the XXPOPUP symbol. If this symbol is set on a visualisation page, it defines the lower right-hand corner and at the same time it defines this page as a popup. All information which lies outside the limited area is not shown. The page is laid centred over the existing page when it is called.
Figure 2.4: Creating a symbol for a popup
Left: Draft of popup page. Right: Called popup in the visualisation
Create the symbol as described above:
Image ID: XXPOPUP
Designation (name): "Ajax_PopUp".
Using a small, square symbol is advisable. The upper left-hand corner of the symbol defines the page size.
In addition, the popup page should be surrounded by a transparent frame so that the frame around the popup is not visible.
A mask (e.g. message archive) can be called from a popup page. However, it is not possible to call another visualisation or popup page within a popup page.
Therefore, a navigation element must be defined on each popup page (e.g. "Navigation: Back" or "Navigation: Starting point"). A draft of the later popup can be seen together with the small red XXPOPUP symbol, which limits the area to be shown, in the left-hand image (see Fig. 2.4). The result which can then be seen as a popup in the HomeServer AjaxVisu is shown on the right.
With a popup page it is possible, for example, to realise device-specific popups, e.g. a popup for blind control.
If a visualisation page is to be laid over the visualisation page to be called (popup), it is possible with the XXPOPUP symbol. If this symbol is set on a visualisation page, it defines the lower right-hand corner and at the same time it defines this page as a popup. All information which lies outside the limited area is not shown. The page is laid centred over the existing page when it is called.
Figure 2.4: Creating a symbol for a popup
Left: Draft of popup page. Right: Called popup in the visualisation
Create the symbol as described above:
Image ID: XXPOPUP
Designation (name): "Ajax_PopUp".
Using a small, square symbol is advisable. The upper left-hand corner of the symbol defines the page size.
In addition, the popup page should be surrounded by a transparent frame so that the frame around the popup is not visible.
A mask (e.g. message archive) can be called from a popup page. However, it is not possible to call another visualisation or popup page within a popup page.
Therefore, a navigation element must be defined on each popup page (e.g. "Navigation: Back" or "Navigation: Starting point"). A draft of the later popup can be seen together with the small red XXPOPUP symbol, which limits the area to be shown, in the left-hand image (see Fig. 2.4). The result which can then be seen as a popup in the HomeServer AjaxVisu is shown on the right.
With a popup page it is possible, for example, to realise device-specific popups, e.g. a popup for blind control.
2.4. Start files
There are three standard files:
- startguest.htm
- start2.htm (variant of startguest.htm)
- start3.htm (alternative to startguest.htm with different touch technology)
Code listing using the file startgast.htm as an example (see: Expert
directory, under /hsupload/hsav-gira_en/):
Explanations
The explanations refer to the setting options in this file. It is assumed
that the standard HTML commands are known.
| line | Explanation |
|---|---|
| 3 | Page heading or tab heading in the browser. |
| 5 - 10 | CSS settings for Login and Reconnect masks. |
| 6 | Background settings. Current: colour. |
| 14 | <div> "xbase". This container contains the entire visualisation. |
| 17 - 19 | <div> "xmark"with img "xmarkimg". The image entered here (img/hide.png) is required for the click display. |
| 22 | <div> "xreconnect". Container for the Reconnect-Display mask. |
| 23 - 36 | This <div> defines the message box in the Reconnect-Display mask. The <span> with the IDs "tryCnt" and "tryState" must be present, as otherwise it is possible to design freely with HTML here. |
| 40 - 42 | Client is started with JavaScript. Some things can be set: |
| 41 | Running the client. In this line startguest.htm and start2.htm differ from each other. See the following chapter for additional information on this topic. |
2.5. Starting visualisation
The HomeServer AjaxVisu is started by calling the file startgast.htm in an
Internet browser:
"https://IP_des_HS/FS/opt/hsav-gira_en/startgast.htm”
There are three call variants which can also be combined with each other:
The possible parameters for the call variants A and B are (in brackets the abbreviation for
the call via Variant B):
"https://IP_des_HS/FS/opt/hsav-gira_en/startgast.htm”
There are three call variants which can also be combined with each other:
- Modification of the included startgast.htm by permanently entering the information.
- Use of parameters, which you add on when calling in the browser
- Neither A. nor B.
Note: The start file can be assigned any desired name.
Of course, any desired name can be assigned to the start file
(startguest.htm). However, you should retain the file ending (.htm) and you should
not use any blank spaces.
- User (user)
- Password (pw)
- Design abbreviation (cl)
- Refresh time (ref)
- Login behaviour (not possible with Variant B)
2.5.1. Call variant A
When using Variant A, the parameters must be placed in single quotation
marks and specified separated from each other with commas. Line 41 in the code
listing.
Here is an example of the call variant A with permanently entered parameters in line 41:
startClientEx('admin','Alpha.123','D1024V','R1',1);
If all information is correct, the HomeServer AjaxVisu starts with the specified visualisation page. Otherwise the Login mask is called.
Here is an example of the call variant A with permanently entered parameters in line 41:
startClientEx('admin','Alpha.123','D1024V','R1',1);
If all information is correct, the HomeServer AjaxVisu starts with the specified visualisation page. Otherwise the Login mask is called.
Note: 5th Parameter.
The 5th parameter can only be modified
here; it does not exist as an call parameter.
Note: Permanently entered parameters are overwritten.
Permanently entered parameters are overwritten by call parameters
(Variant B)!
2.5.2. Call variant B
When using Variant B, a question mark (?) is added onto the file name,
which is then followed by the individual parameters (with abbreviations) each separated by
an ampersand (&). Here is an example of call variant B with call
parameters:
https://192.168.0.51/opt/hsav-gira_en/startgast.htm?pw=admin&user=admin&cl=D1024V&ref=R1
If all information is correct, the HomeServer AjaxVisu starts with the specified visualisation page. Otherwise, the Login mask is called.
https://192.168.0.51/opt/hsav-gira_en/startgast.htm?pw=admin&user=admin&cl=D1024V&ref=R1
If all information is correct, the HomeServer AjaxVisu starts with the specified visualisation page. Otherwise, the Login mask is called.
Note: 5th Parameter.
The 5th parameter can not be
modified here; it does not exist as an call parameter.
Note: Permanently entered parameters are overwritten.
Permanently entered parameters (Variant A) are overwritten by call
parameters!
2.5.3. Call variant C
When using Variant C, the file startgast.htm, is used as described
in the chapter Start files and no parameters are added onto the
call.
The HomeServer AjaxVisu starts with the Login mask.
The HomeServer AjaxVisu starts with the Login mask.
2.5.4. Variant mix
You can also combine the various variants. For example, if you permanently
enter only the design and the refresh rate in the start file, you can include the user
and/or password as call parameters.
You can also permanently enter all information as described in Variant A. If you then also include individual (or all) parameters as call parameters, the permanently entered parameters will be overwritten by the call parameters!
If you have specified all parameters in one or the other form, the HomeServer AjaxVisu starts with the specified page. Otherwise the Login mask is called in which all known fields (except the password) are shown already filled out.
You can also permanently enter all information as described in Variant A. If you then also include individual (or all) parameters as call parameters, the permanently entered parameters will be overwritten by the call parameters!
If you have specified all parameters in one or the other form, the HomeServer AjaxVisu starts with the specified page. Otherwise the Login mask is called in which all known fields (except the password) are shown already filled out.
2.5.5. Cookies
If, as described in Variant A, not all parameters are permanently entered,
the entries from the login are saved and the next time the Login mask is called, the
fields are automatically filled in with this information in advance.
Note: Overwriting parameters.
Permanently entered parameters overwrite the parameters saved in
this way. Call parameters in turn overwrite permanently entered parameters!
2.5.6. Security
As with Variant A the login data are saved unencrypted, we only recommend
only using this variant for users, who only have an internal access authorisation.
Otherwise it is possible for someone to obtain access to this file and misuse the
data.
In general, it is recommended that at least the password not be permanently entered in the start file so that it is not saved in unprotected areas, but is instead requested on each login and each reconnection.
In general, it is recommended that at least the password not be permanently entered in the start file so that it is not saved in unprotected areas, but is instead requested on each login and each reconnection.
2.5.7. QuadClient
For persons commissioning, it is advisable to use Variant B.
In the QuadConfig an entry is structured in the "Navigation button - URL" in such a way that a URL is stored there with call parameters (as described in Variant B). Therefore no critical data is entered in the start file, the user of the QuadClient can, however, nevertheless also log into the visualisation without an additional login procedure in this way.
In the QuadConfig an entry is structured in the "Navigation button - URL" in such a way that a URL is stored there with call parameters (as described in Variant B). Therefore no critical data is entered in the start file, the user of the QuadClient can, however, nevertheless also log into the visualisation without an additional login procedure in this way.
2.5.8. Reconnect and refresh
If the connection to the HS/FS is disconnected, e.g. due to restarting the
HS/FS, a reddish information window with the heading "HomeServer AjaxVisu" and a
note that an attempt is being made to re-establish the disconnected connection are
displayed. This attempt at reconnection is repeated at intervals that are determined by
the refresh time.
A number of asterisks are shown in the information window, each of which stands for a reconnection attempt already carried out.
As soon as the connection has been restored, the information window disappears.
Then the user is on the page again that was active before the connection failed.
Exception: Popup pages. The user is on the page again from which the popup page was called.
A number of asterisks are shown in the information window, each of which stands for a reconnection attempt already carried out.
As soon as the connection has been restored, the information window disappears.
Then the user is on the page again that was active before the connection failed.
Exception: Popup pages. The user is on the page again from which the popup page was called.
2.6. Login mask, fields
The Login mask contains the fields and buttons listed in the following.
The data are created in the Expert software.
Example from the start file: startClientEx('admin','Alpha.123','D1024V','R1',1);
The data are created in the Expert software.
Example from the start file: startClientEx('admin','Alpha.123','D1024V','R1',1);
Important: Rules for user names and passwords
When selecting a user name and password, observe the rules specified in
the online help of the Expert software!
2.6.1. User name
Input field, in the example admin
User name for login to the HomeServer or Facility Server.
This user is assigned the start page in the visualisation.
User name for login to the HomeServer or Facility Server.
This user is assigned the start page in the visualisation.
2.6.2. Password
Input field, in the example Alpha.123
Password for login to the HomeServer or Facility Server.
Password for login to the HomeServer or Facility Server.
2.6.3. Design
Input field (abbreviation), in the example D1024V
Indicates which design or which visualisation page is to be displayed. Otherwise it has no further effect on the HomeServer AjaxVisu.
Indicates which design or which visualisation page is to be displayed. Otherwise it has no further effect on the HomeServer AjaxVisu.
2.6.4. Refresh time
Input field (abbreviation), in the example R1
If a change is brought about with an element in the visualisation, for example a light is switched on, an automatic refresh of the page (the status of the object in question is determined and shown on the visualisation) is carried out at intervals that double each time.
This takes place until a period of time has passed which was entered under the refresh time in the HS/FS Expert.
Example:
5 minutes (= 300 seconds) are entered as a refresh time. Then an automatic refresh is carried out after 2, 4, 8, 16, 32, 64, 128 and 256 seconds.
If a change is brought about with an element in the visualisation, for example a light is switched on, an automatic refresh of the page (the status of the object in question is determined and shown on the visualisation) is carried out at intervals that double each time.
This takes place until a period of time has passed which was entered under the refresh time in the HS/FS Expert.
Example:
5 minutes (= 300 seconds) are entered as a refresh time. Then an automatic refresh is carried out after 2, 4, 8, 16, 32, 64, 128 and 256 seconds.
2.6.5. Save information
Checkbox.
If this checkbox is activated, the user name and password, as well as all other settings are saved on the device as a cookie
If this checkbox is activated, the user name and password, as well as all other settings are saved on the device as a cookie
2.6.6. Login
Button.
By clicking on this button, the user logs in on the HomeServer or FacilityServer with the information previously entered and starts the visualisation following a successful login process.
By clicking on this button, the user logs in on the HomeServer or FacilityServer with the information previously entered and starts the visualisation following a successful login process.
2.6.7. 5th Parameter
There is one additional parameter in the startgast.htm file which,
however, has no input field on the Login mask.
If a connection was terminated, when the connection is restored...
If a connection was terminated, when the connection is restored...
- ... with the value '0' the start page of the visualisation is displayed.
- ... with the value '1' the last page to be displayed prior to the termination is displayed again.
2.7. Installed files
The details of the HomeServer AjaxVisu are described in the following. These
files can be adapted to the user's own needs (colours etc.) with a minimal knowledge of
HTML. The installed files are divided into several sections, each of which can be found in a
separate subdirectory. Sections:
- Graphics files, see ChapterGraphics files..
- Javascript files, see Chapter Javascript files.
- HTML files, see Chapter HTML files.
2.8. Graphics files
The graphics files are stored in the img subdirectory of the hsav-gira_en
folder. The files are used to enable, to prevent or only to display certain actions (e.g.
clicks).
They are expanded or compressed in the horizontal and vertical direction in
accordance with the required area.
The graphics files described in the following can be replaced by you with your own should those contained in the sample project do not appeal to you. They may not simply only be deleted, but rather a file with the corresponding name must always be present!
The graphics files described in the following can be replaced by you with your own should those contained in the sample project do not appeal to you. They may not simply only be deleted, but rather a file with the corresponding name must always be present!
2.8.1. Transparent ".png" files
Internet Explorer in all versions lower than Version 7 does not support
transparent graphics of the type "png".
These graphics are first correctly displayed from Internet Explorer Version 7.
These graphics are first correctly displayed from Internet Explorer Version 7.
2.8.2. Action area for buttons (transparent)
Designation: Ax0.gif
Transparent area, i.e. it has no colour and is therefore 100 percent transparent.
This file is used to to be laid over all visualisation elements defined as clickable. It makes functioning buttons out of purely graphic elements.
Transparent area, i.e. it has no colour and is therefore 100 percent transparent.
This file is used to to be laid over all visualisation elements defined as clickable. It makes functioning buttons out of purely graphic elements.
2.8.3. Click display (red area)
Designation: hide.png
Only partially transparent, red-coloured area, i.e. it is not completely transparent.
This file is used to be laid over a visualisation element for a short time after the user has clicked on it. With it the click is made visible to the user. After one to two seconds the red area disappears again. However, this only occurs in the visualisation; the masks are excluded from this. See also Chapter Start files.
Only partially transparent, red-coloured area, i.e. it is not completely transparent.
This file is used to be laid over a visualisation element for a short time after the user has clicked on it. With it the click is made visible to the user. After one to two seconds the red area disappears again. However, this only occurs in the visualisation; the masks are excluded from this. See also Chapter Start files.
2.8.4. Inactive buttons (white area)
Designation: Hide2.png
Only partially transparent, white-coloured area, i.e. it is not completely transparent.
This file is used, for example, to both display inactive buttons in the masks and to make them inactive for clicking.
Only partially transparent, white-coloured area, i.e. it is not completely transparent.
This file is used, for example, to both display inactive buttons in the masks and to make them inactive for clicking.
2.8.5. No background clicks in masks (grey background)
Designation: Hide3.png
Semi-transparent (grey) full-screen background, which is underlaid after a system mask (e.g. UT, value entry, etc.) is called. This avoids clicks on the background.
Semi-transparent (grey) full-screen background, which is underlaid after a system mask (e.g. UT, value entry, etc.) is called. This avoids clicks on the background.
2.8.6. No background clicks in popups (grey background)
Designation: Hide4.png
Semi-transparent (grey) full-screen background, which is underlaid after a visualisation popup page is called. This avoids clicks on the background.
Semi-transparent (grey) full-screen background, which is underlaid after a visualisation popup page is called. This avoids clicks on the background.
2.8.7. Creating semi-transparent backgrounds
With the Paint.NET program (freeware from Microsoft), semi-transparent
backgrounds can be created for the visualisation. Proceed as follows for this purpose:
- Create new (empty) image
- Mark everything and delete: CTRL-A, DEL
- Select a colour in "Colours" window
- Completely colour everything with "Paint can" tool
- Click on the "Properties" button in the "Levels" window (at the lower edge of the window, on the right)
- Set the opacity as desired in the popup window now displayed
2.9. Javascript files
The Javascript files are stored in the js subdirectory of the hsav-gira_en
folder.
The files are used to breathe life into the HTML files, as it were. These files
contain the program code which, for example, turns a drawn button or the transparent area
which lies over it into a button that actually reacts to clicking.
The file currently used is called ajax.js.
The file currently used is called ajax.js.
2.10. HTML files
The HTML files are stored in the tpl subdirectory of the
hsav-gira_en folder.
These files define the appearance of the predefined visualisation masks. With
them the System Integrator can make his/her own adjustments to the mask design.
Note: Changed entry option.
The Graph and Camera masks are not required (any longer) in the
HomeServer AjaxVisu, as the same thing and even more in a larger range of variations
can be achieved via embedding in the visualisation area.
Note: Changed entry option.
Some masks of the universal time clock are no longer required in the
HomeServer AjaxVisu, as use has changed compared to the default view. The complete
functionality has nevertheless been retained.