Skip to content
This repository was archived by the owner on Jan 6, 2025. It is now read-only.

Commit 516b8c4

Browse files
author
Steven Vergenz
committed
Remove mac references
1 parent 3e39b6e commit 516b8c4

File tree

3 files changed

+6
-11
lines changed

3 files changed

+6
-11
lines changed

README.md

+2-4
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ THIS FILE IS GENERATED FROM README.template.md. EDIT THAT INSTEAD
88

99
## [A-Frame API](https://altspacevr.github.io/AltspaceSDK/doc/aframe/) - [Three.js API](https://altspacevr.github.io/AltspaceSDK/doc/js/)
1010

11-
The AltspaceVR SDK can be used together with [Three.js] or [A-Frame] to create holographic, multi-user web apps for virtual reality. When running inside [AltspaceVR](https://altvr.com/) they can be experienced with consumer VR hardware including the Oculus Rift, HTC Vive, Samsung GearVR, and Google Daydream, as well as in non-VR mode for PC, Mac, and Mobile.
11+
The AltspaceVR SDK can be used together with [Three.js] or [A-Frame] to create holographic, multi-user web apps for virtual reality. When running inside [AltspaceVR](https://altvr.com/) they can be experienced with consumer VR hardware including the Oculus Rift, HTC Vive, Samsung GearVR, and Google Daydream, as well as in non-VR mode for PC.
1212

1313
Three.js is an open-source, renderer-agnostic 3D engine written in Javascript. It is used to construct much of the 3D graphics you see on the web, and can be used to create entire applications, or enhance existing webpages with 3D content. A-Frame is a later addition to the 3D Web family, simplifying the process with the use of HTML-style markup to build 3D scenes instead of Javascript.
1414

@@ -64,9 +64,7 @@ NOTE: these instructions do not apply to Android-based devices!
6464

6565
We provide a standalone debugger that can connect to SDK apps while they're running in Altspace and has the normal functionality of the Chrome developer tools (i.e. you can read console logs, look at the values of variables, execute Javascript, etc.) You can download it here:
6666

67-
**[OSX Debugger](http://sdk.altvr.com/debugger/DebuggerMacOSX.zip) - [Windows Debugger](http://sdk.altvr.com/debugger/DebuggerWindows.exe)**
68-
69-
(Note that you cannot rename the OSX Debugger from Debugger.app after you extract it, or it won’t run due to legacy .app bundle structure — it needs an Info.plist with metadata.)
67+
[Windows Debugger](http://sdk.altvr.com/debugger/DebuggerWindows.exe)**
7068

7169
More generally, Altspace browsers are implemented using an embedded Chromium which exposes the Chrome debugging protocol version 1.1. You can find documentation on the protocol and usage [here](https://developer.chrome.com/devtools/docs/debugger-protocol). The protocol is exposed via a WebSocket interface on port 9999, rather than 9222 as is typical for the Chrome desktop browser. You can test it out by accessing http://localhost:9999/json while running Altspace to see a list of active in-world browsers and enclosures in JSON format.
7270

README.template.md

+2-4
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ THIS FILE IS GENERATED FROM README.template.md. EDIT THAT INSTEAD
88

99
## [A-Frame API](https://altspacevr.github.io/AltspaceSDK/doc/aframe/) - [Three.js API](https://altspacevr.github.io/AltspaceSDK/doc/js/)
1010

11-
The AltspaceVR SDK can be used together with [Three.js] or [A-Frame] to create holographic, multi-user web apps for virtual reality. When running inside [AltspaceVR](https://altvr.com/) they can be experienced with consumer VR hardware including the Oculus Rift, HTC Vive, Samsung GearVR, and Google Daydream, as well as in non-VR mode for PC, Mac, and Mobile.
11+
The AltspaceVR SDK can be used together with [Three.js] or [A-Frame] to create holographic, multi-user web apps for virtual reality. When running inside [AltspaceVR](https://altvr.com/) they can be experienced with consumer VR hardware including the Oculus Rift, HTC Vive, Samsung GearVR, and Google Daydream, as well as in non-VR mode for PC.
1212

1313
Three.js is an open-source, renderer-agnostic 3D engine written in Javascript. It is used to construct much of the 3D graphics you see on the web, and can be used to create entire applications, or enhance existing webpages with 3D content. A-Frame is a later addition to the 3D Web family, simplifying the process with the use of HTML-style markup to build 3D scenes instead of Javascript.
1414

@@ -62,9 +62,7 @@ If you use npm, you can install altspace.js with:
6262

6363
We provide a standalone debugger that can connect to SDK apps while they're running in Altspace and has the normal functionality of the Chrome developer tools (i.e. you can read console logs, look at the values of variables, execute Javascript, etc.) You can download it here:
6464

65-
**[OSX Debugger](http://sdk.altvr.com/debugger/DebuggerMacOSX.zip) - [Windows Debugger](http://sdk.altvr.com/debugger/DebuggerWindows.exe)**
66-
67-
(Note that you cannot rename the OSX Debugger from Debugger.app after you extract it, or it won’t run due to legacy .app bundle structure — it needs an Info.plist with metadata.)
65+
[Windows Debugger](http://sdk.altvr.com/debugger/DebuggerWindows.exe)**
6866

6967
More generally, Altspace browsers are implemented using an embedded Chromium which exposes the Chrome debugging protocol version 1.1. You can find documentation on the protocol and usage [here](https://developer.chrome.com/devtools/docs/debugger-protocol). The protocol is exposed via a WebSocket interface on port 9999, rather than 9222 as is typical for the Chrome desktop browser. You can test it out by accessing http://localhost:9999/json while running Altspace to see a list of active in-world browsers and enclosures in JSON format.
7068

doc/index.html

+2-3
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
-->
77
<h1 id="altspacevr-sdk">AltspaceVR SDK</h1>
88
<h2 id="a-frame-api-three-js-api"><a href="https://altspacevr.github.io/AltspaceSDK/doc/aframe/">A-Frame API</a> - <a href="https://altspacevr.github.io/AltspaceSDK/doc/js/">Three.js API</a></h2>
9-
<p>The AltspaceVR SDK can be used together with <a href="http://threejs.org/">Three.js</a> or <a href="https://aframe.io/docs/0.7.0/introduction/">A-Frame</a> to create holographic, multi-user web apps for virtual reality. When running inside <a href="https://altvr.com/">AltspaceVR</a> they can be experienced with consumer VR hardware including the Oculus Rift, HTC Vive, Samsung GearVR, and Google Daydream, as well as in non-VR mode for PC, Mac, and Mobile.</p>
9+
<p>The AltspaceVR SDK can be used together with <a href="http://threejs.org/">Three.js</a> or <a href="https://aframe.io/docs/0.7.0/introduction/">A-Frame</a> to create holographic, multi-user web apps for virtual reality. When running inside <a href="https://altvr.com/">AltspaceVR</a> they can be experienced with consumer VR hardware including the Oculus Rift, HTC Vive, Samsung GearVR, and Google Daydream, as well as in non-VR mode for PC.</p>
1010
<p>Three.js is an open-source, renderer-agnostic 3D engine written in Javascript. It is used to construct much of the 3D graphics you see on the web, and can be used to create entire applications, or enhance existing webpages with 3D content. A-Frame is a later addition to the 3D Web family, simplifying the process with the use of HTML-style markup to build 3D scenes instead of Javascript.</p>
1111
<p>If you choose, you can apply for AltspaceVR developer privileges <a href="http://developer.altvr.com/devflag">here</a>. You will typically have a response within 2-3 days. Once granted, you will have access to a host of new activity types that are designed for SDK use. This is not required to use the SDK though.</p>
1212
<p><strong>If you are brand new to web development</strong> or 3D applications, we recommend you develop with A-Frame, as it&#39;s more user-friendly and has more utility built-in. Head over to our <a href="https://altspacevr.github.io/AltspaceSDK/doc/aframe/">A-Frame API Documentation</a> for more info on how to get started using A-Frame with AltspaceVR. You should also check out the official reference from <a href="https://aframe.io/docs/0.7.0/introduction/">A-Frame</a>.</p>
@@ -42,8 +42,7 @@ <h2 id="sdk-feature-overview">SDK Feature Overview</h2>
4242
<p>** Meshes outside the bounds of the enclosure will be culled unless you request full space access.</p>
4343
<h2 id="debugging-sdk-apps">Debugging SDK Apps</h2>
4444
<p>We provide a standalone debugger that can connect to SDK apps while they&#39;re running in Altspace and has the normal functionality of the Chrome developer tools (i.e. you can read console logs, look at the values of variables, execute Javascript, etc.) You can download it here:</p>
45-
<p><strong><a href="http://sdk.altvr.com/debugger/DebuggerMacOSX.zip">OSX Debugger</a> - <a href="http://sdk.altvr.com/debugger/DebuggerWindows.exe">Windows Debugger</a></strong></p>
46-
<p>(Note that you cannot rename the OSX Debugger from Debugger.app after you extract it, or it won’t run due to legacy .app bundle structure — it needs an Info.plist with metadata.)</p>
45+
<p><strong><a href="http://sdk.altvr.com/debugger/DebuggerWindows.exe">Windows Debugger</a></strong></p>
4746
<p>More generally, Altspace browsers are implemented using an embedded Chromium which exposes the Chrome debugging protocol version 1.1. You can find documentation on the protocol and usage <a href="https://developer.chrome.com/devtools/docs/debugger-protocol">here</a>. The protocol is exposed via a WebSocket interface on port 9999, rather than 9222 as is typical for the Chrome desktop browser. You can test it out by accessing <a href="http://localhost:9999/json">http://localhost:9999/json</a> while running Altspace to see a list of active in-world browsers and enclosures in JSON format.</p>
4847
<p>There are many third-party tools that speak this protocol which you can point at running Altspace browsers, e.g.:</p>
4948
<ul>

0 commit comments

Comments
 (0)