Lampix Apps API
  • Introduction
  • Application Development
    • Getting Started
      • Up and Running
      • Boilerplate
    • Step by step app
      • What We'll Build
      • Environment Setup
      • Styling
      • HTML Structure
      • NeuralNetworkClassifier
      • MovementBasedSegmenter
      • Final Step
      • Extras
    • LampixJS
      • API Reference
        • Watcher
        • RegisteredWatcher
        • .watchers.add
        • .watchers.remove
        • .watchers.pauseAll
        • .watchers.resumeAll
        • .presets.button
        • .helpers.rectangle
        • getLampixInfo
        • switchToApp
        • exit
        • getApps
        • getAppConfig
        • getAppMetadata
        • writeJsonToFile
        • readJsonFromFile
        • transformRectCoords
        • constants
      • Examples
        • NeuralNetworkClassifier: Buttons
        • MovementBasedSegmenter
        • Counter App
      • Migrating from v0.x.x to v1.0.0-beta.x
      • Ecosystem
    • Deploying
      • Application Structure (production)
      • Local Deploy
    • Standard Watchers
    • Custom Watchers
      • Description
      • Environment Setup
      • Directory Structure
      • End result
      • QRCodeDetector implementation
    • Community
  • Lampix Simulator
    • Installation
    • Usage
      • Basics
Powered by GitBook
On this page
  • Terminology
  • Accepted protocols
  • file:
  • http(s):
  • simulator: (experimental)
  • Selecting watchers and the recognized class

Was this helpful?

  1. Lampix Simulator
  2. Usage

Basics

PreviousUsage

Last updated 6 years ago

Was this helpful?

Terminology

  • simulator is used to refer to the main window (the one with the address bar for loading applications)

  • simulation is used to refer to a simulated application's window

Accepted protocols

  • used to load local files

  • can be used via the address bar manually

  • can be used by dragging and dropping either a folder with index.html in it or an HTML file in the main simulator interface

  • writeJsonToFile writes in the same directory as the loaded HTML file

Notes

Since localStorage data is isolated on a per origin basis AND the origin of all URLs using the file: protocol is file://, data separation cannot be achieved with this protocol. If this is a concern for you, use instead.

Example

file:///home/username/project/super-app/index.html file:///d:/super-app/index.html

  • used to load served web applications (it doesn't matter whether the server is local or remote)

  • can be used via the address bar manually

Example

http://localhost:3000 https://super.remote.app

Notes

Examples

simulator://super-app simulator://super-duper-app

Selecting watchers and the recognized class

  1. In the simulator, open the expansion panel in the middle that says Simulator <your-url>

  2. Select the watcher name

  3. Select the recognized class

  4. In the simulation, click inside the area of a matching registered watcher

writeJsonToFile writes in the directory, in a folder called webapps-data

serves applications in the webapps folder found in the directory

writeJsonToFile writes in the directory, in a folder called webapps-data

Though simulator: URLs resemble URLs, these do benefit from separation of localStorage data (as the origin is determined to be simulator://app-name).

user data
user data
user data
file:
the http protocol
http(s):
simulator: (experimental)
file: