Small Win32 text editor written in C.
No Electron. No webview. No telemetry.
The tiny builds are live in Releases.
| Build | Size | Role |
|---|---|---|
| DBYTEPAD NANO v0.3.0 | 421 B / 3368 bits | VOID executable, exits immediately |
| DBYTEPAD-1K v0.1.0 | 454 B | size-kill Win32 EDIT core |
| DBYTEPAD Micro v0.1.0 | 1224 B | practical tiny editor: argv open, edit, Ctrl+S save-back |
SIZE LAB: docs/SIZE_LAB.md
Build first. Measure second. Talk third.
build.batOutput:
build\dbytepad.exe
build\dbytepad.exe README.md- Open, save, reload.
- Read-only open.
- Recent files.
- Find and replace.
- Word Wrap.
- Font setting.
- Drag and drop file open.
- File Facts.
- Line, column, char count, and UTF-8 byte count.
- Remembers window size, font, word wrap, and recent files in
dbytepad.ini.
flowchart TD
A[User / command line / drag-drop] --> B[wWinMain]
B --> C[Win32 main window]
C --> D[Menu + accelerators + messages]
D --> E[RichEdit text buffer]
F[Disk file] --> G[read_text]
G --> H[decode: UTF-8 / UTF-16LE / ANSI fallback]
H --> E
E --> I[status + facts]
I --> J[line / column / chars / UTF-8 bytes]
E --> K[save_file]
K --> L[encode UTF-8 + CRLF]
L --> F
E --> M[DByte mode detector]
M --> N[title/status DBYTE marker]
M --> O[DByte Facts]
M --> P{dbyte.exe in PATH?}
P -- yes --> Q[Run DByte / DByte Version]
Q --> R[external dbyte tool]
P -- no --> S[editor still works]
DBYTEPAD knows DByte source files:
.dby.dbyte.dbytercDbyte.toml
When a DByte file is open, the title and status bar show DBYTE.
Tools > DByte Facts works without the DByte tool installed.
Tools > Run DByte and Tools > DByte Version use the external DByte command-line tool when it is in PATH.
DByte mode is optional. DBYTEPAD still opens, edits, and saves DByte source files without DByte installed.
Current release: v1.2.1
Measured build:
- commit: c26cb7f
- exe: 185856 bytes
- source: 1431 lines
- source: 42963 bytes
- sha256:
e45cfbc8997fedf2f6d248144bde683349b873bebd80db594b43c3a174b5432a
Start with docs.
MIT. See LICENSE.
