Rename SolveCraft to SolidCraft everywhere, with compatibility shims (#389)
* WIP deep rename (not for push) * WIP2 * WIP3 * WIP4 wxs fix * rustfmt * Rename the remaining identifiers in merged crash-report code Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RjGw4gA5ZvKrU8MQP6sBgT --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
27415e4dd7
commit
296683229d
464 files changed
+3408
-2956
No files matched your search
@@ -1,13 +1,13 @@
|
||||
#!/usr/bin/env python3
|
||||
"""Demo v2/v3: build an electronics enclosure in a running SolveCraft the way a person would,
|
||||
"""Demo v2/v3: build an electronics enclosure in a running SolidCraft the way a person would,
|
||||
with the parametric steps sent over MCP.
|
||||
|
||||
--story v3 (default): one standoff placed from the parameters and patterned 2 x 2 in the
|
||||
Rectangular Pattern dialog, then width and wall changed in the Parameters dialog.
|
||||
--story v2: four standoffs from one sketch, then the width changed over MCP.
|
||||
|
||||
solvecraft --control 7878 &
|
||||
python3 examples/demo/enclosure_ui_mcp.py --port 7878 --cli solvecraft-cli [--story v2|v3]
|
||||
solidcraft --control 7878 &
|
||||
python3 examples/demo/enclosure_ui_mcp.py --port 7878 --cli solidcraft-cli [--story v2|v3]
|
||||
|
||||
Modelling steps go through the app's UI over its control channel: the pointer glides to a
|
||||
toolbar button and clicks it (the real dialog opens), glides to the face or point it picks and
|
||||
@@ -15,7 +15,7 @@ clicks, and values are typed into the dialog, as by hand. The port and boss sket
|
||||
directly to the enclosure's side face and inner floor, as in the original demo.
|
||||
The camera follows like a user's would (Look At on a new sketch, back out to a 3/4 view on
|
||||
Finish Sketch, a little orbit between features). The parameters and the dimensions that use them
|
||||
are MCP `execute` calls through `solvecraft-cli mcp --connect` (enclosure_mcp.py's client).
|
||||
are MCP `execute` calls through `solidcraft-cli mcp --connect` (enclosure_mcp.py's client).
|
||||
|
||||
--log writes one JSON line per caption and per pointer event, which record.sh turns into burnt-in
|
||||
captions and a drawn cursor (the app gets synthetic pointer events, so the screen's own pointer
|
||||
@@ -398,7 +398,7 @@ def run_v3(d):
|
||||
def main():
|
||||
ap = argparse.ArgumentParser(description=__doc__.splitlines()[0])
|
||||
ap.add_argument("--port", type=int, default=7878, help="the app's --control port")
|
||||
ap.add_argument("--cli", default="solvecraft-cli", help="path to solvecraft-cli")
|
||||
ap.add_argument("--cli", default="solidcraft-cli", help="path to solidcraft-cli")
|
||||
ap.add_argument("--log", help="write a JSON line per caption and pointer event")
|
||||
ap.add_argument("--story", choices=["v2", "v3"], default="v3", help="v2: standoffs from one sketch, width over MCP; v3: one standoff patterned, Parameters dialog")
|
||||
ap.add_argument("--until", type=int, default=10**6, help="stop before step N (trying the script out)")
|
||||
|
||||
Reference in new issue
Block a user