Glue42 Web allows JavasScript applications to integrate with other applications, part of the same Glue42 Core project via a set of APIs. With Glue42 Web you can share data with other applications, expose functionality, manage windows and notifications.
<script> tag, and as a node.js module.
You can use Glue42 Web in a
script tag include, e.g.:
Object used to turn on or off the applications auto-save and auto-restore functionality
Whether to initialize the Channels API or not.
Whether to initialize the Application Manager API or not.
Application name. If not specified the Application Manager API won’t know about the application and its instances.
todo: An object exposing settings related to the Glue42 Core resources.
() => Promise<void>
Disposes Glue42 API. This will remove all Interop methods and streams registered by the application.
Brings up the Glue42 Desktop feedback dialog.
Info object containing versions of all included libraries and Glue42 itself.
If true, the set of windows opened by the application will be saved (in local storage) when the window is closed and restored when the window is started again. The data saved about each window includes URL, bounds and custom window context. It will also save and restore the window context of the current window.
If set to
true, will return glue.windows.my().context automatically when asked for layout state.
This defines the location of the Glue42 Core assets bundle (glue.layouts.json, glue.config.json, workspaces app and more).
If set to true the initialization logic will fetch the glue.config.json and use the defined glue object there to extend the provided config. We recommend setting this to false if you do not have a glue.config.json.