Skip to content

Commit dce37cd

Browse files
author
DavidQ
committed
Still organizing look & feel
1 parent 4515f4e commit dce37cd

37 files changed

Lines changed: 1001 additions & 515 deletions

File tree

‎tools/3D Asset Viewer/README.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
Toolbox Aid
2+
David Quesenberry
3+
04/21/2026
4+
README.md
5+
6+
# 3D Asset Viewer
7+
8+
High-level overview for '3D Asset Viewer' under 'tools/3D Asset Viewer/'.
9+
10+
## Purpose
11+
- Provide a focused workspace for this tool's primary authoring/debug workflow.
12+
- Keep output deterministic and compatible with shared Toolbox Aid contracts.
13+
- Integrate cleanly with shared header, workspace lifecycle, and tool navigation.
14+
15+
## What To Expect
16+
- Browser-based tool interface with panel/workspace controls.
17+
- Shared header context and status integration.
18+
- Safe workflows for loading, editing, previewing, and exporting relevant data.
19+
20+
## Entry Points
21+
- Tool UI: 'tools/3D Asset Viewer/index.html'
22+
- How-to guide: 'tools/3D Asset Viewer/how_to_use.html'

‎tools/3D Asset Viewer/how_to_use.html‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
<!DOCTYPE html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="UTF-8" />
5+
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
6+
<title>3D Asset Viewer - How To Use</title>
7+
<link rel="stylesheet" href="../../src/engine/ui/hubCommon.css" />
8+
<link rel="stylesheet" href="../shared/platformShell.css" />
9+
<link rel="stylesheet" href="../../src/engine/theme/main.css" />
10+
</head>
11+
<body class="hub-page-tools tools-platform-surface tools-howto-page" data-tools-platform-page="tool">
12+
<div id="shared-theme-header"></div>
13+
<main class="wrap">
14+
<section class="hero">
15+
<h1>3D Asset Viewer: How To Use</h1>
16+
<p class="subtitle">Detailed workflow with action guidance and why each step matters for day-to-day usage.</p>
17+
</section>
18+
19+
<section class="section">
20+
<h2>Step-by-Step</h2>
21+
<div class="card">
22+
<p><strong>1. Open the tool</strong><br />Action: Open <code>tools/3D Asset Viewer/index.html</code> from Tools index.<br />Why: Tool loads with shared header and ready status.</p>
23+
<p><strong>2. Start a workspace session</strong><br />Action: Use Workspace controls (New/Open) when available.<br />Why: A clean working state is created or loaded for editing.</p>
24+
<p><strong>3. Configure input/settings</strong><br />Action: Set core options (mode, dimensions, source, or filters) for this tool task.<br />Why: Canvas/panels update to reflect the active configuration.</p>
25+
<p><strong>4. Perform edits</strong><br />Action: Use primary controls to create/adjust data in the main workspace.<br />Why: Visible output changes and status reflects latest edits.</p>
26+
<p><strong>5. Validate/preview</strong><br />Action: Use built-in preview, inspection, or validation actions.<br />Why: Errors and warnings are surfaced before export/save.</p>
27+
<p><strong>6. Save/export</strong><br />Action: Save workspace and export artifact/payload as needed.<br />Why: Reusable output is produced for tools, samples, or game flows.</p>
28+
</div>
29+
</section>
30+
</main>
31+
<script type="module" src="../../src/engine/theme/mount-shared-header.js"></script>
32+
</body>
33+
</html>
34+
35+

‎tools/3D Camera Path Editor/README.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
Toolbox Aid
2+
David Quesenberry
3+
04/21/2026
4+
README.md
5+
6+
# 3D Camera Path Editor
7+
8+
High-level overview for '3D Camera Path Editor' under 'tools/3D Camera Path Editor/'.
9+
10+
## Purpose
11+
- Provide a focused workspace for this tool's primary authoring/debug workflow.
12+
- Keep output deterministic and compatible with shared Toolbox Aid contracts.
13+
- Integrate cleanly with shared header, workspace lifecycle, and tool navigation.
14+
15+
## What To Expect
16+
- Browser-based tool interface with panel/workspace controls.
17+
- Shared header context and status integration.
18+
- Safe workflows for loading, editing, previewing, and exporting relevant data.
19+
20+
## Entry Points
21+
- Tool UI: 'tools/3D Camera Path Editor/index.html'
22+
- How-to guide: 'tools/3D Camera Path Editor/how_to_use.html'

‎tools/3D Camera Path Editor/how_to_use.html‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
<!DOCTYPE html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="UTF-8" />
5+
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
6+
<title>3D Camera Path Editor - How To Use</title>
7+
<link rel="stylesheet" href="../../src/engine/ui/hubCommon.css" />
8+
<link rel="stylesheet" href="../shared/platformShell.css" />
9+
<link rel="stylesheet" href="../../src/engine/theme/main.css" />
10+
</head>
11+
<body class="hub-page-tools tools-platform-surface tools-howto-page" data-tools-platform-page="tool">
12+
<div id="shared-theme-header"></div>
13+
<main class="wrap">
14+
<section class="hero">
15+
<h1>3D Camera Path Editor: How To Use</h1>
16+
<p class="subtitle">Detailed workflow with action guidance and why each step matters for day-to-day usage.</p>
17+
</section>
18+
19+
<section class="section">
20+
<h2>Step-by-Step</h2>
21+
<div class="card">
22+
<p><strong>1. Open the tool</strong><br />Action: Open <code>tools/3D Camera Path Editor/index.html</code> from Tools index.<br />Why: Tool loads with shared header and ready status.</p>
23+
<p><strong>2. Start a workspace session</strong><br />Action: Use Workspace controls (New/Open) when available.<br />Why: A clean working state is created or loaded for editing.</p>
24+
<p><strong>3. Configure input/settings</strong><br />Action: Set core options (mode, dimensions, source, or filters) for this tool task.<br />Why: Canvas/panels update to reflect the active configuration.</p>
25+
<p><strong>4. Perform edits</strong><br />Action: Use primary controls to create/adjust data in the main workspace.<br />Why: Visible output changes and status reflects latest edits.</p>
26+
<p><strong>5. Validate/preview</strong><br />Action: Use built-in preview, inspection, or validation actions.<br />Why: Errors and warnings are surfaced before export/save.</p>
27+
<p><strong>6. Save/export</strong><br />Action: Save workspace and export artifact/payload as needed.<br />Why: Reusable output is produced for tools, samples, or game flows.</p>
28+
</div>
29+
</section>
30+
</main>
31+
<script type="module" src="../../src/engine/theme/mount-shared-header.js"></script>
32+
</body>
33+
</html>
34+
35+

‎tools/3D Map Editor/README.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
Toolbox Aid
2+
David Quesenberry
3+
04/21/2026
4+
README.md
5+
6+
# 3D Map Editor
7+
8+
High-level overview for '3D Map Editor' under 'tools/3D Map Editor/'.
9+
10+
## Purpose
11+
- Provide a focused workspace for this tool's primary authoring/debug workflow.
12+
- Keep output deterministic and compatible with shared Toolbox Aid contracts.
13+
- Integrate cleanly with shared header, workspace lifecycle, and tool navigation.
14+
15+
## What To Expect
16+
- Browser-based tool interface with panel/workspace controls.
17+
- Shared header context and status integration.
18+
- Safe workflows for loading, editing, previewing, and exporting relevant data.
19+
20+
## Entry Points
21+
- Tool UI: 'tools/3D Map Editor/index.html'
22+
- How-to guide: 'tools/3D Map Editor/how_to_use.html'

‎tools/3D Map Editor/how_to_use.html‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
<!DOCTYPE html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="UTF-8" />
5+
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
6+
<title>3D Map Editor - How To Use</title>
7+
<link rel="stylesheet" href="../../src/engine/ui/hubCommon.css" />
8+
<link rel="stylesheet" href="../shared/platformShell.css" />
9+
<link rel="stylesheet" href="../../src/engine/theme/main.css" />
10+
</head>
11+
<body class="hub-page-tools tools-platform-surface tools-howto-page" data-tools-platform-page="tool">
12+
<div id="shared-theme-header"></div>
13+
<main class="wrap">
14+
<section class="hero">
15+
<h1>3D Map Editor: How To Use</h1>
16+
<p class="subtitle">Detailed workflow with action guidance and why each step matters for day-to-day usage.</p>
17+
</section>
18+
19+
<section class="section">
20+
<h2>Step-by-Step</h2>
21+
<div class="card">
22+
<p><strong>1. Open the tool</strong><br />Action: Open <code>tools/3D Map Editor/index.html</code> from Tools index.<br />Why: Tool loads with shared header and ready status.</p>
23+
<p><strong>2. Start a workspace session</strong><br />Action: Use Workspace controls (New/Open) when available.<br />Why: A clean working state is created or loaded for editing.</p>
24+
<p><strong>3. Configure input/settings</strong><br />Action: Set core options (mode, dimensions, source, or filters) for this tool task.<br />Why: Canvas/panels update to reflect the active configuration.</p>
25+
<p><strong>4. Perform edits</strong><br />Action: Use primary controls to create/adjust data in the main workspace.<br />Why: Visible output changes and status reflects latest edits.</p>
26+
<p><strong>5. Validate/preview</strong><br />Action: Use built-in preview, inspection, or validation actions.<br />Why: Errors and warnings are surfaced before export/save.</p>
27+
<p><strong>6. Save/export</strong><br />Action: Save workspace and export artifact/payload as needed.<br />Why: Reusable output is produced for tools, samples, or game flows.</p>
28+
</div>
29+
</section>
30+
</main>
31+
<script type="module" src="../../src/engine/theme/mount-shared-header.js"></script>
32+
</body>
33+
</html>
34+
35+

‎tools/Asset Browser/README.md‎

Lines changed: 18 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,22 @@
1+
Toolbox Aid
2+
David Quesenberry
3+
04/21/2026
4+
README.md
5+
16
# Asset Browser / Import Hub
27

3-
Asset Browser / Import Hub is a first-class tools surface for browsing approved project asset locations and generating non-destructive import plans.
8+
High-level overview for 'Asset Browser / Import Hub' under 'tools/Asset Browser/'.
9+
10+
## Purpose
11+
- Provide a focused workspace for this tool's primary authoring/debug workflow.
12+
- Keep output deterministic and compatible with shared Toolbox Aid contracts.
13+
- Integrate cleanly with shared header, workspace lifecycle, and tool navigation.
414

5-
## Phase 1
6-
- Browse approved vector, sprite, tilemap, parallax, palette, and workflow assets.
7-
- Preview SVG and JSON-backed assets.
8-
- Validate local file names against approved import targets.
9-
- Download an import-plan JSON without mutating repo files directly.
15+
## What To Expect
16+
- Browser-based tool interface with panel/workspace controls.
17+
- Shared header context and status integration.
18+
- Safe workflows for loading, editing, previewing, and exporting relevant data.
1019

11-
## Boundary
12-
- This tool is not a general filesystem explorer.
13-
- It does not write directly into the repo.
14-
- It stays aligned to approved platform asset folders and shared tools conventions.
20+
## Entry Points
21+
- Tool UI: 'tools/Asset Browser/index.html'
22+
- How-to guide: 'tools/Asset Browser/how_to_use.html'

‎tools/Asset Browser/how_to_use.html‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
<!DOCTYPE html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="UTF-8" />
5+
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
6+
<title>Asset Browser / Import Hub - How To Use</title>
7+
<link rel="stylesheet" href="../../src/engine/ui/hubCommon.css" />
8+
<link rel="stylesheet" href="../shared/platformShell.css" />
9+
<link rel="stylesheet" href="../../src/engine/theme/main.css" />
10+
</head>
11+
<body class="hub-page-tools tools-platform-surface tools-howto-page" data-tools-platform-page="tool">
12+
<div id="shared-theme-header"></div>
13+
<main class="wrap">
14+
<section class="hero">
15+
<h1>Asset Browser / Import Hub: How To Use</h1>
16+
<p class="subtitle">Detailed workflow with action guidance and why each step matters for day-to-day usage.</p>
17+
</section>
18+
19+
<section class="section">
20+
<h2>Step-by-Step</h2>
21+
<div class="card">
22+
<p><strong>1. Open the tool</strong><br />Action: Open <code>tools/Asset Browser/index.html</code> from Tools index.<br />Why: Tool loads with shared header and ready status.</p>
23+
<p><strong>2. Start a workspace session</strong><br />Action: Use Workspace controls (New/Open) when available.<br />Why: A clean working state is created or loaded for editing.</p>
24+
<p><strong>3. Configure input/settings</strong><br />Action: Set core options (mode, dimensions, source, or filters) for this tool task.<br />Why: Canvas/panels update to reflect the active configuration.</p>
25+
<p><strong>4. Perform edits</strong><br />Action: Use primary controls to create/adjust data in the main workspace.<br />Why: Visible output changes and status reflects latest edits.</p>
26+
<p><strong>5. Validate/preview</strong><br />Action: Use built-in preview, inspection, or validation actions.<br />Why: Errors and warnings are surfaced before export/save.</p>
27+
<p><strong>6. Save/export</strong><br />Action: Save workspace and export artifact/payload as needed.<br />Why: Reusable output is produced for tools, samples, or game flows.</p>
28+
</div>
29+
</section>
30+
</main>
31+
<script type="module" src="../../src/engine/theme/mount-shared-header.js"></script>
32+
</body>
33+
</html>
34+
35+

‎tools/Asset Pipeline Tool/README.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
Toolbox Aid
2+
David Quesenberry
3+
04/21/2026
4+
README.md
5+
6+
# Asset Pipeline Tool
7+
8+
High-level overview for 'Asset Pipeline Tool' under 'tools/Asset Pipeline Tool/'.
9+
10+
## Purpose
11+
- Provide a focused workspace for this tool's primary authoring/debug workflow.
12+
- Keep output deterministic and compatible with shared Toolbox Aid contracts.
13+
- Integrate cleanly with shared header, workspace lifecycle, and tool navigation.
14+
15+
## What To Expect
16+
- Browser-based tool interface with panel/workspace controls.
17+
- Shared header context and status integration.
18+
- Safe workflows for loading, editing, previewing, and exporting relevant data.
19+
20+
## Entry Points
21+
- Tool UI: 'tools/Asset Pipeline Tool/index.html'
22+
- How-to guide: 'tools/Asset Pipeline Tool/how_to_use.html'

‎tools/Asset Pipeline Tool/how_to_use.html‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
<!DOCTYPE html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="UTF-8" />
5+
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
6+
<title>Asset Pipeline Tool - How To Use</title>
7+
<link rel="stylesheet" href="../../src/engine/ui/hubCommon.css" />
8+
<link rel="stylesheet" href="../shared/platformShell.css" />
9+
<link rel="stylesheet" href="../../src/engine/theme/main.css" />
10+
</head>
11+
<body class="hub-page-tools tools-platform-surface tools-howto-page" data-tools-platform-page="tool">
12+
<div id="shared-theme-header"></div>
13+
<main class="wrap">
14+
<section class="hero">
15+
<h1>Asset Pipeline Tool: How To Use</h1>
16+
<p class="subtitle">Detailed workflow with action guidance and why each step matters for day-to-day usage.</p>
17+
</section>
18+
19+
<section class="section">
20+
<h2>Step-by-Step</h2>
21+
<div class="card">
22+
<p><strong>1. Open the tool</strong><br />Action: Open <code>tools/Asset Pipeline Tool/index.html</code> from Tools index.<br />Why: Tool loads with shared header and ready status.</p>
23+
<p><strong>2. Start a workspace session</strong><br />Action: Use Workspace controls (New/Open) when available.<br />Why: A clean working state is created or loaded for editing.</p>
24+
<p><strong>3. Configure input/settings</strong><br />Action: Set core options (mode, dimensions, source, or filters) for this tool task.<br />Why: Canvas/panels update to reflect the active configuration.</p>
25+
<p><strong>4. Perform edits</strong><br />Action: Use primary controls to create/adjust data in the main workspace.<br />Why: Visible output changes and status reflects latest edits.</p>
26+
<p><strong>5. Validate/preview</strong><br />Action: Use built-in preview, inspection, or validation actions.<br />Why: Errors and warnings are surfaced before export/save.</p>
27+
<p><strong>6. Save/export</strong><br />Action: Save workspace and export artifact/payload as needed.<br />Why: Reusable output is produced for tools, samples, or game flows.</p>
28+
</div>
29+
</section>
30+
</main>
31+
<script type="module" src="../../src/engine/theme/mount-shared-header.js"></script>
32+
</body>
33+
</html>
34+
35+

0 commit comments

Comments
 (0)