# ibarrar/clipper architecture

> Architecture diagram of the GitHub repository ibarrar/clipper, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-07-01). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/ibarrar/clipper
- Repository: https://github.com/ibarrar/clipper

## Overview

1. This repository is not one application; it is an archive of several related DOS-era business systems built on the same Clipper tooling stack. The main products are POS variants, a payroll/accounting suite, and supporting utilities/drivers.

2. The shared architectural base is Clipper/Five-Like xBase development: `.PRG` source files compile into `.EXE`/`.OBJ`, with `.CH` include files for shared types/constants and `.LIB` files for reusable modules. The repo also preserves the original build toolchains in `CLIPPER5`, `TC`, `C600`, and `BLINKER3`.

3. Data storage is file-based, not database-server based. Most applications use dBASE-style tables (`.DBF`) with memo files (`.DBT`) and indexes (`.NTX`), plus supporting text/config files. Several subsystems store operational history, backups, and export/import feeds as plain files in `DATA`, `ARCHIVE`, `TEST`, and `CENTRAL` folders.

4. The clearest server/client boundary is in `AIM`, where `AIM/SERVER` contains a standalone server executable and setup/media files, while `AIM/TSMS` contains the Clipper application modules and local data tables. That structure suggests a host-driven business application with a separate server process coordinating access to shared records or device/network services.

5. The largest runtime family is the POS line: `POWERPOS`, `PCPOSMTS`, `NEWMTS`, and related backups/dated snapshots. These contain many domain modules for cashiering, item/PLU maintenance, departments, returns, stock transfer, purchase orders, pricing, reports, voids, and end-of-day processing. The data flow is transaction-centric: terminal actions write to local or shared `.DBF` files, then reporting and closing jobs summarize or redistribute those transactions.

6. `PCPOSMTS` is especially explicit about that operational split. It contains compiled modules, source, object backups, and a `TEST/MTSDATA` tree with live-style tables for items, departments, terminals, stock, receipts, returns, and purchase orders. That makes it look like the canonical application package, with `BACKUP` and `OBJ_BACKUP` preserving previous module generations.

7. Hardware integration is a major architectural layer. Across POS and payroll code, there are driver and interface folders for scanners, cash drawers, printers, serial peripherals, keyboards, and displays. `SETUP/DRIVER`, `PENTIUM/DRIVER`, and `POWERPOS/GRAPHICS` show this explicitly, including vendor-specific components such as PFL, Verifone-related code, Epson printer definitions, and custom low-level serial/keyboard support.

8. The payroll/accounting suite lives primarily under `STISYS`, with modules for payroll, general ledger, vouchers, claims, business services, and related subpackages. The layout under `STISYS/STISYS/ARCHIVE/CLIPSYS` and `STISYS/STISYS/PAYROLL` shows a modular domain architecture: each business function has its own executable, maintenance program, and report set, all sharing the same Clipper base libraries.

9. Reporting is a first-class subsystem rather than an afterthought. Many product areas have dedicated `REPORTS*`, `PRINT`, `R_*`, or `REPORTS` modules, often paired with printer abstraction headers. This suggests a workflow where operational transactions are entered in the main app, then periodic reports are generated locally from the same file-based data.

10. There is a strong separation between application logic and infrastructure helpers. Reusable helpers include browse controls, menu systems, gauges, windowing, string/date utilities, locking, file access, memo editing, and printer wrappers. Those helpers appear both as source and prebuilt libraries, indicating shared UI/data-access primitives across all products.

11. Backup and distribution are part of the system design. Many folders contain `BACKUP` trees, dated snapshots, zipped archives, and installation bundles. This implies offline deployment/update workflows typical of DOS networked applications: binaries and data sets are copied as releases, not deployed by centralized runtime packaging.

12. `SETUP` functions as the environment/bootstrap layer. It contains DOS configuration files, network client components, keyboard maps, and application install images. Architecture-wise, this is the boundary between the business application and the machine/network setup needed to run it.

13. `BLINKER3`, `CLIPPER5`, `TC`, `C600`, and `NG` are tooling/support archives, not business subsystems. They provide compilers, linkers, libraries, and memory/overlay utilities required to build the executables in the application folders. An architecture diagram should treat these as build-time dependencies, separate from the runtime application graph.

14. In short, the repository represents a family of tightly coupled, file-based DOS business systems with shared Clipper infrastructure, hardware integration, and report-heavy workflows. The core boundaries are: build toolchain vs runtime app, app logic vs device drivers, and local/shared DBF data vs maintenance/reporting/backup utilities.

Main entry points: [`PCPOSMTS`](https://github.com/ibarrar/clipper/tree/master/PCPOSMTS) (PCPOSMTS app), [`STISYS/STISYS/ARCHIVE/CLIPSYS`](https://github.com/ibarrar/clipper/tree/master/STISYS/STISYS/ARCHIVE/CLIPSYS) (STISYS core), [`CLIPPER5`](https://github.com/ibarrar/clipper/tree/master/CLIPPER5) (Clipper 5), [`AIM/SERVER`](https://github.com/ibarrar/clipper/tree/master/AIM/SERVER) (AIM server)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_tooling["Tooling"]
  node_clipper5["Clipper 5<br/>xBase toolchain"]
  node_tc["Turbo C<br/>C toolchain"]
  node_blinker3["Blinker 3"]
  node_c600["C 6.0<br/>C toolchain"]
  node_ng["NG tools<br/>build scripts"]
end

subgraph group_shared["Shared Base"]
  node_base_libs["Base libs<br/>shared libs"]
  node_clipper_includes["Shared includes<br/>headers"]
end

subgraph group_aim["AIM"]
  node_aim_server[("AIM server<br/>server process")]
  node_aim_tsms["TSMS app<br/>clipper app"]
end

subgraph group_pos["POS Suite"]
  node_pos_core["POS core<br/>pos runtime"]
  node_pos_data[("POS data<br/>file tables")]
  node_pos_graphics["POS graphics<br/>ui/device layer"]
  node_pos_faccess["FACCESS<br/>file access lib"]
  node_pos_reports["POS reports<br/>reporting"]
  node_pcposmts["PCPOSMTS app<br/>pos package"]
  node_newmts["NEWMTS app<br/>pos package"]
end

subgraph group_payroll["Payroll"]
  node_stisys_core["STISYS core<br/>business suite"]
  node_payroll_app["Payroll app<br/>payroll runtime"]
  node_gl_data[("GL data<br/>ledger tables")]
end

subgraph group_setup["Setup"]
  node_setup_drivers["Drivers<br/>peripheral setup"]
  node_setup_net["Net client<br/>network setup"]
end

node_clipper5 -->|"runtime libs"| node_base_libs
node_clipper5 -->|"headers"| node_clipper_includes
node_blinker3 -->|"links"| node_aim_server
node_blinker3 -->|"links"| node_pcposmts
node_tc -->|"compiles"| node_pos_graphics
node_c600 -->|"builds"| node_stisys_core
node_ng -.->|"supports"| node_clipper5
node_setup_drivers -->|"hardware I/O"| node_pos_core
node_setup_net -->|"network boot"| node_pos_core
node_setup_drivers -->|"peripherals"| node_aim_server
node_aim_server -->|"coordinates"| node_aim_tsms
node_aim_tsms -->|"uses"| node_base_libs
node_pcposmts -->|"data access"| node_pos_faccess
node_pos_faccess -->|"reads/writes"| node_pos_data
node_pcposmts -->|"reports"| node_pos_reports
node_pos_reports -->|"summarizes"| node_pos_data
node_pcposmts -->|"ui layer"| node_pos_graphics
node_newmts -.->|"build family"| node_pcposmts
node_stisys_core -->|"shared base"| node_payroll_app
node_payroll_app -->|"books to"| node_gl_data
node_stisys_core -->|"manages"| node_gl_data

click node_clipper5 "https://github.com/ibarrar/clipper/tree/master/CLIPPER5"
click node_tc "https://github.com/ibarrar/clipper/tree/master/TC"
click node_blinker3 "https://github.com/ibarrar/clipper/tree/master/BLINKER3"
click node_c600 "https://github.com/ibarrar/clipper/tree/master/C600"
click node_ng "https://github.com/ibarrar/clipper/tree/master/NG"
click node_base_libs "https://github.com/ibarrar/clipper/tree/master/CLIPPER5/SOURCE/USERLIB"
click node_clipper_includes "https://github.com/ibarrar/clipper/tree/master/CLIPPER5/INCLUDE"
click node_setup_drivers "https://github.com/ibarrar/clipper/tree/master/SETUP/DRIVER"
click node_setup_net "https://github.com/ibarrar/clipper/tree/master/SETUP/NWCLIENT"
click node_aim_server "https://github.com/ibarrar/clipper/tree/master/AIM/SERVER"
click node_aim_tsms "https://github.com/ibarrar/clipper/tree/master/AIM/TSMS"
click node_pos_core "https://github.com/ibarrar/clipper/tree/master/POWERPOS"
click node_pos_data "https://github.com/ibarrar/clipper/tree/master/POWERPOS/081298"
click node_pos_graphics "https://github.com/ibarrar/clipper/tree/master/POWERPOS/GRAPHICS"
click node_pos_faccess "https://github.com/ibarrar/clipper/tree/master/POWERPOS/FACCESS"
click node_pos_reports "https://github.com/ibarrar/clipper/tree/master/PCPOSMTS/REPORTS"
click node_pcposmts "https://github.com/ibarrar/clipper/tree/master/PCPOSMTS"
click node_newmts "https://github.com/ibarrar/clipper/tree/master/NEWMTS"
click node_stisys_core "https://github.com/ibarrar/clipper/tree/master/STISYS/STISYS/ARCHIVE/CLIPSYS"
click node_payroll_app "https://github.com/ibarrar/clipper/tree/master/STISYS/STISYS/PAYROLL"
click node_gl_data "https://github.com/ibarrar/clipper/tree/master/STISYS/STISYS/ARCHIVE/GLDATA/GLDATA"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_clipper5,node_tc,node_blinker3,node_c600,node_ng toneBlue
class node_base_libs,node_clipper_includes toneAmber
class node_aim_server,node_aim_tsms toneMint
class node_pos_core,node_pos_data,node_pos_graphics,node_pos_faccess,node_pos_reports,node_pcposmts,node_newmts toneRose
class node_stisys_core,node_payroll_app,node_gl_data toneIndigo
class node_setup_drivers,node_setup_net toneTeal
```

## Components

### Tooling

Build and development toolchains preserved in the archive.

- [Clipper 5](https://github.com/ibarrar/clipper/tree/master/CLIPPER5): xBase toolchain · Primary Clipper compiler, runtime, and libraries used by the application family. · `CLIPPER5`
- [Turbo C](https://github.com/ibarrar/clipper/tree/master/TC): C toolchain · Borland/Turbo C environment and headers used for low-level modules and utilities. · `TC`
- [Blinker 3](https://github.com/ibarrar/clipper/tree/master/BLINKER3): linker · DOS linker and overlay toolchain archive used to build executables. · `BLINKER3`
- [C 6.0](https://github.com/ibarrar/clipper/tree/master/C600): C toolchain · Microsoft C 6.0 build environment and libraries preserved for legacy components. · `C600`
- [NG tools](https://github.com/ibarrar/clipper/tree/master/NG): build scripts · Additional linker/build configuration archive for Clipper-related builds. · `NG`

### Shared Base

Reusable Clipper infrastructure and support libraries.

- [Base libs](https://github.com/ibarrar/clipper/tree/master/CLIPPER5/SOURCE/USERLIB): shared libs · Reusable Clipper primitives for menus, browsing, screen, locking, printing, and utilities. · `CLIPPER5/SOURCE/USERLIB`
- [Shared includes](https://github.com/ibarrar/clipper/tree/master/CLIPPER5/INCLUDE): headers · Common .CH/.H interface layer shared across applications. · `CLIPPER5/INCLUDE`

### AIM

Server-oriented application with local TSMS client package.

- [AIM server](https://github.com/ibarrar/clipper/tree/master/AIM/SERVER): server process · Standalone server executable plus setup/media assets and master table. · `AIM/SERVER`
- [TSMS app](https://github.com/ibarrar/clipper/tree/master/AIM/TSMS): clipper app · Local Clipper application package with shared data tables, browsing, and reporting. · `AIM/TSMS`

### POS Suite

Point-of-sale application family and its variants.

- [POS core](https://github.com/ibarrar/clipper/tree/master/POWERPOS): pos runtime · Main POS transaction shell, sign-on, terminal flow, and daily operation modules. · `POWERPOS`
- [POS data](https://github.com/ibarrar/clipper/tree/master/POWERPOS/081298): file tables · File-based operational data, transaction feeds, and backups for the POS line. · `POWERPOS/081298`
- [POS graphics](https://github.com/ibarrar/clipper/tree/master/POWERPOS/GRAPHICS): ui/device layer · Graphics and display/rendering helpers plus bitmap and printer-related assets. · `POWERPOS/GRAPHICS`
- [FACCESS](https://github.com/ibarrar/clipper/tree/master/POWERPOS/FACCESS): file access lib · Reusable access layer for clerk, department, item, PLU, return, and FM file handling. · `POWERPOS/FACCESS`
- [POS reports](https://github.com/ibarrar/clipper/tree/master/PCPOSMTS/REPORTS): reporting · Report executables and print-oriented summaries for sales, stock, returns, and accounting. · `PCPOSMTS/REPORTS`
- [PCPOSMTS app](https://github.com/ibarrar/clipper/tree/master/PCPOSMTS): pos package · Canonical POS package with cashier, items, stock, purchase order, and closing modules. · `PCPOSMTS`
- [NEWMTS app](https://github.com/ibarrar/clipper/tree/master/NEWMTS): pos package · Supporting POS maintenance/build package for departments, items, vendors, and security. · `NEWMTS`

### Payroll

Payroll and accounting suite with reports and ledgers.

- [STISYS core](https://github.com/ibarrar/clipper/tree/master/STISYS/STISYS/ARCHIVE/CLIPSYS): business suite · Archive of modular payroll/accounting applications built on shared Clipper base libraries. · `STISYS/STISYS/ARCHIVE/CLIPSYS`
- [Payroll app](https://github.com/ibarrar/clipper/tree/master/STISYS/STISYS/PAYROLL): payroll runtime · Active payroll executable and data package with slips, history, wages, and pay periods. · `STISYS/STISYS/PAYROLL`
- [GL data](https://github.com/ibarrar/clipper/tree/master/STISYS/STISYS/ARCHIVE/GLDATA/GLDATA): ledger tables · General ledger and transaction datasets used by the accounting modules. · `STISYS/STISYS/ARCHIVE/GLDATA/GLDATA`

### Setup

Machine, network, and peripheral bootstrap assets.

- [Drivers](https://github.com/ibarrar/clipper/tree/master/SETUP/DRIVER): peripheral setup · DOS drivers and hardware interfaces for scanners, drawers, LCDs, keyboards, and printers. · `SETUP/DRIVER`
- [Net client](https://github.com/ibarrar/clipper/tree/master/SETUP/NWCLIENT): network setup · Novell client and network boot utilities used by deployed systems. · `SETUP/NWCLIENT`

## Connections

- Clipper 5 → Base libs: runtime libs · Shared Clipper libraries are built from and linked against the core toolchain.
- Clipper 5 → Shared includes: headers · Applications include common Clipper interface definitions and constants.
- Blinker 3 → AIM server: links · Blinker provides linking/build support for executables in the AIM server package.
- Blinker 3 → PCPOSMTS app: links · POS executables are linked with Blinker-based DOS toolchains.
- Turbo C → POS graphics: compiles · Turbo C underpins the graphics and low-level device-support modules.
- C 6.0 → STISYS core: builds · Legacy C components and tool support back the modular STISYS archive.
- NG tools → Clipper 5: supports · NG archives additional linker/build configuration used with Clipper builds.
- Drivers → POS core: hardware I/O · POS runtime depends on local device drivers for scanners, drawers, printers, and displays.
- Net client → POS core: network boot · Deployed POS instances assume network client services and redirectors.
- Drivers → AIM server: peripherals · AIM server setup includes hardware and access integration components.
- AIM server → TSMS app: coordinates · Server process coordinates the TSMS client package and shared record access.
- TSMS app → Base libs: uses · TSMS modules are built on shared browsing, menu, screen, and printer primitives.
- PCPOSMTS app → FACCESS: data access · POS application modules rely on the file-access layer for DBF-style operational tables.
- FACCESS → POS data: reads/writes · FACCESS mediates clerk, item, PLU, return, and related file-based records.
- PCPOSMTS app → POS reports: reports · Operational POS modules feed dedicated reporting programs.
- POS reports → POS data: summarizes · Reports are generated from the same local transaction and master data files.
- PCPOSMTS app → POS graphics: ui layer · POS runtime uses graphics helpers for display, branding, and operator interaction.
- NEWMTS app → PCPOSMTS app: build family · NEWMTS contains supporting maintenance and build modules for the POS family.
- STISYS core → Payroll app: shared base · Payroll runtime shares the same Clipper base architecture as the archived suite.
- Payroll app → GL data: books to · Payroll and accounting modules operate over ledger and transaction tables.
- STISYS core → GL data: manages · The accounting archive includes general-ledger data structures and indexes.
