deploy.

App/wwwroot/HiAPI-docsite/anatomy/execution/mission/NcFileCommand-panel.html

@@ -97,9 +97,8 @@ into the project itself.</p>
 and an absolute path on the server is accepted just as well. No base directory is stored with the
 command: at play time <a class="xref" href="../../../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_RunNcFile_">RunNcFile</a> hands the stored path
 together with the project's own base directory to the local project service, and that is where a
-relative path acquires its root. The WPF panel's <code>BaseDirectory</code> is the code-behind assistant
-property the <a class="xref" href="../../conventions/gui-file-path-assignment.html">Load Pattern</a> asks a file-assigning GUI to carry,
-assigned to the panel by its parent — a panel member, not a model member.</p>
+relative path acquires its root; the convention behind it is the
+<a class="xref" href="../../conventions/gui-file-path-assignment.html">Load Pattern</a>.</p>
 <p>The panel renders on the command's own node in the Mission branch of the Execution page's Control
 Tree, below the move / duplicate / delete control bar. This command has no title of its own, so the
 row and tree label read <code>Program File [path]</code>, the path being the detail the label brackets.</p>
@@ -124,8 +123,7 @@ as CSV, and every other extension as brand NC).</p>
 the project folder.</li>
 <li>Every keystroke saves the path. Leaving the field or pressing Enter additionally refreshes
 the file-info banner.</li>
-<li>The web field flexes to fill the row beside the Browse button at any panel width; the WPF
-field is a fixed 200 px column carrying its own label.</li>
+<li>The field flexes to fill the row beside the Browse button at any panel width.</li>
 </ul>
 </li>
 <li>Browse Button
@@ -140,8 +138,6 @@ field is a fixed 200 px column carrying its own label.</li>
 <li>The model is <a class="xref" href="../../../api/Hi.SessionCommands.NcFileCommand.html#Hi_SessionCommands_NcFileCommand_NcKind">NcKind</a>.</li>
 <li>Four choices: Auto (by extension), Brand NC, CL (CLSF) and CSV. The hint restates what Auto
 detects, so the runner can be pinned when the extension would route the file elsewhere.</li>
-<li>This control is the web client's. The WPF panel ships no kind control, so a project edited
-there keeps the kind it already holds — Auto until something else sets it.</li>
 </ul>
 </li>
 <li>File Info Banner
@@ -180,9 +176,6 @@ browser to preserve. It is the backstop for a brand extension the NC group does
 </ul>
 <p>CL and CSV are split out because they are closed extension sets: those are exactly the extensions
 Auto routes to the CL and CSV runners, and everything else falls through to brand NC.</p>
-<p>The WPF Browse button opens an <code>OpenFileDialog</code> with the panel's file-filter resource, starting at
-the project directory or at the current file's own directory. A pick under the project directory is
-stored as a relative path, and a pick outside it as an absolute one.</p>
 <h2 id="multi-pick-fan-out">Multi-Pick Fan-Out</h2>
 <p>The dialog is multi-select, and this is the one command editor that grows the mission. The first
 picked file lands on this command. Each further pick becomes a <strong>new</strong> Program File command, added
@@ -191,18 +184,9 @@ list, so a command inside a nested list fans out inside that nested list. The pa
 structure change, which rebuilds the owning list's branch around the new rows and leaves the
 selection on this command.</p>
 <h2 id="where-the-program-text-is-edited">Where the Program Text Is Edited</h2>
-<p>The two clients part company here, and the command is the same either way: it stores a path.</p>
-<ul>
-<li><strong>Web</strong> — the panel does not edit the file. It assigns the path, picks the runner, reports what
-the server knows about the file, and previews its first 100 lines read-only. Nothing in the
-browser writes NC bytes back; the two file endpoints this panel calls are both reads.</li>
-<li><strong>WPF</strong> — the panel opens the file. A non-text file, or one the panel cannot find, disables the
-editor and states why in the Head Message Place above it. A text file within 20000 lines opens for
-editing, with its line count in the group-box header; a longer one shows its first 20000 lines
-read-only and warns in the Head Message Place. Two seconds after the last keystroke the editor
-writes the file back, and reports the save in that same message place. The editor is AvalonEdit
-with line numbers where that assembly resolves, and a plain Consolas text box otherwise.</li>
-</ul>
+<p>The command stores a path, and the panel does not edit the file. It assigns the path, picks the
+runner, reports what the server knows about the file, and previews its first 100 lines read-only.
+Nothing in the browser writes NC bytes back; the two file endpoints this panel calls are both reads.</p>
 <h2 id="source-code-path">Source Code Path</h2>
 <p>See <a class="xref" href="../../index.html">HiNC App Anatomy</a> for git repository links.</p>
 <h3 id="web-application">Web Application</h3>