The Four Core Controls of Workspace

Workspace consists of four primary controls that serve distinct yet complementary roles. Together, they allow developers to organize the project, work on source code, navigate its structure, and inspect operation outputs.

Environment Workspace IDE
Components 4 Integrated Controls
Document Type Conceptual Functional Description

00 Conceptual Environment Layout

Each component addresses a distinct dimension of the daily development workflow: physical file structure, text editing, semantic structure, and execution output.

Workspace — Integrated Development Environment 1. Project Tree 📁 /src ├─ main.prg └─ utils.prg Physical structure 2. Editor FUNCTION Main() // Active source code RETURN NIL Editing & syntax 3. Navigator ƒ Main() C TWorkspace m Init() Semantic structure 4. Console > BuildSystem: Building project... 0 errors, 0 warnings. Process output, commands, and diagnostics
Layout and interaction diagram of the four core controls in Workspace.

01 Breakdown of the Four Controls

1. Project Tree
File Explorer

The explorer for the project's directory hierarchy, allowing developers to inspect folders, files, and their structural relationships.

Key functions:

  • Organize and browse project files.
  • Inspect folders and subfolders.
  • Select files to open them in the editor.
  • Access file and directory operations.
  • Identify the overall project layout.
Responsibility: Manage navigation across the physical file structure of the project.
2. Editor
Workspace Area

The primary workspace surface where source code is written and modified.

Key functions:

  • Open and edit source code files.
  • Provide language syntax highlighting.
  • Manage open documents.
  • Facilitate reading and modifying code.
  • Enable direct editing of file contents.
Responsibility: Provide the environment for editing and modifying source code.
4. Console
Output & Diagnostics

The dedicated area for displaying output from processes and operations executed by Workspace.

Key functions:

  • Display compilation process messages.
  • Report errors and warnings.
  • Show BuildSystem results.
  • Present output from executed commands and processes.
  • Assist in troubleshooting issues during development.
Responsibility: Serve as the communication channel between Workspace and the processes it executes.

02 Summary of Responsibilities

Control Primary Responsibility
Project Tree Organize and locate project files.
Editor Write and modify source code.
Navigator Find and traverse internal code elements.
Console Display process results, messages, and diagnostics.

03 How They Work Together

The four controls form an integrated development environment where each stage flows seamlessly into the next:

STEP 1
Project Tree

Lets you locate and select a file within the project hierarchy.

STEP 2
Editor

Lets you open, read, and edit its contents with syntax highlighting.

STEP 3
Navigator

Lets you quickly locate functions, procedures, classes, and methods inside the code.

STEP 4
Console

Reports what happens when operations, commands, or builds are executed.

Core Concept

Each control has a distinct responsibility: the Tree manages project structure; the Editor handles file contents; the Navigator exposes internal code structure; and the Console surfaces information generated by running processes.

04 Scope of This Documentation

Note

This is a conceptual functional description. Specific capabilities should be verified against the actual implementation of each control in Workspace.