Just noticed another thing that could easily catch me out when
[sgt/puzzles] / CHECKLST.txt
1 Useful checklists
2 =================
3
4 Things to remember when adding a new puzzle
5 -------------------------------------------
6
7 Write the source file for the new puzzle (duhh).
8
9 Write a section in print.py, if applicable.
10
11 Add it to Recipe in _four_ places:
12 - the `ALL' definition, to ensure it is compiled into the OS X binary
13 - as a GTK build target
14 - as a Windows build target
15 - in the Unix `make install' section at the bottom.
16
17 Add it to list.c so that the OS X binary will be able to select it
18 from the menus. (Also, double-check that the game structure name in
19 the source file has been renamed from `nullgame'. Actually compiling
20 it on OS X would be a good way to check this, if convenient.)
21
22 Add a documentation section in puzzles.but.
23
24 Make sure there's a Windows help topic name defined in puzzles.but,
25 and that it's referenced by the help topic field in the game
26 structure in the source file.
27
28 Add the new Unix binary name to the svn:ignore property.
29
30 Don't forget to `svn add' the new source file before checkin!
31
32 Put the puzzle on the web:
33 - make a screenshot
34 - add an entry in the puzzles list in index.html
35 - add a link to the Windows binary
36 - make sure the Windows binary link points at the right binary, not
37 the wrong one!
38 - run puzzlesnap
39 - test that the binary link and the docs link work
40 - run webupdate
41 - test again
42 - `svn add' the binary symlink and the screenshot
43 - check in the website changes (screenshot, symlink, index.html)