Review of illustrations by Casey
From Maze
(Difference between revisions)
(Starting the page with a few headers) | (Text about photos) | ||
| Line 1: | Line 1: | ||
===Photos=== | ===Photos=== | ||
| + | |||
| + | Somewhere, we should have some high-resolution and well-lit photos of the C64, particularly to have a macro shot of the diagonal lines. Who is the best photographer in the group? Ian? Me? | ||
| + | |||
| + | We can run tests of the images at duotones, blue and black. I think running them with only black is a lost opportunity to make the book feel unique. | ||
| + | |||
===Diagrams=== | ===Diagrams=== | ||
| + | |||
===Typography=== | ===Typography=== | ||
| − | The "Token-by-Token Explanation of the Program" section dividers could each present the full program, but blue used to highlight (a blue box) the token of the code that the paragraph refers to. | + | The "Token-by-Token Explanation of the Program" section dividers could each present the full program, with blue used to highlight (a solid blue box behind the black letters at 50% blue) the token the paragraph refers to. |
| + | |||
| + | All code should be set in a monospaced font an indented. I considered using the C64 font by commissioning it (if it doesn't already exist) but I think something that is more appropriate for the printed page will be better. Every time 10 PRINT reference appears in the body, it could also be in this mono font. (Maybe not, might be jarring for the reader; it's best to try and evaluate the comparison when the time comes.) | ||
