@brftech/filex-app-ui 0.48.1 → 0.50.0

package/README.md

@@ -5,7 +5,7 @@ The SDK an app's own interface bundles to talk to [filex](https://github.com/BRF
 An app may bring its own HTML/JS/CSS interface. filex serves it from the app's
 approved package and runs it in a sandboxed frame whose policy allows no
 connection, no storage and no cookie (a browser cannot fully stop a page
-sending data out — see filex's APP-PLUGINS.md). Everything the interface does
+sending data out - see filex's APP-PLUGINS.md). Everything the interface does
 goes through filex over one checked channel, and this package is that channel: a few KB, no dependency.
 
 ```bash
@@ -30,10 +30,10 @@ with a `<script src>`: it defines `window.FilexAppUI.connect`.
 | `fx.session` | the app and view, the reader's language and direction, filex's colours, the person's display name, the files, the grants |
 | `fx.open(i)` / `fx.save(data)` / `fx.saveAs(name, data)` | read an opened file; save over it (a new version, or the draft it is); save a new file where the person picks |
 | `fx.dirty(on)`, `fx.title(t)`, `fx.toast(t, tone)`, `fx.confirm(opts)`, `fx.close()` | tell filex about unsaved changes; ask filex to draw a line, a question, to close (a toast and a question carry your app's name) |
-| `fx.copy(text)` | put text on the clipboard — call it from a click or a key press: without one, filex asks the person first |
-| `fx.download(name, data, mime?)` | hand the person a file for their own disk (`"ui": { "download": true }` in the manifest) — from a click, or filex asks; 256 MiB at most; Chromium streams it into the file they pick |
+| `fx.copy(text)` | put text on the clipboard - call it from a click or a key press: without one, filex asks the person first |
+| `fx.download(name, data, mime?)` | hand the person a file for their own disk (`"ui": { "download": true }` in the manifest) - from a click, or filex asks; 256 MiB at most; Chromium streams it into the file they pick |
 | `fx.call(method, params)` | ask the app's own module (`ui_call`) |
-| `fx.submit(action, params)` | queue one of the app's actions on the opened files — like `copy`, from a click, or filex asks |
+| `fx.submit(action, params)` | queue one of the app's actions on the opened files - like `copy`, from a click, or filex asks |
 | `fx.state.get(key)` / `fx.state.set(key, value)` | a small store for this app and this person |
 | `fx.on('theme' \| 'locale' \| 'file.changed' \| 'close.request' \| 'app.updated', fn)` | listen to filex |
 
@@ -41,7 +41,7 @@ with a `<script src>`: it defines `window.FilexAppUI.connect`.
 and `data-theme` onto `<html>` and keeps them current; pass
 `{ applyTheme: false }` to do it yourself.
 
-The whole contract — manifest, serving policy, every message — is
+The whole contract - manifest, serving policy, every message - is
 `docs/APP-PLUGINS-API.md` → "An app's own interface"; how to build and package
 an interface is `docs/PLUGIN-KIT.md` → "Writing an interface". The protocol
 itself is `src/protocol.ts` (also exported as `@brftech/filex-app-ui/protocol`),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brftech/filex-app-ui",
-  "version": "0.48.1",
+  "version": "0.50.0",
   "description": "filex app interface SDK: the bridge between an app's own sandboxed interface and filex (open, save, dirty, call the app's module)",
   "type": "module",
   "main": "./dist/filex-app-ui.js",