https://github.com/graysonhicks/vrworkplace
Explore different workplaces with ReactVR, and find hotspots to learn more about them.
https://github.com/graysonhicks/vrworkplace
gh-pages react react-vr reactvr vr webvr
Last synced: 10 months ago
JSON representation
Explore different workplaces with ReactVR, and find hotspots to learn more about them.
- Host: GitHub
- URL: https://github.com/graysonhicks/vrworkplace
- Owner: graysonhicks
- Created: 2017-04-20T11:52:13.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2017-06-01T14:23:24.000Z (over 8 years ago)
- Last Synced: 2025-01-29T12:24:20.653Z (12 months ago)
- Topics: gh-pages, react, react-vr, reactvr, vr, webvr
- Language: JavaScript
- Homepage: https://graysonhicks.github.io/vrWorkplace/
- Size: 108 MB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# vrWorkplace
## A Simple VR App To Explore Different Work Environments
## Use
- Choose a workplace from the main menu
- discover 'hotpoints' around workplace and click to learn more
### For deployment
- on `master` branch, `npm run bundle` to build prod bundles in `/build` folder
- the `static_assets/` folder must be copied down in `build/` folder
- `index.html` is not built by this command, so existing `vr/index.html` must be placed down in `/build` folder
- now paths must be changed in the `build/index.html` file to point to the prod bundles instead of dev js
- `` becomes ``
- `ReactVR.init('../index.vr.bundle?platform=vr&dev=true',document.body);` becomes `ReactVR.init('./index.bundle.js?platform=vr', document.body);`
- now will use the the `gh-pages` package to deploy
- run `npm run deploy` it looks like this `"deploy": "gh-pages -d vr/build"` in the `package.json`
- `gh-pages` also requires the "homepage" to be set in `package.json`, it will look like this: `"homepage": "https://graysonhicks.github.io/vrWorkplace"`
- now run `npm run deploy`
- you should not have to checkout/merge/alter on the gh-pages directly as long as this process is done correctly, otherwise can cause failures
### To Do
- main menu as select/options instead of buttons
- move homelink to client js to allow for fixed position like 'full screen' and direction buttons
- ~~reset camera position on scene changes~~
- set correct rotations on hotpoints
- maybe keep pano in state
- fetch data remotely from json in deploy/production mode
- ~~fetch data remotely from json (locally)~~
- ~~inital loading animation~~
- ~~loading animation for pano image changes~~
- ~~make welcome text its own Component, ``~~
- ~~fade `` in and out on page load, remove from click events~~
- ~~`` component to hold and animate `` and ``~~
- ~~home button to return to main menu from scene~~
- ~~new main menu pano~~
- ~~close icon on panel to toggle~~
- ~~animate hotpoints on hover (use Animate like this: https://www.sitepoint.com/building-a-full-sphere-3d-image-gallery-with-react-vr/)~~
- ~~menu jump on hotpoint click bug~~
- ~~set translates on hotpoints to be equidistant from perspective~~
- ~~show info panel on hotpoints click~~
- ~~refactor buttons and hotpoints to individual component files~~