Substantial infrastructure upheaval. I've separated the drawing API

as seen by the back ends from the one implemented by the front end,
and shoved a piece of middleware (drawing.c) in between to permit
interchange of multiple kinds of the latter. I've also added a
number of functions to the drawing API to permit printing as well as
on-screen drawing, and retired print.py in favour of integrated
printing done by means of that API.

The immediate visible change is that print.py is dead, and each
puzzle now does its own printing: where you would previously have
typed `print.py solo 2x3', you now type `solo --print 2x3' and it
should work in much the same way.

Advantages of the new mechanism available right now:
 - Map is now printable, because the new print function can make use
   of the output from the existing game ID decoder rather than me
   having to replicate all those fiddly algorithms in Python.
 - the new print functions can cope with non-initial game states,
   which means each puzzle supporting --print also supports
   --with-solutions.
 - there's also a --scale option permitting users to adjust the size
   of the printed puzzles.

Advantages which will be available at some point:
 - the new API should permit me to implement native printing
   mechanisms on Windows and OS X.

[originally from svn r6190]

1 files changed, 0 insertions, 2 deletions

diff --git a/CHECKLST.txt b/CHECKLST.txt
index 9d68009..748104e 100644
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -6,8 +6,6 @@ Things to remember when adding a new puzzle
 
 Write the source file for the new puzzle (duhh).
 
-Write a section in print.py, if applicable.
-
 Add it to Recipe in _four_ places:
  - the `ALL' definition, to ensure it is compiled into the OS X binary
  - as a GTK build target