feat(worker): support pattern marker loading in worker and plugin helper

[Copilot]

Implementation plan for pattern marker loading in worker and plugin integration:

• Update src/worker/worker.js to handle 'loadMarker' messages
  • Add arController.loadMarker() and arController.trackPatternMarkerId() calls
  • Send back 'loadMarkerResult' messages with ok:true/false
  • Ensure arController is initialized before loading
  • Add logging for marker loading operations
  • Keep Node worker fallback support
  • Fix CORS error by checking environment before importing node:worker_threads
• Update src/plugin.js to expose ArtoolkitPlugin.loadMarker() method
  • Add loadMarker(patternUrl, size) method that sends 'loadMarker' message
  • Return Promise that resolves when 'loadMarkerResult' is received
  • Handle 'loadMarkerResult' messages in _onWorkerMessage
• Create examples/simple-marker directory and files
  • Create examples/simple-marker/index.html
  • Add plugin.loadMarker() call after worker ready
  • Create examples/simple-marker/data/patt.hiro file
  • Create examples/simple-marker/README.md with instructions
• Test and validate changes
  • Ensure tests pass
  • Verify worker message handling
  • Fix browser CORS issues

Summary

Successfully implemented pattern marker loading support in worker and plugin integration.

Changed Files:

• src/worker/worker.js - Added loadMarker message handler with ARController initialization, fixed CORS error
• src/plugin.js - Added loadMarker() method with Promise-based API
• examples/simple-marker/index.html - Interactive example demonstrating marker loading
• examples/simple-marker/data/patt.hiro - Placeholder pattern file
• examples/simple-marker/README.md - Setup and usage instructions

Key Features:

• Worker accepts 'loadMarker' messages and calls arController.loadMarker(patternUrl)
• Plugin exposes loadMarker(patternUrl, size) helper method returning a Promise
• Automatic ARController initialization with default dimensions if not initialized
• Comprehensive logging throughout the marker loading pipeline
• Node worker_threads compatibility maintained
• Browser environment properly detected to prevent CORS errors

Latest Fix:

Fixed CORS policy violation by checking environment (typeof self === 'undefined') before attempting to import node:worker_threads. The worker now only tries to import Node.js modules when actually running in a Node.js environment.

Draft PR: #5

Original prompt

Implement pattern marker loading in worker and plugin integration:

Changes to make on branch copilot/integrate-artoolkit-wasm (create branch from copilot/scaffold-artoolkit if not present):

1. Update src/worker/worker.js to add handling for 'loadMarker' messages: call arController.loadMarker(patternUrl) and arController.trackPatternMarkerId(markerId, size), and send back 'loadMarkerResult' messages with ok:true/false. Keep Node fallback. Ensure arController is initialized (initArtoolkit) before loading; if not, initialize with default dimensions. Add logging.

2. Update src/plugin.js to expose a helper method ArtoolkitPlugin.loadMarker(patternUrl, size) that sends a 'loadMarker' message to the worker and returns a Promise resolving when 'loadMarkerResult' is received. Also ensure detectionResult payloads are logged (already done).

3. Update examples/simple-marker/index.html to call plugin.loadMarker('/examples/simple-marker/data/patt.hiro', 1) after worker ready, and include a sample patt.hiro file path in README.

4. Add examples/simple-marker/data/patt.hiro placeholder file (or note) and update examples/simple-marker/README.md with instructions.

Notes:

• The worker must accept absolute or repo-relative URLs for pattern files; recommend using absolute URL path from example page.
• Keep PR as draft and title: "feat(worker): support pattern marker loading in worker and plugin helper". In PR body include changed files and setup instructions.

Ensure all modified files are committed and pushed to new branch copilot/integrate-artoolkit-wasm and open draft PR against main.

Please create the PR and return the PR URL and list of changed files.

This pull request was created as a result of the following prompt from Copilot chat.

Implement pattern marker loading in worker and plugin integration:

Changes to make on branch copilot/integrate-artoolkit-wasm (create branch from copilot/scaffold-artoolkit if not present):

1. Update src/worker/worker.js to add handling for 'loadMarker' messages: call arController.loadMarker(patternUrl) and arController.trackPatternMarkerId(markerId, size), and send back 'loadMarkerResult' messages with ok:true/false. Keep Node fallback. Ensure arController is initialized (initArtoolkit) before loading; if not, initialize with default dimensions. Add logging.

2. Update src/plugin.js to expose a helper method ArtoolkitPlugin.loadMarker(patternUrl, size) that sends a 'loadMarker' message to the worker and returns a Promise resolving when 'loadMarkerResult' is received. Also ensure detectionResult payloads are logged (already done).

3. Update examples/simple-marker/index.html to call plugin.loadMarker('/examples/simple-marker/data/patt.hiro', 1) after worker ready, and include a sample patt.hiro file path in README.

4. Add examples/simple-marker/data/patt.hiro placeholder file (or note) and update examples/simple-marker/README.md with instructions.

Notes:

• The worker must accept absolute or repo-relative URLs for pattern files; recommend using absolute URL path from example page.
• Keep PR as draft and title: "feat(worker): support pattern marker loading in worker and plugin helper". In PR body include changed files and setup instructions.

Ensure all modified files are committed and pushed to new branch copilot/integrate-artoolkit-wasm and open draft PR against main.

Please create the PR and return the PR URL and list of changed files.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[kalwalt]

@copilot Creating ArtoolkitPlugin instance...
index.html:77 Initializing plugin...
index.html:77 Enabling plugin...
index.html:77 EventBus: Subscribed to engine:update
index.html:77 EventBus: Subscribed to ar:workerReady
index.html:77 EventBus: Subscribed to ar:markerFound
index.html:77 EventBus: Subscribed to ar:markerUpdated
index.html:77 EventBus: Subscribed to ar:markerLost
Access to script at 'node:worker_threads' from origin 'http://localhost:63343' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: chrome, chrome-extension, chrome-untrusted, data, http, https, isolated-app.Understand this error
index.html:1 Access to script at 'node:worker_threads' from origin 'http://localhost:63343' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: chrome, chrome-extension, chrome-untrusted, data, http, https, isolated-app.Understand this error

[Copilot]

@copilot Creating ArtoolkitPlugin instance...
index.html:77 Initializing plugin...
index.html:77 Enabling plugin......

Fixed in 372de54. The CORS error was caused by attempting to import node:worker_threads in the browser. Now checking for Node.js environment (typeof self === 'undefined') before attempting the import, so browser workers skip the Node-specific code entirely.

[kalwalt]

@copilot now it can be loaded: [2025-11-02T00:15:58.322Z] Creating ArtoolkitPlugin instance...
[2025-11-02T00:15:58.322Z] Initializing plugin...
[2025-11-02T00:15:58.322Z] Enabling plugin...
[2025-11-02T00:15:58.322Z] EventBus: Subscribed to engine:update
[2025-11-02T00:15:58.323Z] EventBus: Subscribed to ar:workerReady
[2025-11-02T00:15:58.323Z] EventBus: Subscribed to ar:markerFound
[2025-11-02T00:15:58.323Z] EventBus: Subscribed to ar:markerUpdated
[2025-11-02T00:15:58.323Z] EventBus: Subscribed to ar:markerLost
[2025-11-02T00:15:58.410Z] EventBus: Event 'ar:workerReady' emitted with data: {}
[2025-11-02T00:15:58.411Z] Worker is ready!
[2025-11-02T00:16:02.258Z] Calling plugin.loadMarker()...
[2025-11-02T00:16:02.329Z] Marker loaded successfully! ID: 119, Size: 1