EPadLink ePad Vision Bedienungsanleitung Seite 5

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 27
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 4
5 www.epadlink.com
Integration Guide (ePad-vision SDK for Chrome & Firefox)
2.1 Chrome Browser
Chrome supports access to local devices (signature pads) using native applications,(Native Messaging
Hosts) and standard extensions. Web pages can interact with native applications via extensions.
2.1.1 Native Messaging Host Application
The Native Messaging Host is the core component of the SDK and acts as a bridge between the
browser and the actual signature capture device. It will have all the input and output interfaces
implemented as Standard Input and Output streams as required by the Google Native Messaging API
framework. The Native Messaging Host Application processes the input text message from the Chrome
browser and executes the request asynchronously, and when the task is complete sends back the
status or output data (signature points and widget events) as a native output text message. It will host
all the functions for capture of signatures and creation of custom screens on the ePad-vision device.
Chrome runs this application in a separate process and launches it through Connect APIs and sends a
notification back to the Chrome Extension when the application is ended by the user.
2.1.2 Chrome Extension/web page
Extensions are the HTML, JavaScript, and CSS based applications. The extensions use JavaScript
based Native Messaging APIs to launch and communicate with the Topaz Native Messaging Host
application for signature capture and other relevant features. The extension listens for the output
messages from the Native Messaging Host Application and processes them accordingly. Native
Messaging has a Connect API to launch the application and a Disconnect event to let the web page
know about termination of the native host application. Using Connect and Disconnect, the life cycle of
the native host application can be controlled.
2.2 Firefox Browser
Firefox supports access to local devices (signature pads) using JS-Ctypes framework. The JS-Ctypes
framework allows Firefox extensions to invoke native C/C++ libraries.
2.2.1 JS-Ctypes library
The JS-Ctype library is the core component of the SDK and acts as a bridge between the browser and
the actual signature capture device. It will have all the methods implemented as required by the Firefox
JS-Ctypes API framework. The library takes all the input data as JSON string messages (same as
Chrome NMH input messages) from the Firefox browser and executes the request synchronously, and
when the task is complete sends back the status method return parameter.
2.2.2 Firefox Extension/web page
Extensions are the HTML, JavaScript, and CSS based applications. The extensions use JavaScript
APIs to launch and communicate with the Topaz JS-Ctypes library for signature capture and other
relevant features. The extension polls for the signature and widget events from the library and
processes them accordingly.
The host application will host all the functions for capture of signatures and creation of custom screens
on the ePad-vision device. Firefox runs this application in the same process.
Seitenansicht 4
1 2 3 4 5 6 7 8 9 10 ... 26 27

Kommentare zu diesen Handbüchern

Keine Kommentare