Creating adapters for Google Chrome and Mozilla Firefox
The add-in adapter for Chrome and Firefox is a console application. During the installation it registers one or several unique extension types. We recommend that you begin extension names with "com." and include the add-in version numbers in them (for example, com.YourCompanyName.YourAddInName.1). When you release a new add-in version, increment the version number in its name, otherwise the web client will use the old version of the add-in.
For example, an add-in with name com.YourCompanyName.YourAddInName.3 is used in a configuration. When you release a new add-in version, to include it in the configuration, rebuild the Chrome adapter with name changed to com.YourCompanyName.YourAddInName.4. Then rebuild the installation packages and include them in the archive that will be loaded to the configuration. Also, in the archive manifest file, change the name to com.YourCompanyName.YourAddInName.4. Then load the archive to the configuration. When the web client is started with the new configuration on the computer where the previous add-in version is installed, the web client retrieves the name com.YourCompanyName.YourAddInName.4 from the configuration. Since this name is not registered in the browser, the previous add-in version will not be used. To start using the new add-in version, the user must install it. The previous add-in version remains installed and can be used with earlier configuration versions.
Use the AddInChrome project from the example directory as a basis for add-in development. In the config.cpp file, change the values of the following variables: nameFilePrj and nameFileComponent. The nameFilePrj variable contains the adapter file name (for example, AddInChrWin32.exe). The nameFileComponent variable contains the add-in file name (for example, AddInNative.dll).
The adapters are based on the jsoncpp library (view license).