1b470bcf |
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. |
19 | |
20 | Add a documentation section in puzzles.but. |
21 | |
22 | Make sure there's a Windows help topic name defined in puzzles.but, |
23 | and that it's referenced by the help topic field in the game |
24 | structure in the source file. |
25 | |
26 | Add the new Unix binary name to the svn:ignore property. |
27 | |
28 | Don't forget to `svn add' the new source file before checkin! |
29 | |
30 | Put the puzzle on the web: |
31 | - make a screenshot |
32 | - add an entry in the puzzles list in index.html |
33 | - add a link to the Windows binary |
34 | - make sure the Windows binary link points at the right binary, not |
35 | the wrong one! |
36 | - run puzzlesnap |
37 | - test that the binary link and the docs link work |
38 | - run webupdate |
39 | - test again |
40 | - `svn add' the binary symlink and the screenshot |
41 | - check in the website changes (screenshot, symlink, index.html) |