summaryrefslogtreecommitdiff
path: root/Client/ThirdParty/Box2D/docs/testbed.md
diff options
context:
space:
mode:
Diffstat (limited to 'Client/ThirdParty/Box2D/docs/testbed.md')
-rw-r--r--Client/ThirdParty/Box2D/docs/testbed.md21
1 files changed, 21 insertions, 0 deletions
diff --git a/Client/ThirdParty/Box2D/docs/testbed.md b/Client/ThirdParty/Box2D/docs/testbed.md
new file mode 100644
index 0000000..a6f2233
--- /dev/null
+++ b/Client/ThirdParty/Box2D/docs/testbed.md
@@ -0,0 +1,21 @@
+# Testbed
+Once you have conquered the HelloWorld example, you should start looking
+at Box2D's testbed. The testbed is a testing framework and demo
+environment. Here are some of the features:
+- Camera with pan and zoom.
+- Mouse picking of shapes attached to dynamic bodies.
+- Extensible set of tests.
+- GUI for selecting tests, parameter tuning, and debug drawing options.
+- Pause and single step simulation.
+- Text rendering.
+
+![Box2D Testbed](images/testbed.png)
+
+The testbed has many examples of Box2D usage in the test cases and the
+framework itself. I encourage you to explore and tinker with the testbed
+as you learn Box2D.
+
+Note: the testbed is written using [GLFW](https://www.glfw.org) and
+[imgui](https://github.com/ocornut/imgui). The testbed is not part of the
+Box2D library. The Box2D library is agnostic about rendering. As shown by
+the HelloWorld example, you don't need a renderer to use Box2D.