Preparing add-ins for working with the web client

Add-ins interact with the web client using extensions. Projects for creating Mozilla Firefox, Google Chrome, Internet Explorer, and Safari extensions are provided in the examples. For security reasons, each extension can work with a single add-in specified at the compilation stage. Each extension consists of an add-in (possibly created using the COM technology) and a browser adapter.

For Microsoft Windows and Mac OS X operating systems, all executable files included in the installer package and the installer package itself must be signed with the developer's digital signature. For Microsoft Windows installer packages, dual signing (SHA-1 and SHA-256) is required, with the exception of MSI packages (see the Microsoft recommendation).

The browser script language is single-threaded. Therefore, you have to avoid callbacks from secondary add-in threads. Only the following methods will work in secondary threads: ExternalEvent(), SetStatusLine(), and ResetStatusLine().

Libraries of Windows browsers use the Visual Studio 2013 compiler.

On platform versions 8.3.6 and later, Firefox and Google Chrome use the same adapter.

Add comment