Skip to content

Commit 4b34be4

Browse files
authored
minor doc tweaks (#265)
1 parent 191c32c commit 4b34be4

File tree

5 files changed

+25
-28
lines changed

5 files changed

+25
-28
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
# wgpu-py
66

7-
Next generation GPU API for Python
7+
A Python implementation of WebGPU - the next generation GPU API.
88

99
<img width=300 src='https://user-images.githubusercontent.com/3015475/159725890-5656204b-648b-4f6f-88d5-a656d8ad00c6.png' />
1010
<img width=300 src='https://user-images.githubusercontent.com/3015475/159726895-2c0cbc7b-ed0a-4cd3-a90c-dd579977eaa4.png' />
@@ -28,7 +28,7 @@ To get an idea of what this API looks like have a look at [triangle.py](https://
2828

2929
*The wgpu-API has not settled yet, use with care!*
3030

31-
* Coverage of the WebGPU spec is nearly complete.
31+
* Coverage of the WebGPU spec is complete enough to build e.g. [pygfx](https://github.com/pygfx/pygfx).
3232
* Test coverage of the API is 100%.
3333
* Support for Windows, Linux, and MacOS (Intel and M1).
3434
* Until WebGPU settles as a standard, its specification

docs/guide.rst

Lines changed: 19 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -5,37 +5,39 @@ Guide
55
Not a lot here yet. More will come over time.
66

77

8-
A brief history of WGPU
9-
-----------------------
8+
A brief history of WebGPU
9+
-------------------------
1010

1111
For years, OpenGL has been the only cross-platform API to talk to the GPU.
1212
But over time OpenGL has grown into an inconsistent and complex API ...
1313

1414
*OpenGL is dying*
1515
--- Dzmitry Malyshau at `Fosdem 2020 <https://fosdem.org/2020/schedule/event/rust_webgpu/>`_
1616

17-
In recent years, modern API's have emerged that solve many of OpenGL's problems.
18-
You may have heard of them: Vulkan, Metal, and DX12. These API's are
19-
much closer to the hardware. Unfortunately, the huge amount of "knobs
20-
to turn" makes them quite hard to work with for developers.
17+
In recent years, modern API's have emerged that solve many of OpenGL's
18+
problems. You may have heard of them: Vulkan, Metal, and DX12. These
19+
API's are much closer to the hardware, which makes the drivers more
20+
consistent and reliable. Unfortunately, the huge amount of "knobs to
21+
turn" also makes them quite hard to work with for developers.
2122

2223
Therefore, people are working on a higher level API, that wraps Vulkan/Metal/DX12,
23-
and uses the same principals, but is much easier to work with. This is the
24-
`WebGPU spec <https://gpuweb.github.io/gpuweb/>`_. This is what future devs
24+
using the same concepts, but is much easier to work with. This is the
25+
`WebGPU specification <https://gpuweb.github.io/gpuweb/>`_. This is what future devs
2526
will be using to write GPU code for the browser. And for desktop and mobile.
2627

27-
As WebGPU spec is being developed, a reference implementation is also
28-
being build. It's written in Rust, and is powering the WebGPU implementation in Firefox.
29-
This reference implementation, called `wgpu-native <https://github.com/gfx-rs/wgpu>`_,
30-
also exposes a C-api, which means that it can be wrapped in Python. And this is what
31-
wgpu-py does.
28+
As the WebGPU spec is being developed, a reference implementation is
29+
also build. It's written in Rust and powers the WebGPU implementation in Firefox.
30+
This reference implementation, called `wgpu <https://github.com/gfx-rs/wgpu>`_,
31+
also exposes a C-api (via `wgpu-native <https://github.com/gfx-rs/wgpu-native>`_),
32+
so that it can be wrapped in Python. And this is precisely what wgpu-py does.
3233

33-
So in short, wgpu-py is a Python wrapper of wgpu-native, which is a wrapper
34-
for Vulkan, Metal and DX12, which are low-level API's to talk to the GPU hardware.
34+
So in short, wgpu-py is a Python wrapper of wgpu, which is an desktop
35+
implementation of WebGPU, an API that wraps Vulkan, Metal and DX12,
36+
which talk to the GPU hardware.
3537

3638

37-
Getting started with WGPU
38-
-------------------------
39+
Getting started with WebGPU
40+
---------------------------
3941

4042
For now, we'll direct you to some related tutorials:
4143

docs/index.rst

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,5 @@
1-
.. wgpu-py documentation master file, created by
2-
sphinx-quickstart on Fri Apr 3 14:28:56 2020.
3-
You can adapt this file completely to your liking, but it should at least
4-
contain the root `toctree` directive.
5-
6-
Welcome to wgpu-py's documentation!
7-
===================================
1+
Welcome to the wgpu-py docs!
2+
==============================
83

94
.. automodule:: wgpu
105

docs/start.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ About this API
3333

3434
This library presents a Pythonic API for the `WebGPU spec
3535
<https://gpuweb.github.io/gpuweb/>`_. It is an API to control graphics
36-
hardware. Like OpenGL, but modern.
36+
hardware. Like OpenGL but modern, or like Vulkan but higher level.
3737
GPU programming is a craft that requires knowledge of how GPU's work.
3838
See the guide for more info and links to resources.
3939

wgpu/__init__.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
"""
2-
This a Python implementation of the next generation GPU API.
2+
The wgpu library is a Python implementation of WebGPU.
33
"""
44

55
from ._coreutils import logger # noqa: F401,F403

0 commit comments

Comments
 (0)