diff options
Diffstat (limited to 'packages/meshbay-android/app/src/main/assets')
| -rw-r--r-- | packages/meshbay-android/app/src/main/assets/bridge/meshbay-bridge.js | 20 |
1 files changed, 2 insertions, 18 deletions
diff --git a/packages/meshbay-android/app/src/main/assets/bridge/meshbay-bridge.js b/packages/meshbay-android/app/src/main/assets/bridge/meshbay-bridge.js index a07399f..d829df3 100644 --- a/packages/meshbay-android/app/src/main/assets/bridge/meshbay-bridge.js +++ b/packages/meshbay-android/app/src/main/assets/bridge/meshbay-bridge.js @@ -15,12 +15,11 @@ * that refuses: `platform.js` decides what to show from whether an object * exists (`platform.node.available`, `platform.folder.available`, …). * - * `HUB_BASE`, `BINARY`, `CAST`, `BACKUP` and `MESSAGES` are prepended by the + * `HUB_BASE`, `BINARY`, `CAST` and `BACKUP` are prepended by the * shell when it injects this file: the interface asks for the hub while its * modules load, before anything can await; BINARY says whether the WebView carries ArrayBuffer * messages; CAST whether this device can cast at all; BACKUP whether this is - * the personal profile, the only one backed up; MESSAGES whether this build - * backs text messages up (not the Play build). + * the personal profile, the only one backed up. */ (function () { 'use strict'; @@ -238,7 +237,6 @@ sent: (token, dir, name) => call('contactsync:sent', token, dir, name), completed: () => call('contactsync:completed'), failed: (code, text) => call('contactsync:failed', code, text), - openSettings: () => call('contactsync:open-settings'), }, // Calendar backup (§9.13), the same way: one iCalendar file of every @@ -251,7 +249,6 @@ sent: (token, dir, name) => call('calendarsync:sent', token, dir, name), completed: () => call('calendarsync:completed'), failed: (code, text) => call('calendarsync:failed', code, text), - openSettings: () => call('calendarsync:open-settings'), }, // Files backup (§9.13): folders the person chose through the system's @@ -287,19 +284,6 @@ }, } : {}), - // Messages backup (§9.13), the same way as contacts: the messages added - // since the last file the node took. Only in a build that may read them. - ...(MESSAGES ? { messageSync: { - status: () => call('messagesync:status'), - permit: () => call('messagesync:permit'), - configure: (settings) => call('messagesync:configure', settings || null), - plan: () => call('messagesync:plan'), - sent: (token, dir, name) => call('messagesync:sent', token, dir, name), - completed: () => call('messagesync:completed'), - failed: (code, text) => call('messagesync:failed', code, text), - openSettings: () => call('messagesync:open-settings'), - } } : {}), - // Where downloads go, chosen once. A display name comes back, never a URI. folder: { choose: () => call('folder:choose'), |