|
16 | 16 | # TODO: 1. |
17 | 17 | # (Yes, that means for YOU to DO things per these instructions:) |
18 | 18 | # |
19 | | -# Run this module by using the green arrow on the toolbar up top. |
20 | | -# After running, find the Console tab (to the right) and confirm that |
| 19 | +# Run this module by right clicking anywhere in this window and select |
| 20 | +# Run 'name of file' |
| 21 | +# After running, find the Console tab (below) and confirm that |
21 | 22 | # Hello, World |
22 | 23 | # did indeed get printed (displayed) on the Console. |
23 | 24 | # |
|
27 | 28 | # |
28 | 29 | # TODO: 2. |
29 | 30 | # Notice the small horizontal BLUE bars on the scrollbar-like thing |
30 | | -# on the right. Each blue bar indicates a TODO in this module. |
| 31 | +# on the right. Each blue bar indicates a TO DO in this module. |
31 | 32 | # |
32 | | -# a. You can use the blue bars to go from one TODO to the next |
| 33 | +# a. You can use the blue bars to go from one TO DO to the next |
33 | 34 | # by clicking on the blue bars. ** Try that now. ** |
34 | 35 | # |
35 | | -# b. When you have completed a TODO, you should change the word |
| 36 | +# b. When you have completed a TO DO, you should change the word |
36 | 37 | # TODO |
37 | 38 | # to |
38 | 39 | # DONE. |
|
43 | 44 | # finished all the exercises in a module -- there will be no blue bars |
44 | 45 | # left on the scrollbar-like thing to the right. |
45 | 46 | # |
46 | | -# You have now completed TODO #2, so change its TODO on line 26 to DONE |
| 47 | +# You have now completed TO DO #2, so change its TO DO on line 26 to DONE |
47 | 48 | # (and proceed similarly for all forthcoming TODOs in this course). |
48 | 49 | # |
49 | 50 | ######################################################################## |
50 | 51 |
|
51 | 52 | ######################################################################## |
52 | 53 | # |
53 | 54 | # TODO: 3. |
54 | | -# Add another print statement below the current Line 1. |
| 55 | +# Add another print statement below. |
55 | 56 | # It should print any string that you want (but keep it G-rated!) |
56 | | -# Test your code by re-running this module and looking at |
57 | | -# the Console to be sure that your string printed as expected. |
| 57 | +# Test your code by re-running this module using either the right click |
| 58 | +# method again or by using the play button in the upper right. |
| 59 | +# Look at the Console to be sure that your string printed as expected. |
58 | 60 | # |
59 | 61 | ######################################################################## |
60 | 62 |
|
61 | 63 | ######################################################################## |
62 | 64 | # |
63 | 65 | # TODO: 4. |
64 | | -# Add yet another print statement, just below the previous one. |
65 | | -# This one should print the product of 3,607 and 34,227. |
| 66 | +# Add yet another print statement. |
| 67 | +# This one should print the *product* of 3,607 and 34,227. |
66 | 68 | # Let the computer do the arithmetic for you (no calculators!). |
67 | | -# You do NOT have to use strings for this, so no quote marks! |
| 69 | +# You do NOT have to use strings for this, so no quotation marks! |
68 | 70 | # |
69 | 71 | # TEST your code by re-running this module, then asking someone |
70 | | -# whom you trust: What number did your print display? |
71 | | -# (HINT: It is an INTERESTING number.) Get help if yours is wrong. |
| 72 | +# whom you trust: What number did your print display for TO DO 4? |
| 73 | +# (HINT: It is an INTERESTING number.) Get help if your value is wrong. |
72 | 74 | # |
73 | 75 | ######################################################################## |
74 | 76 |
|
|
78 | 80 | # Look at the list of files in this project in the |
79 | 81 | # PyDev Package Explorer |
80 | 82 | # to the left. |
81 | | -# Note that this file (m2_hello_world.py) has a little black dot |
82 | | -# to the left of the filename. That means that you have |
83 | | -# made changes to this file that you have not yet turned in. |
| 83 | +# Note that this file (m2_hello_world.py) is now displayed in a blue |
| 84 | +# font color. That means that you have made changes to this file which |
| 85 | +# have not yet been committed. |
84 | 86 | # |
85 | | -# COMMIT your work (which turns it in) by selecting (clicking on) |
86 | | -# the file with the black dot (or the entire project if you prefer) |
87 | | -# and then do SVN ~ Commit... from the SVN menu at the top. |
88 | | -# |
89 | | -# Then check that the black symbol beside the file name in the |
90 | | -# PyDev Package Explorer on the left has gone away. |
91 | | -# That's how you can tell that you have turned in your work. |
| 87 | +# COMMIT your work by selecting VCS from the menu bar, then select Commit Changes |
| 88 | +# Make sure only the files you want to commit are checked and optionally |
| 89 | +# add a quick Commit message to describe your work. Then hover over the |
| 90 | +# Commit button and select Commit and Push. Commit saves the work to |
| 91 | +# your computer. Push saves a copy of your work up into your Github |
| 92 | +# repository (saving to the cloud is saver). |
92 | 93 | # |
93 | 94 | # Oh, one more thing: |
94 | 95 | # Do you have any blue bars left on the on the scrollbar-like thing |
95 | 96 | # to the right? If so, click on each blue bar and change |
96 | | -# its TODO to DONE. Then run the file to save it, and COMMIT again. |
| 97 | +# its TO DO to DONE. Then run the file (to make sure you didn't break |
| 98 | +# anything) then Commit and Sync again. |
97 | 99 | # |
98 | 100 | # You can COMMIT as often as you like. DO FREQUENT COMMITS. |
99 | 101 | # |
|
0 commit comments