@coasys/ad4m-connect
v0.10.0-rc7.local-ai.4
Published
Lib for handling everything needed to setup a connection to a local or remote ad4m-executor
Downloads
226
Keywords
Readme
AD4M connection library and wizard for apps
This package makes it easy for AD4M apps to connect to a local or remote AD4M executor by handling all the complex things like finding the local executor port, requesting and storing a capability token, creating and recreating an Ad4mClient.
Installation
npm install -s @coasys/ad4m-connect
Properties
appName(required)
: Name of the application using ad4m-connect.appDesc(required)
: Description of the application using ad4m-connect.appDomain(required)
: Domain of the application using ad4m-connect.capabilities(required)
: Capabilities requested by the application.appIconPath
: Icon for the app using ad4m-connect.port
: Port that AD4M is running on.token
: JWT token if you have one.url
: The url that we should connect to.
Events
authstatechange
:authenticated
|unauthenticated
|locked
connectionstatechange
:connecting
|connected
|not_connected
|disconnected
|error
;configstatechange
:token
|url
|port
In the Browser
import Ad4mConnectUI from "@coasys/ad4m-connect";
const ui = Ad4mConnect({
appName: "Example",
appDesc: "This is a sample app.",
appDomain: "ad4m.dev",
appIconPath: "https://i.ibb.co/GnqjPJP/icon.png",
capabilities: [{ with: { domain: "*", pointers: ["*"] }, can: ["*"] }],
});
ui.addEventListener("authstatechange", (e) => {
if (e.detail === "authenticated") {
// We are authenticated
}
});
// Open popup and save the client when we are done
ui.connect().then((client) => {
// Save the client
});
Usage (from Node / Electron)
Call ad4mConnect with parameters of your app:
const { ad4mConnect } = require("@coasys/ad4m-connect/electron");
ad4mConnect({
// Provide the name of your app to be displayed in the dialog
appName: "Perspect3ve",
// Provide an icon to be displayed in the dialog as well
appIconPath: path.join(__dirname, "graphics", "Logo.png"),
// Name the capabilities your app needs
// (this is an example with all capabilities)
capabilities: [{ with: { domain: "*", pointers: ["*"] }, can: ["*"] }],
// Provide a directory in which the capability token and the executor
// URL will be stored such that future calls won't even open a dialog
// but try the token against that URL and resolve immediately
// if it works.
dataPath: path.join(homedir(), ".perspect3ve"),
})
.then(({ client, capabilityToken, executorUrl }) => {
// Retrieved `capabilityToken` and selected `executorUrl` are returned
// but all that is really needed is `client` which is a fully setup
// (including capability token) and working Ad4mClient.
//
// Both, the URL and the token have already been stored on disk
// in the directory provided as `dataPath`.
//
// Consequetive calls
createWindow(client);
})
.catch(() => {
console.log("User closed AD4M connection wizard. Exiting...");
app.exit(0);
process.exit(0);
});
Extra steps to be used in capacitor:
- On Android
<?xml version="1.0" encoding="utf-8"?>
<manifest
xmlns:android="http://schemas.android.com/apk/res/android"
+ xmlns:tools="http://schemas.android.com/tools"
package="com.example">
<application
+ android:hardwareAccelerated="true"
>
</application>
+ <uses-permission android:name="android.permission.CAMERA" />
+ <uses-sdk tools:overrideLibrary="com.google.zxing.client.android" />
</manifest>
- On IOs
<dict>
+ <key>NSCameraUsageDescription</key>
+ <string>To be able to scan barcodes</string>
</dict>
- Then run
npx cap sync
&npx cap build