aboutsummaryrefslogtreecommitdiff
path: root/html/blackbox.html
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2013-03-30 20:04:10 +0000
committerSimon Tatham <anakin@pobox.com>2013-03-30 20:04:10 +0000
commite2c84a5fd2b1ca6d3d8be0279466079b35b6c189 (patch)
tree59ff27ef2ca442ba15fa855f900a7f8ec1d1a59d /html/blackbox.html
parent6920d97c0977a77be869ecfa1ae933eaaf131e90 (diff)
downloadpuzzles-e2c84a5fd2b1ca6d3d8be0279466079b35b6c189.zip
puzzles-e2c84a5fd2b1ca6d3d8be0279466079b35b6c189.tar.gz
puzzles-e2c84a5fd2b1ca6d3d8be0279466079b35b6c189.tar.bz2
puzzles-e2c84a5fd2b1ca6d3d8be0279466079b35b6c189.tar.xz
Introduce a mechanism in this source tree for building the container
web pages for the Java applets. Previously, those have all been maintained by hand in my website's svn area, which is a bit silly. Now we have a file per puzzle in the 'html' subdirectory which contains the puzzle's name, one or two attributes, and the instructions snippet to go below the puzzle applet; and then there's a Perl script that builds all the real web pages out of that by adding in the parts common across all files: the header, footer, and middle fragment with the <applet> tag and resizing bits and pieces. One piece _not_ checked in here is the footer text specific to my hosting at chiark, which I think does still belong in the www area. So Buildscr doesn't actually build the web pages; it just delivers the bits and pieces by which my nightly snapshot script will be able to run the program that _does_ build them, passing that footer as an extra argument. [originally from svn r9780]
Diffstat (limited to 'html/blackbox.html')
-rw-r--r--html/blackbox.html16
1 files changed, 16 insertions, 0 deletions
diff --git a/html/blackbox.html b/html/blackbox.html
new file mode 100644
index 0000000..f98604f
--- /dev/null
+++ b/html/blackbox.html
@@ -0,0 +1,16 @@
+Black Box
+<p>
+Determine where the hidden balls are in the box, by observing the
+behaviour of light beams fired into the box from the sides.
+<p>
+Click in a square around the edge of the box to send a beam into the
+box. Possible results are 'H' (the beam hit a ball dead-on and
+stopped), 'R' (the beam was either reflected back the way it came or
+there was a ball just to one side of its entry point) or a number
+appearing in two squares (indicating that the beam entered one of
+those squares and emerged from the other).
+<p>
+Click in the middle of the box to place your guessed ball positions.
+When you have placed enough, a green button will appear in the top
+left; click that to indicate that you think you have the answer.
+You can also right-click to mark squares as definitely known.