Merge pull request #3 from googlefonts/piet

Very basic compute shader wired up

Author: raphlinus

.gitignore

@@ -1,2 +1,4 @@
 target
-Cargo.lock
+.ninja_deps
+.ninja_log
+

README.md

@@ -18,6 +18,8 @@ The second subdirectory is a simple GUI application that runs a compute shader a
 
 Recommended activity: find an existing shadertoy that implements some interesting algorithm or visual effect, and port it to run in a compute shader. Is there some limitation of the original that could be improved by compute capabilities?
 
+A great place to find shaders to adapt is [The Book of Shaders].
+
 ## A note on the choice of runtime
 
 Your compute shader code cannot run on its own, but rather needs a *runtime* to connect to the GPU, set up resources such as buffers and compiled shader code, and manage the submission of that work to the GPU. There is, as of this writing, no standard runtime for such things, but I hope that will change in time.
@@ -66,3 +68,4 @@ Licensed under either of
 [Cg]: https://www.khronos.org/opengl/wiki/Cg
 [rust-gpu]: https://github.com/EmbarkStudios/rust-gpu
 [IREE]: https://google.github.io/iree/
+[The Book of Shaders]: https://thebookofshaders.com/

compute-shader-toy/Cargo.toml

@@ -3,6 +3,7 @@ name = "compute-shader-toy"
 version = "0.1.0"
 authors = ["Raph Levien <raph@google.com>"]
 license = "MIT/Apache-2.0"
+description = "A simple compute shader example that draws in a window, based on wgpu."
 edition = "2018"
 
 [dependencies]

compute-shader-toy/src/main.rs

@@ -14,7 +14,7 @@
 //
 // Also licensed under MIT license, at your choice.
 
-//! A simple
+//! A simple compute shader example that draws into a window, based on wgpu.
 
 use wgpu::util::DeviceExt;
 use wgpu::{BufferUsage, Extent3d};

docs/glossary.md

@@ -8,7 +8,7 @@ One barrier to learning and talking about GPU compute is the bewildering termino
 * [WebGPU](https://github.com/gpuweb/gpuweb) - [WebGPU shading language](https://gpuweb.github.io/gpuweb/wgsl/)
 * [CUDA](https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html)
 
-My choice of 5 API's is somewhat opinionated, and future-leaning. I've left off OpenGL and OpenCL because they appear to be stagnating. Even though my main focus is writing compute shaders, because I'm interested in portability, I'm also including CUDA because it's by far the best developed API for writing GPU compute, and one that will no doubt be familiar to mamy readers.
+My choice of 5 API's is somewhat opinionated, and future-leaning. I've left off OpenGL and OpenCL because they appear to be stagnating. Even though my main focus is writing compute shaders, because I'm interested in portability, I'm also including CUDA because it's by far the best developed API for writing GPU compute, and one that will no doubt be familiar to many readers.
 
 I'm including WebGPU because I feel it has potential to become a common, widely implemented standard, on which it's possible to build a rich infrastructure of tools, libraries, and applications. The people working on WebGPU are doing a lot of deep thinking about achieving portability, performance, and security on GPU, and these discussions are openly available.