aiden/VR-Web-Player
1
0
Fork 0
forked from EXT/VR180-Web-Player
Code Actions Activity

deploy update
Some checks failed
Publish Pages / publish (push) Failing after 4s
Details
Test / test (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Aiden
2026-06-11 16:07:10 +10:00
parent c86490542d
commit 469dc81491
2 changed files with 11 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.gitea/workflows/publish-pages.yml
View File

@@ -8,6 +8,8 @@ on:
jobs: jobs:
publish: publish:
runs-on: ubuntu-latest runs-on: ubuntu-latest
container:
image: node:22-bookworm
env: env:
R2_ENDPOINT: https://${{ secrets.F40_PAGES_R2_ACCOUNT_ID }}.r2.cloudflarestorage.com R2_ENDPOINT: https://${{ secrets.F40_PAGES_R2_ACCOUNT_ID }}.r2.cloudflarestorage.com
R2_ACCOUNT_ID: ${{ secrets.F40_PAGES_R2_ACCOUNT_ID }} R2_ACCOUNT_ID: ${{ secrets.F40_PAGES_R2_ACCOUNT_ID }}
@@ -21,10 +23,6 @@ jobs:
steps: steps:
- uses: actions/checkout@v4 - uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 22
- name: Resolve settings - name: Resolve settings
run: | run: |
SITE_NAME="${SITE_NAME_OVERRIDE:-${GITHUB_REPOSITORY##*/}}" SITE_NAME="${SITE_NAME_OVERRIDE:-${GITHUB_REPOSITORY##*/}}"

10
README.md
View File

@@ -9,6 +9,12 @@ The player supports two projection modes:
## How to use it ## How to use it
Build the player first, then host the generated `vr180player/` directory on your CDN and include the module script. The script automatically loads its matching CSS file from the same folder, and it imports its helper modules with relative module paths. Build the player first, then host the generated `vr180player/` directory on your CDN and include the module script. The script automatically loads its matching CSS file from the same folder, and it imports its helper modules with relative module paths.
Current F40 Pages CDN entrypoint:
```html
<script type="module" src="https://pages.f-40.com/VR-Web-Player/vr180player/vr180-player.js"></script>
```
```html ```html
<button <button
type="button" type="button"
@@ -21,7 +27,7 @@ Build the player first, then host the generated `vr180player/` directory on your
<img src="temple-thumb.jpg" alt="Temple Hall"> <img src="temple-thumb.jpg" alt="Temple Hall">
</button> </button>
<script type="module" src="https://cdn.example.com/vr180player/vr180-player.js"></script> <script type="module" src="https://pages.f-40.com/VR-Web-Player/vr180player/vr180-player.js"></script>
``` ```
A page can contain any number of launchers. Each launcher represents one SBS media item. A launcher click goes straight into immersive WebXR when `immersive-vr` is supported. When immersive WebXR is unavailable, the same click opens a modal with the left-eye fallback view. A page can contain any number of launchers. Each launcher represents one SBS media item. A launcher click goes straight into immersive WebXR when `immersive-vr` is supported. When immersive WebXR is unavailable, the same click opens a modal with the left-eye fallback view.
@@ -96,6 +102,8 @@ When the page loads, the script binds every `[data-vr-web-launcher]` on the page
## Demo ## Demo
Run `npm run build`, then open `test-pages/index.html` through a local web server. The test hub has three options: a local file picker for browser-selected image/video media, one bundled SBS flat 3D image, and one bundled SBS VR180 image. Run `npm run build`, then open `test-pages/index.html` through a local web server. The test hub has three options: a local file picker for browser-selected image/video media, one bundled SBS flat 3D image, and one bundled SBS VR180 image.
The deployed test app is expected at `https://pages.f-40.com/VR-Web-Player/` once the F40 Pages workflow has published a release.
For local experimentation, run: For local experimentation, run:
```sh ```sh