EPadLink ePad Vision Manuel d'utilisateur télécharger pdf (Page 10)

10 www.epadlink.com

Integration Guide (ePad-vision SDK for Chrome & Firefox)

installed/copied. If the executable and the manifest file are in same

location, the name itself will do. If absolute or relative paths are

specified, please make sure to enter ‘\\’ as the folder separator. Adjust

the paths as needed for Windows and Linux operating systems.

Type

Type of the interface used to communicate with the native messaging

host. Currently there is only one possible value for this

parameter: stdio. It indicates that Chrome should use

stdin and stdout to communicate with the host.

allowed_origins

List of extensions that should have access to the native messaging

host. Normally specifies the extensions from which the host can be

accessed. Supports specifying multiple extension IDs. The default

manifest file shipped with the SDK contains the IDs of the sample

extensions that are shipped with the SDK. These should be changed

appropriately if custom extensions are developed. Extension ID can be

grabbed from Chrome://Extensions page once the extension is

deployed. Use the extension ID copied in Extension installation section.

Once the editing of the manifest file is completed, the next step would be to register the host application

with the Chrome Browser.

7.3.1 – Windows

For 32 bit and 64 bit operating systems running respective Chrome browsers (32 and 64 bit versions)

the following registry key should be created. The manifest file can be located anywhere in the file

system.

Create a registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\NativeMessagingHosts\

com.topaz.epadvision.win

For 64 bit operating systems running 32 bit Chrome the following key should be created in the

registry.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Chrome\NativeMessagingHosts\

com.topaz.epadvision.win

Once the key is created, set the default value of that key to the full path of the manifest file.

Now the host application is ready for access from the specified extensions.

For 32 bit Chrome it is recommended to enter the X86 version of manifest file path located

under

<SDK_location>\SDK\ Chrome-NativeMessagingHost\Windows\X86\manifest.json

For 64 bit Chrome it is recommended to enter the X64 version of manifest file path located

under

<SDK_location>\SDK\ Chrome-NativeMessagingHost\Windows\X64\manifest.json

1 2 ... 5 6 7 8 9 10 11 12 13 14 15 ... 26 27

Pas de commentaire

EPadLink ePad Vision Manuel d'utilisateur Page 10