P1 Updates in Images

[jamesjuett]

Several images are slightly out-of-date with respect to recent changes to P1:

• Addition of new driver. Now two_sample.cpp rather than main.cpp.
• Name change from p1-stats to stats
• Change from p1_library.hpp and p1_library.cpp to library.hpp and library.cpp.

I think students should still be able to follow the tutorials without much disturbance. It would be nice to update the images, but it is a lot of work.

A couple other possibilities:

• Revert the changes so that P1 is back to p1-stats rather than stats. However, that would be inconsistent with the updated naming for the rest of the projects to remove the hardcoded number.
• Consider a dedicated project 0 for EECS 280. That would presumably lower maintenance burden in the tutorials since it would change less frequently.
• Update images, but make them more agnostic about the specific files or somehow else indicate "your files may vary".

This issue supersedes #195

[awdeorio]

I think students should still be able to follow the tutorials without much disturbance. It would be nice to update the images, but it is a lot of work.

I agree that this is probably fine as-is. Or at least a lower priority problem.

Revert the changes so that P1 is back to p1-stats rather than stats. However, that would be inconsistent with the updated naming for the rest of the projects to remove the hardcoded number.

I would be fine with this, but I expect you had reasons to make the change in the first place.

Consider a dedicated project 0 for EECS 280. That would presumably lower maintenance burden in the tutorials since it would change less frequently.

I'm hesitant to add a dedicated project 0 for EECS 280 because I feel like Project 1 serves that role and the setup tutorials already feel like a lot for students.

Update images, but make them more agnostic about the specific files or somehow else indicate "your files may vary".

This would be nice to have wherever it's reasonably possible.

[awdeorio]

I gave this a little more thought. I believe that the name change affects the screenshots for Visual Studio and Xcode in addition to VS Code on macOS and VS Code on Windows, which have many separate screenshots. I wonder if updating the screenshots is really worth it.