HiNC App Anatomy
This section is a transparent, per-component anatomy of the HiNC application family — the HiNC-2025-webservice (the current flagship product: Quasar SPA + ASP.NET Core) and the HiNC-2025-win-desktop (the WPF desktop client). Every page dissects one UI component and exposes three layers:
- Layout — the visual / widget tree the user sees.
- Key Model — the backing HiAPI types (MachiningProject, UserService, …).
- Source Code Path — the concrete files (WPF
.xaml+ Quasar.vue+ controller.cs) that implement the component, per application variant.
The sibling General Rules describes conventions shared across the anatomy.
Note
This is not a from-scratch build tutorial. It documents how the shipped HiNC apps are put together, so that:
- End users can understand exactly what each product screen does and which project model each widget edits.
- Developers extending HiAPI-based apps can see a live, production-scale example of every building block mapped to its source.
- AI agents working on the codebase have a single reference for the view ↔ model ↔ source correspondence.
Source Code Repositories
The anatomy covers two codebases in parallel. Each page's Source Code Path section lists the file in each repository that implements the same component.
HiNC-2025-webservice (current flagship)
Quasar CLI SPA (Vue 3 + TypeScript + Pinia + Quasar) served by ASP.NET Core. This is the primary product delivered to end users today.
HiNC-2025-win-desktop
Native Windows desktop client built on WPF.
Architecture Patterns
Cross-cutting patterns referenced by many pages:
- DictionaryService and DictionaryHub Pattern — Connection-scoped object indexing for hierarchical components.
- Rendering Canvas on Web Service — WebSocket / SignalR-based 3D canvas architecture.
Reading Guide
Jump straight to the component you want to understand. Most readers will land here via an in-text cross-link; the sections below are a browsable index of the anatomy.
Core Framework
- Initialize HiAPI — Application startup and HiAPI bootstrap.
- Main Panel — The top-level window / layout shell.
- Message Section — Status and notification bar.
Rendering and Visualization
- RenderingCanvas Tool Bar — 3D view-control toolbar.
- Player Panel — Simulation playback and visualization.
Configuration Panels
- Preference Menu — Application settings entry point.
- Graphic-Cache Dropdown — Graphics caching tuning.
Geometry and Mechanism
- Widget Components — Reusable primitives (Vec3dControl, NumericInput, …).
- Geometry Panels — Geometry creation and management.
- Transformers — Coordinate-transformation editors.
- Fixture Page — Fixture configuration.
- Workpiece Page — Workpiece definition.
- ToolHouse Page — Tool library.
Operation
- Controller Page — CNC controller settings.
- Mission Page — Mission (shell-command sequence) editor.
Reading a Page
Each anatomy page is structured so the reader can pivot between the three layers in a single glance:
- Start at Layout to see the widget tree and understand the user-visible structure.
- Drop down to Key Model to learn which backing type each widget edits; click the
<xref:…>links to open the API reference. - Finish at Source Code Path to open the actual file in each repository. “Web Page Application Source Code Path” is authoritative for the current flagship product; the WPF entry supplies the desktop-client comparison.
Tip
If you are starting a new application on top of HiAPI and want a step-by-step build guide instead, see Getting Started. The anatomy is the reference you keep open while you build; the Getting Started page is the tutorial you follow in sequence.
Note
If you are using an AI agent to make changes across both apps, point it at the specific anatomy page whose component you are editing. Each page intentionally names the WPF and Quasar source files in lock-step so the agent keeps the two in sync.