Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Ablesons
three.js
提交
9ec1a7b9
T
three.js
项目概览
Ablesons
/
three.js
与 Fork 源项目一致
从无法访问的项目Fork
通知
2
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
T
three.js
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
9ec1a7b9
编写于
4月 11, 2020
作者:
M
Mugen87
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Docs: Added page for WebXRManager.
上级
332760a1
变更
5
显示空白变更内容
内联
并排
Showing
5 changed file
with
140 addition
and
14 deletion
+140
-14
docs/api/en/renderers/WebGLRenderer.html
docs/api/en/renderers/WebGLRenderer.html
+2
-7
docs/api/en/renderers/webxr/WebXRManager.html
docs/api/en/renderers/webxr/WebXRManager.html
+64
-0
docs/api/zh/renderers/WebGLRenderer.html
docs/api/zh/renderers/WebGLRenderer.html
+2
-7
docs/api/zh/renderers/webxr/WebXRManager.html
docs/api/zh/renderers/webxr/WebXRManager.html
+64
-0
docs/list.js
docs/list.js
+8
-0
未找到文件。
docs/api/en/renderers/WebGLRenderer.html
浏览文件 @
9ec1a7b9
...
...
@@ -279,14 +279,9 @@
Tone mapping white point. Default is *1*.
</p>
<h3>
[property:
Object
xr]
</h3>
<h3>
[property:
WebXRManager
xr]
</h3>
<p>
Provides access to the WebXR related interface of the renderer.
</p>
<h3>
[property:Boolean xr.enabled]
</h3>
<p>
Whether the renderer should enable XR rendering or not. Default is *false*.
Provides access to the WebXR related [page:WebXRManager interface] of the renderer.
</p>
<h2>
Methods
</h2>
...
...
docs/api/en/renderers/webxr/WebXRManager.html
0 → 100644
浏览文件 @
9ec1a7b9
<!DOCTYPE html>
<html
lang=
"en"
>
<head>
<meta
charset=
"utf-8"
/>
<base
href=
"../../../../"
/>
<script
src=
"list.js"
></script>
<script
src=
"page.js"
></script>
<link
type=
"text/css"
rel=
"stylesheet"
href=
"page.css"
/>
</head>
<body>
<h1>
[name]
</h1>
<p
class=
"desc"
>
This class represents an abstraction of the WebXR Device API and is internally used by [page:WebGLRenderer].
[name] also provides a public interface that allows users to enable/disable XR and perform XR related tasks like
for instance retrieving controllers.
</p>
<h2>
Properties
</h2>
<h3>
[property:Boolean enabled]
</h3>
<p>
This flag notifies the renderer to be ready for XR rendering. Default is *false*. Set it to *true* if you are going
to use XR in your app.
</p>
<h3>
[property:Boolean isPresenting]
</h3>
<p>
Whether XR presentation is active or not. Default is *false*. This flag is read-only and automatically set by [name].
</p>
<h2>
Methods
</h2>
<h3>
[method:Group getController]( [param:Integer index] )
</h3>
<p>
[page:Integer index] — The index of the controller.
<br
/><br
/>
Returns a [page:Group] representing the so called *target ray* space of the controller.
Use this space for visualizing 3D objects that support the user in pointing tasks like UI interaction.
</p>
<h3>
[method:Group getControllerGrip]( [param:Integer index] )
</h3>
<p>
[page:Integer index] — The index of the controller.
<br
/><br
/>
Returns a [page:Group] representing the so called *grip* space of the controller.
Use this space if the user is going to hold other 3D objects like a lightsaber.
</p>
<p>
Note: If you want to show something in the user's hand AND offer a pointing ray at the same time, you'll want to attached the handheld object to the
group returned by [page:.getControllerGrip]() and the ray to the group returned by [page:.getController](). The idea is to have two different groups
in two different coordinate spaces for the same WebXR controller.
</p>
<h2>
Source
</h2>
<p>
[link:https://github.com/mrdoob/three.js/blob/master/src/[path].js src/[path].js]
</p>
</body>
</html>
docs/api/zh/renderers/WebGLRenderer.html
浏览文件 @
9ec1a7b9
...
...
@@ -256,14 +256,9 @@
色调映射的白点。默认是*1*
</p>
<h3>
[property:
Object
xr]
</h3>
<h3>
[property:
WebXRManager
xr]
</h3>
<p>
Provides access to the WebXR related interface of the renderer.
</p>
<h3>
[property:Boolean xr.enabled]
</h3>
<p>
Whether the renderer should enable XR rendering or not. Default is *false*.
Provides access to the WebXR related [page:WebXRManager interface] of the renderer.
</p>
<h2>
方法
</h2>
...
...
docs/api/zh/renderers/webxr/WebXRManager.html
0 → 100644
浏览文件 @
9ec1a7b9
<!DOCTYPE html>
<html
lang=
"en"
>
<head>
<meta
charset=
"utf-8"
/>
<base
href=
"../../../../"
/>
<script
src=
"list.js"
></script>
<script
src=
"page.js"
></script>
<link
type=
"text/css"
rel=
"stylesheet"
href=
"page.css"
/>
</head>
<body>
<h1>
[name]
</h1>
<p
class=
"desc"
>
This class represents an abstraction of the WebXR Device API and is internally used by [page:WebGLRenderer].
[name] also provides a public interface that allows users to enable/disable XR and perform XR related tasks like
for instance retrieving controllers.
</p>
<h2>
Properties
</h2>
<h3>
[property:Boolean enabled]
</h3>
<p>
This flag notifies the renderer to be ready for XR rendering. Default is *false*. Set it to *true* if you are going
to use XR in your app.
</p>
<h3>
[property:Boolean isPresenting]
</h3>
<p>
Whether XR presentation is active or not. Default is *false*. This flag is read-only and automatically set by [name].
</p>
<h2>
Methods
</h2>
<h3>
[method:Group getController]( [param:Integer index] )
</h3>
<p>
[page:Integer index] — The index of the controller.
<br
/><br
/>
Returns a [page:Group] representing the so called *target ray* space of the controller.
Use this space for visualizing 3D objects that support the user in pointing tasks like UI interaction.
</p>
<h3>
[method:Group getControllerGrip]( [param:Integer index] )
</h3>
<p>
[page:Integer index] — The index of the controller.
<br
/><br
/>
Returns a [page:Group] representing the so called *grip* space of the controller.
Use this space if the user is going to hold other 3D objects like a lightsaber.
</p>
<p>
Note: If you want to show something in the user's hand AND offer a pointing ray at the same time, you'll want to attached the handheld object to the
group returned by [page:.getControllerGrip]() and the ray to the group returned by [page:.getController](). The idea is to have two different groups
in two different coordinate spaces for the same WebXR controller.
</p>
<h2>
Source
</h2>
<p>
[link:https://github.com/mrdoob/three.js/blob/master/src/[path].js src/[path].js]
</p>
</body>
</html>
docs/list.js
浏览文件 @
9ec1a7b9
...
...
@@ -321,6 +321,10 @@ var list = {
"
UniformsUtils
"
:
"
api/en/renderers/shaders/UniformsUtils
"
},
"
Renderers / WebXR
"
:
{
"
WebXRManager
"
:
"
api/en/renderers/webxr/WebXRManager
"
},
"
Scenes
"
:
{
"
Fog
"
:
"
api/en/scenes/Fog
"
,
"
FogExp2
"
:
"
api/en/scenes/FogExp2
"
,
...
...
@@ -769,6 +773,10 @@ var list = {
"
UniformsUtils
"
:
"
api/zh/renderers/shaders/UniformsUtils
"
},
"
渲染器 / WebXR
"
:
{
"
WebXRManager
"
:
"
api/zh/renderers/webxr/WebXRManager
"
},
"
场景
"
:
{
"
Fog
"
:
"
api/zh/scenes/Fog
"
,
"
FogExp2
"
:
"
api/zh/scenes/FogExp2
"
,
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录