Sanity pass for code blocks.

[hollasch]

• [x] In One Weekend
  • [x] chapter 1
  • [x] chapter 2
  • [x] chapter 3
  • [x] chapter 4
  • [x] chapter 5
  • [x] chapter 6
  • [x] chapter 7
  • [x] chapter 8
  • [x] chapter 9
  • [x] chapter 10
  • [x] chapter 11
  • [x] chapter 12
• [x] The Next Week
  • [x] chapter 1
  • [x] chapter 2
  • [x] chapter 3
  • [x] chapter 4
  • [x] chapter 5
  • [x] chapter 6
  • [x] chapter 7
  • [x] chapter 8
  • [x] chapter 9
• [x] The Rest Of Your Life
  • [x] chapter 1
  • [x] chapter 2
  • [x] chapter 3
  • [x] chapter 4
  • [x] chapter 5
  • [x] chapter 6
  • [x] chapter 7
  • [x] chapter 8
  • [x] chapter 9

[trevordblack]

For instances of "float" and "double" and other types in the text, do we want them to be inlined, i.e. floats and doubles.

[hollasch]

I tend to use “single precision” and “double precision”, or “32-bit floats” and “64-bit floats” in prose unless I'm talking specifically about the types. If the types are important, then yeah, generally I try to mark them up as code: float/double. I'm not super strict on this, as sometimes my prose looks like a clown car of type changes, so sometimes I'll drop the inline code style just so the text reads easier (not usually).

So generally, use code styling, but with an escape hatch when you need it.

[lorihollasch]

• [ ] General: should be hittable, not hitable

Book 1

Chapter 2

• "top part of my vec3 class":
  • [x] Reorder include files to match src conventions
• "lots of vector operations":
  • [x] dot: unclear (spaces needed?)
  • [x] function signatures: inconsistent spacing, eg: ){ versus ) {
  • [x] two spaces after e[x] in some methods
  • [x] order methods consistently as + - * /
  • [x] unbold unit_vector
• "change our main":
  • [x] Reorder include files to match src conventions
  • [x] Put spaces

Chapter 3

• "add antialiasing later":
  • [x] Reorder include files to match src conventions
  • [x] Remove *world and depth parameters from color

Chapter 5

• "motion blur at some point":
  • [x] Put hit_record and { on same line
  • [x] Make spacing in 2 temp calculations the same
• "And a list of objects":
  • [x] Remove space between signature and hit_record_temp_rec
• "And the new main":
  • [x] Reorder include files to match src conventions

Chapter 6

• "camera from before":
  • [x] Add #include "random.h"
• "Main is also changed":
  • [x] Make spacing in s's for loop consistent with i and j (int s = 0)

Chapter 7

• "is perfect for that":
  • [x] Remove depth parameter from color

Chapter 8

• "in the hitable class below":
  • [x] Put hit_record and { on same line
• "below marked with":
  • [x] Make spacing in 2 temp calculations the same
• "For Lambertian materials":
  • [x] Put const and { on same line
  • [x] Remove blank space above vec3 albedo
• "The metal material":
  • [x] Put const and { on same line
• "And add some metal":
  • [x] List[0] Lambertian vec3 constants are different from Pete's
  • [x] Make spacing in s's for loop consistent with I and j (int s = 0)
  • [x] Add space between world, and 0 <- do elsewhere too?
• "sphere which yields":
  • [x] Put const and { on same line

Chapter 9

• "And the dielectric material":
  • [x] Put const and { on same line
  • [x] Add curly braces back to if (refract) statement
• "If we try that out":
  • [x] Remove 0.0 parameter from metal
• "This yields our full glass":
  • [x] Put const and { on same line

Chapter 10

• "with crazy camera angles":
  • [x] Change lookatfrom to be lookfrom

Chapter 11

• "rather than from a point":
  • [x] Put const and { on same line

[lorihollasch]

Book 2:

Chapter 1

• "rays over a time period":
  • [x] Camera's parameters layout differs from Book 1. Here there is one parameter per line versus several per line in Book 1
• "aperture open close":
  • [x] Add space between time0 and time1

Chapter 2

• "Here is such a class":
  • [x] One space instead of two between class and method?
• "will get optimized later":
  • [x] Add curly braces for conditions in axis if statement (for consistency)?
  • [x] Add space between time0,time1 (2 instances)

Chapter 3

• "any color a texture":
  • [x] constant_texture: change open brace to open curly
  • [x] books haven't had spaces between {} in empty constructors. Remove space(s) between { } (2 instances)
• "with a texture pointer":
  • [x] Change "const (" to "const {"
• "a 3D checker pattern":
  • [x] Remove space(s) between { } (2 instances)
• "If we add a new scene":
  • [x] List[0] and list[1] both missing );

Chapter 4

• "And we can use that one some spheres":
  • [x] Fix the above sentence (eg: "We can use that texture on some spheres")
  • [x] Change "() (" to "() {"
• "we can linearly interpolate":
  • [x] Change Z to 2
  • [x] Remove ; from end of pexm_z calculation
• "The Perlin class is now":
  • [x] Remove ; from end of pexm_z calculation
• "giving a marble-like effect":
  • [x] Change ") ;" to ");"

Chapter 6 Rectangles and Lights

• "It's very simple":
  • [x] Remove double spacing from "material {"
• "The actual xy_rect class":
  • [x] Remove double spacing from "hitable {"
• "This is yz and xz"
  • [x] Change to "xz and yz" to align with code for better readability
  • [x] Remove double spacing from "hitable {"
• "Let's make the 5 walls":
  • [x] Change hitable array size to 5? (was 6 in Pete's code; changed to 8 in new code)

Chapter 7 Instances

• "And the changes to Cornell is":
  • [x] ^should be "changes are" or "change is"
  • [x] Remove extraneous comma in second translate

Chapter 8 Volumes

• "And the changes to Cornell is":
  • [x] Remove blank line before phase function calculation
• "And the hit function is":
  • [x] Be consistent with short if statements. Some are on one line, some are on two lines.

Chapter 9 A Scene Testing All New Features

• "design decision":
  • [x] *light calculation: remove space between ") )"
  • [x] new sphere: add space between 400,200 and between 220,280
  • [x] sphere in for loop has code line that is long enough to require scrolling
  • [x] new bvh_node: add space between boxlist2,ns

[lorihollasch]

Book 3

Chapter 2 (Monte Carlo)

• "centered at the origin":
  • [x] Reorder include files to match src conventions
  • [x] Loop conditional should be i < N
• "a running estimate":
  • [x] Reorder include files to match src conventions
• "try it both ways":
  • [x] Reorder include files to match src conventions

Chapter 3 (1D MC Integration)

• "In fact it is exactly":
  • [x] Reorder include files to match src conventions
• "and the code is":
  • [x] Reorder include files to match src conventions
• "1 sample we get":
  • [x] Reorder include files to match src conventions

Chapter 6 (Importance Sampling Materials):

• "generates the model":
  • [x] Remove flip_normals from 3rd list item
  • [x] Make lookfrom and lookat spacing consistent
• "color function gets":
  • [x] Change hrec to rec

Chapter 7 (Generating Random Directions)

• "We can output":
  • [x] z calculation is different - is that an error or deliberate?

Chapter 8 (Ortho-normal Bases)

• "use that axis":
  • [x] Original book had pseudocode; new book has code block, but code isn't correct
• "using this to get":
  • [x] Remove extra space in direction calculation ") )"

Chapter 9 (Sampling Lights Directly)

• "see the highlighted region"
  • [x] Add highlighted region

Chapter 10 (Mixture Densities)

• "with the main changes highlighted"
  • [x] Add highlighted region
• "And then change color"
  • [x] Add light_shape to parameter list (see color code later in chapter)
  • [ ] Add open curly to "if (depth)" statement
  • [x] Add highlighted region
• "plugging it into color"
  • [x] Add highlighted region
  • [x] Add open curly to "if (depth)" statement

Chapter 12 (Cleaning Up pdf Management)

• "And color() changes are small"
  • [x] Add highlighted region
• "Metal is easy to fix"
  • [x] Add highlighted region
• "an implicitly sampled ray"
  • [x] Add highlighted region
• "We also need to change the block"
  • [x] Add highlighted region
• "We assemble a list to pass in to color"
  • [x] Did you mean to add all the extra code beyond hlist?