So as the PmaPanel object would offer its image into the Web server, it is necessary to check the "Enable as Web component" configurator on the "Web server" tab and to fill in all other configurators on this tab correctly.
The client requiring data from this Web component is of the PmWebClient type from the licence point of view.
Since the version Pm8.2.0 the HTML pages generated by the system were transformed to standard HTML5 technologies so these can be displayed in alternative browsers (Chrome, Firefox, Edge, InternetExplorer ...) including their mobile versions.
Up to the version PROMOTIC Pm8.2 the HTML pages generated by the system were designed only for InternetExplorer.
The main restriction is that it is unable to access directly in the script to other objects in the tree of Pma objects, for example access for values in the PmaData object (this restriction is valid for scripts - not for example in the "PP - Data binding to Pma object property" data binding - it can use references to other objects).
This limitation can be solved, by calling for example panel the method (i.e. in Pmg object event) pMe.PmPanel.Methods.XXX(a,b,..). This calling the "XXX" method makes the client send XML command to server and so the method is called on the server. In this panel method the script can be present, accessing other objects in the tree of Pma objects. For additional info see more.
The "Type" configurator with "Selection and edit" setting is not functional for the Web so far.
Called methods can have parameters and an output value (pResult) only:
A panel (created in the PmaPanel object) can be opened directly in the runtime application (local panel) or in the Web browser (Web panel). If in such panel calling an algorithm is needed (for example after pressing the button), which has to do something different in local panel than in the Web panel, then it is recommended to use the PmgRoot.ClientType property. The value of this property informs, whether the panel is opened in the application or in the Web browser. Examples see description of the ClientType property.
When developing a Web panel, it is necessary to understand, that, multiple clients can see it simultaneously. So it is a bad idea for example to create one panel (one PmaPanel object) able to display multiple devices according to a variable set in the application. In such case the clients would be rewriting this global variable mutually and see incorrect values as a consequence. If one panel displaying various data is needed, then the best way to do so, is:
Ther ActiveX objects are not functional.