Desktop Program / Help Page
Use the desktop program to load C/C++ source files, compile with Clang, run EXE files in CMD, open code folders, edit user details, and connect to the server.
Download the current BYTE FORGE EDU desktop program package directly to the PC, then extract it into a normal local folder.
Download the ZIP package and extract it into a normal folder. The ZIP should contain the main program EXE and updater EXE. The program can create default settings files on first start.
Download is ready. After click, this button will be available again after 5 seconds.
A ZIP file is easiest for now. Students can extract it into a normal folder and run the EXE.
Do not run directly from inside the compressed ZIP preview. Extract the files first so the program can create its local txt files.
First launch checks the required local tools and shows clear color status boxes in the desktop window.
Extract the downloaded package into a normal folder on the PC.
Open the BYTE FORGE EDU executable from the extracted folder.
Green status means Notepad++ or Clang was found. Yellow means missing or not ready.
Use LOAD CODE FILE to choose a .c, .cpp, .cc, or .cxx file.
The normal student workflow is load source file, compile, inspect compiler messages, then run the compiled program.
Chooses the source file and remembers its project folder until another file is loaded.
Deletes the old EXE, runs Clang/Clang++, and prints warnings or errors in the big box.
Opens the compiled program in CMD so students can see output and input behavior.
Opens the current project folder in Windows File Explorer.
Opens source code in Notepad++ if installed, otherwise in the default editor.
Checks the server health API and can toggle connected/disconnected state.
Static screenshot tabs showing what the desktop program looks like and what each workflow screen is used for.
This is the first program view after startup. The big text area shows startup checks and later compiler messages. The right-side buttons are the main actions for loading code, compiling, running, opening folders, viewing files, opening the website, editing user details, and connecting to the server.
This tab is kept at the end for a future screenshot. Startup checks happen directly in the main window, so a separate startup screenshot is not needed for the current help flow.
Use this workflow when the student wants to load one direct source file. After a code file is loaded, the program remembers that file and its project folder for compile, run, open folder, and view file actions.
The folder loader is for project-style work. It opens a Windows Explorer-style folder picker, then checks the selected folder for a required start file.
After a valid project folder is loaded, the app lists the code and header files found in that folder. If main.c or main.cpp is found, it becomes the active compile target automatically.
The compile button clears the big message box, deletes the old EXE if it exists, runs Clang or Clang++, and then prints compiler output. This gives the student one place to read errors, warnings, output file name, and success status.
After compile success, the run button opens the compiled EXE in CMD. This lets students see the real program output, test keyboard input, and confirm that the compiled version is the one currently running.
The server button checks the web API health endpoint. When the server responds correctly, the button can show a green connected state so the user can see that the desktop app is online with the server.
The user details area is for local student/account data. The desktop app can save this data locally and sync it with the server so the website can later show safe public profile information.
The program is useful only when the student PC has a compiler ready. Notepad++ is optional but recommended.
Required for compile buttons. The program checks common LLVM and MSYS2 paths.
Required for C++ source files like .cpp, .cc, and .cxx.
Recommended for opening code files. If missing, Windows default editor is used.
Most problems come from missing tools, wrong folder paths, or trying to run before a successful compile.
Install Clang or add it to PATH, then restart the program.
Read the big output box and fix the first compiler error first.
Compile successfully first. The EXE must exist beside the source file.
Check that the loaded file still exists and the folder was not moved.
Check internet access and the configured health API URL.
Check write permissions in the program folder and server API response.