Glossary
Distinguish source, runtime files, delivery packages, and the three development tools.
Terminology#
| Name | Meaning |
|---|---|
| GlassSDK | Glasses C plugin SDK: headers, examples, build tools, and GMP packaging. |
| PhoneSDK | Phone Web plugin SDK: JavaScript Bridge, examples, and MMPKG packaging. |
| Desktop Studio | Development tool that loads Web and GMP components and generates combined ZIPs and LAN QR codes. |
| Browser Studio | An auxiliary browser previewer in PhoneSDK; it does not execute GMP. |
| Host API | Function table supplied by glasses firmware to C plugins, starting at gm_plugin.h. |
| Bridge | SDK interface for Web pages to communicate with App/Studio hosts. |
| GMP | Glasses plugin image compiled from C source. |
| MMPKG | Packages containing Web manifest, pages, scripts and static resources. |
| Device-test ZIP | Complete Studio-generated file for QR download, installation, and device retesting. |
| LAN / local area network | The computer-to-phone download path used during scanning. |
| BT / Bluetooth | The App-to-glasses installation and business path, carrying only required runtime data. |
| Source-build attachments | Encrypted glasses source code snapshot and associated metadata, not participating in glasses execution. |
| ABI | The binary interface contract between the glasses Host and GMP. |
| manifest | Declarations for component name, identity, version, entry, permissions, and pairing. |