Working in Your Course IDE

Working in Your Course IDE

The Module Four Assignment uses several file types in VS Code. Each supports a different part of the workflow.

The Codio Virtual Desktop (CVD) is the IT 140 reference environment. A supported local computer configured through the Module One Setup Tasks can also be used.

Open the Assignment Folder

Open the repository folder in VS Code:

~/Repos/it140-m4-assignment

The Explorer should show it140-m4-assignment as the top-level folder. Opening the whole repository lets relative links, Git integration, and terminal commands work as intended.

Markdown Files (.md)

README, SRS, SDD, and SDW files use Markdown.

To read a Markdown file in a formatted view:

1. Right-click the file in the Explorer.
2. Choose Open Preview or Open Preview to the Side.

Opening instructions to the side is useful while working in another file.

Most Markdown files are course-provided. hilow_game_sdw.md is the optional Markdown file intended for student working notes.

Pseudocode File (.pseudo)

design/hilow_game.pseudo is the graded Module Four deliverable.

Open it in the regular text editor. Replace the starter TODO prompts with your own design.

Use indentation consistently so a reader can see which statements belong inside decisions and loops.

A useful workflow is:

1. open design/README.md in Preview to the side;
2. open hilow_game.pseudo in the main editor;
3. work on one requirement group at a time; and
4. save frequently.

Draw.io File (.drawio)

design/hilow_game.drawio is course-provided reference material.

It is not a graded Module Four deliverable. Do not edit or submit it unless current course instructions explicitly tell you otherwise.

VS Code Explorer

The Explorer shows the simplified SDLC folders:

analysis/
design/
src/
tests/

For the required Module Four assignment, your graded work is in design/.

Source Control

VS Code Source Control provides a graphical way to use Git.

A common save-to-GitHub workflow is:

1. select the Source Control icon;
2. review changed files;
3. stage only the student files you intended to change;
4. enter a short commit message;
5. commit; and
6. Sync/Push to GitHub.

Before committing, ask:

"Did I accidentally edit a course-provided file?"

If so, restore it before pushing.

Integrated Terminal

Use Terminal > New Terminal when repository instructions ask you to run a command.

Common uses include:

• checking Git status;
• committing/pushing work;
• running the optional Python program; and
• running the optional test file.

Windows users should use PowerShell or Git Bash rather than Command Prompt when following the repository shell commands.

Optional Python File (.py)

Only edit src/hilow_game.py after the graded pseudocode is complete if you choose the optional construction practice.

The starter includes main() and a main guard as scaffolding. Functions are taught later in the course; you do not need to master them for this optional exercise.

Run the optional program from the repository root:

python3 src/hilow_game.py

Problems Panel and Error Indicators

During optional Python practice, VS Code may underline syntax problems or show them in the Problems panel.

Treat these indicators as clues. Read the message, correct one problem, and run again.

GitHub Actions Are Separate From VS Code

After a push, GitHub runs Assignment Checks in your personal repository. VS Code does not automatically submit anything to D2L.

Remember:

VS Code = development environment

GitHub = repository and backup

D2L Brightspace = assignment submission, grading, and instructor feedback

Return to Home or continue to Testing and Debugging.