aboutsummaryrefslogtreecommitdiff
path: root/html/samegame.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/samegame.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/samegame.html')
-rw-r--r--html/samegame.html14
1 files changed, 14 insertions, 0 deletions
diff --git a/html/samegame.html b/html/samegame.html
new file mode 100644
index 0000000..e6de095
--- /dev/null
+++ b/html/samegame.html
@@ -0,0 +1,14 @@
+Same Game
+<p>
+Try to empty the playing area completely, by removing connected
+groups of two or more squares of the same colour. Then try to score
+as much as possible, by removing large groups at a time instead of
+small ones.
+<p>
+Click on a coloured square to highlight the rest of its connected
+group. The status line will print the number of squares selected,
+and the score you would gain by removing them. Click again to remove
+the group; other squares will fall down to fill the space, and if
+you empty a whole column then the other columns will move up. You
+cannot remove a single isolated square: try to avoid dead-end
+positions where all remaining squares are isolated.