Review of illustrations by Casey

From Maze

(Difference between revisions)
Jump to: navigation, search
(Text about photos)
(Adding intro)
Line 1:Line 1:
−
===Photos===
+
In general, I think the strategy should be to include figures only when necessary, when they make a strong point or support the text substantially. I see the book has having a mixture of photography, diagrams, and screen shots. Based on what I've seen, I'm assuming the screen shots will be taken from an emulator. This looses much of the feeling of the CRT, but brings clarity.
−
 
−
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===
 +
 +
asdg
 +
 +
 +
===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? FYI, the Wikipedia photo has a CC attribution license so it can be used.
 +
 +
What about a photo of the way the graphics look on a CRT or a video of the program running for the web?
 +
 +
We can run tests of the photos as blue and black duotones. I think printing them with only black is a lost opportunity to make the book feel unique.
 +
 +
I'm excited to take a few high resolution photos of the original program pages in the manual and run those as a full spread with the spine of the manual in the spine of our book. This gives the physical context of the program, how the program was communicated. This is the book in a book technique.

Revision as of 14:26, 16 November 2010

View this revision of Review of illustrations by Casey.

Personal tools