← All projects

Part 1 of this project

Getting Started

Open a CustomTkinter window that greets Pulsebay

Goal for this part

Open a CustomTkinter window that greets Pulsebay.

Treat 01-Getting-Started as the source of truth for this checkpoint. If your local tree drifted, re-clone that folder rather than mixing files from neighbors.

What you should already know

You do not need prior CustomTkinter experience for part 1. Later parts assume you finished the earlier snapshots on the same machine.

  • You can open a terminal and run python3
  • You are comfortable editing a .py file and saving it
  • You have a desktop session (not a headless SSH box without display forwarding)

Why CustomTkinter fits Pulsebay

CustomTkinter modernizes Tkinter widgets. Pair it with psutil to teach live metrics without a heavyweight GUI stack.

Tabs for CPU, memory, and processes keep the UI readable. Poll on a timer—never block the main thread on long scans.

Checkpoint

After you run the snapshot, you should recognize the behavior described in the goal—before you move on. If the window (or server) never appears, stop and fix the run steps.

Code shape

Snapshots stay small on purpose. Look for this kind of core call as you read the folder:

psutil.cpu_percent(interval=0.2)

How to run it

Clone the teaching repo, open 01-Getting-Started, install what the README asks for, then run python app.py.

git clone https://github.com/michaeldunga1/fcc-ctk-monitor.git
cd fcc-ctk-monitor/01-Getting-Started
python3 -m venv .venv
source .venv/bin/activate
pip install -r ../requirements.txt
python app.py

Common mistakes

  • Ignoring platform-specific install notes in the snapshot README
  • Running from the repo root instead of the numbered snapshot folder
  • Skipping the install steps listed on this page
  • Closing the app before you confirm the greeting/layout checkpoint

Related tutorials