HiNC-Deploy/HiNC-2025-win-desktop-Deploy
Archived
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

deploy.

Browse Source
This commit is contained in:
iamboss
2026-09-12 18:16:27 +08:00
parent b7f55aa631
commit 397a7a8cc4
96 changed files with 1167 additions and 1259 deletions
Download Patch File Download Diff File Expand all files Collapse all files
App/wwwroot/HiAPI-docsite/anatomy/index.html
+5 -17
View File
@@ -131,10 +131,6 @@ regroup adds a migration hop. The ids themselves have moved repeatedly.</p>
<td><a href="tool-house/index.html">Tool House Page</a></td>
</tr>
<tr>
<td><code>/controller/:tab?</code></td>
<td><a href="legacy-controller.html">Legacy Controller</a></td>
</tr>
<tr>
<td><code>/util/file-explorer</code>, <code>/util/mech-builder</code></td>
<td><a href="util/index.html">Utility Pages</a></td>
</tr>
@@ -174,23 +170,16 @@ regroup adds a migration hop. The ids themselves have moved repeatedly.</p>
<li><a href="execution/index.html">Execution Page</a> — The run cockpit: its tool bars, the step column, the charts, and the Mission branch it hosts</li>
<li><a href="general-setup/index.html">General Setup Page</a> — The equipment Control Tree: the machine, the spindle envelope, the scene, the fixture, the workpiece and the controller branch</li>
<li><a href="tool-house/index.html">Tool House Page</a> — The tool library and the per-tool editor tabs, cutter and holder</li>
<li><a href="legacy-controller.html">Legacy Controller</a> — The superseded HardNcEnv controller surface and its REST implementation</li>
<li><a href="legacy-controller-settings.html">Legacy Controller Settings</a> — The HardNcEnv model that surface edits: the three settings it owns alone, what it shares with the Controller branch, and the engine files behind both</li>
<li><a href="legacy-controller-settings.html">Legacy Controller Model (HardNcEnv)</a> — The deprecating HardNc controller model the project still carries beside the runner: what the live pipeline still reads from it, the three settings that retire with it and the Align P0 action the runner path does not offer, what the Controller branch edits a runner-side copy of, and the engine files behind both</li>
<li><a href="util/index.html">Utility Pages</a> — The two <code>/util/</code> routes: the File Explorer and the Mechanism Builder</li>
<li><a href="by-source/index.html">By Source Directory</a> — The same knowledge keyed on the source tree instead of the screen: one directory index per half of the flagship</li>
</ul>
<h2 id="the-two-codebases">The Two Codebases</h2>
<p>A page's <em>Source Code Path</em> section lists the files that implement it in the flagship web service.
The desktop client's counterparts are not listed at all: it takes no new feature work, and a
hand-maintained map of its files went stale faster than anyone read it. The two codebases are not
peers.</p>
<h2 id="the-codebase">The Codebase</h2>
<p>A page's <em>Source Code Path</em> section lists the files that implement it in the flagship web service,
which is the only application codebase Anatomy documents.</p>
<p><strong>HiNC-2025-webservice</strong> is the flagship — a Quasar SPA (Vue 3 + TypeScript + Pinia) served by
ASP.NET Core, and the only target for new feature work. Repository:
<a href="https://superhightech-gitea.webredirect.org/HiAPI/HiNC-2025-webservice.git">HiNC-2025-webservice.git</a></p>
<p><strong>HiNC-2025-win-desktop</strong> is the outgoing WPF client, kept here only so a reader familiar with the
desktop UI can find the equivalent web-service component. Do not start new work against it.
Repository:
<a href="https://superhightech-gitea.webredirect.org/HiNC-Deploy/HiNC-2025-win-desktop.git">HiNC-2025-win-desktop.git</a></p>
<div class="TIP">
<h5>Tip</h5>
<p>The host process, its configuration and the address it listens on are documented in
@@ -204,8 +193,7 @@ Control Tree, its <code>?tree=</code> id. Make no claim that the id is stable.</
<li><strong>Key Model</strong> — the backing HiAPI types, as <code>&lt;xref:&gt;</code> so the API reference is one click away.</li>
<li><strong>Source Code Path</strong> — the implementing files <strong>in the web service</strong>. Backtick every path, with
its extension: <code>tools/check-source-paths.ps1</code> resolves a full path against the source tree and a
bare file name by its base name, and refuses an entry carrying no backticks at all. Do not add
desktop-client files.</li>
bare file name by its base name, and refuses an entry carrying no backticks at all.</li>
<li><strong><code>## See Also</code></strong> — mandatory, and audited for reciprocity. An entry is not landed until the
target links back.
Anatomy is <strong>authoritative</strong> on component and source facts: when Manual and Anatomy disagree,