ICS+File+Organization

It is your responsibility to keep your files organized and stored in the appropriate location(s). **File Location** In general, you will be working within your personal network space (P: drive). When saving work, it is always safer to use the "Save As" command (under the file menu) and select the correct location. **Warning:** Some programs will try to use the C: drive (desktop computer) by default. This may even work at first, but there are many ways to lose your work (switching computers, the computer is reformatted, sometimes just logging off). **Folder & File Structure** On your P: drive, you should create a folder for your current course: ICS2O, ICS3C, ICS3U, ICS4C, ICS4U. I usually recommend putting the numbers 00 in front, which ensures that this folder will always be at the time of your list. In this folder, you will create additional files and folders for the various units of study throughout the course. You have some choice in this, but it must be organized. **You may be required to demonstrate your file organization for a grade at various points throughout the course.** Below is a sample showing only some of the folders suggested for the ICS2O course. As you can hopefully see, numbering the folders also helps keep them in the order you prefer (usually the order in which they were done in the course, but not always).  P :

 ├── 00 ICS2O

 │ ├── 01 Programming in Scratch

 │ ├── 02 Computer Hardware

 │ ├── 03 Computer Security

 │ └── 04 Programming in Turing

<span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> │ ├── 01 Input & Output

<span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> │ │ ├── 01 Exercises

<span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> │ │ ├── 02 Assignments

<span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> │ │ └── 03 Miscellaneous

<span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> │ ├── 02 Programs That Calculate

<span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> │ └── 03 Making Decisions

<span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> ├── 00 ICS3U

<span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> └── 00 ICS4U <span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;">**File History** <span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;">Some exercises will be fairly simple, and you will complete them on your first try. For more involved exercises, or assignments, you will likely need to make several **revisions** of the file. Since we may want to see what we tried before, it is important to keep some sort of **revision history** of our files. This is particularly important for programs, because we may change a program that works, break it, and need to see the previous working program to understand how to fix it. <span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;">There are various ways to preserve the history of your files. The easiest use numbers or letters, plus a good file name, to keep track of changes. Don't forget to use the correct file extension (.t for Turing, .java for Java) on each of your files. <span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;">For example, suppose we have a program that calculates student marks, and we are developing this program in Turing. If we have been working on this for 5 days, we should have **at least** 5 copies, one for each day. You may have more than 5 copies if you made several important changes in a day. The general rule for revisions it to make a new revision each day, and also save a revision whenever you make a major change (usually this means you have gotten an important feature to work). <span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;">In P:\ICS3U\01 Programming in Turing\02 Programs That Calculate <span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> MarkCalc01.t <span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> MarkCalc02.t  <span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> MarkCalc03.t  <span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> MarkCalc04.t  <span style="background-color: #ffffff; color: #444444; font-family: 'Segoe UI','Lucida Grande',Arial; vertical-align: baseline;"> MarkCalc05.t