Overview of libraries¶
This page is the library index. For the four-tier model, the dependency rule, and how host apps stay system-agnostic via plugin discovery, see Architecture.
Tier 1 — Core libraries¶
UI-agnostic, system-agnostic. The 6502 CPU emulator itself, the abstractions for emulated systems, the plugin contracts + discovery, and supporting libraries (monitor, scripting, debug adapter, remoting, AI). Run anywhere .NET runs.
→ Per-library reference and dependency layering
Tier 2 — System-specific core libraries¶
The "computer" layer — implements ISystem for a specific machine using the core
libraries. Still UI-agnostic.
- Commodore 64 —
Highbyte.DotNet6502.Systems.Commodore64 - VIC-20 —
Highbyte.DotNet6502.Systems.Vic20 - Apple II Plus —
Highbyte.DotNet6502.Systems.Apple2 - Oric Atmos —
Highbyte.DotNet6502.Systems.Oric - Generic —
Highbyte.DotNet6502.Systems.Generic
Tier 3 — Implementation libraries¶
Bind a system to a UI / render / input / audio technology. Each tier-3 technology is split in two:
Impl.<Tech>— host-technology glue that is system-agnostic (e.g.Impl.Avalonia,Impl.NAudio).Impl.<Tech>.<System>— per-system engine-plugin libraries (e.g.Impl.Avalonia.Commodore64,Impl.SilkNet.Generic). Each ships anISystemEnginePluginregistering that system for that host.
→ App-by-library matrix showing which implementation libraries each desktop and web app consumes.