Exporter UI Refactor [AARD-1883]

[rutmanz]

Task

AARD-1883

Uses Fusion's palette system to make the UI for the exporter a React webpage. Goal is to make the UI cleaner, easier to build on, and not such a pain to update.

Symptom

When you click the exporter button in fusion, you previously saw the old UI. The old UI was difficult to update and very inflexible in its layout.

Solution

• Old ConfigureCommand GUI replaced with a palette, which has all of the same inputs re-implemented using MUI and React
• Uses the Fusion-Web communication protocol to transfer data at key moments
  • When selecting joints and game pieces (Web UI prompts Fusion to allow the user to select an appropriate item in the scene, Fusion returns the selected items)
  • When first opening the panel (Fusion sends calculated robot weight)
  • When exporting (Web UI sends configuration to Fusion and initiates the export process)

Photos

Limitations

• Uses Fusion's internal units (rad/s, cm/s, kg, N) instead of user's unit preferences
  • This isn't a technical limitation, could update to account for that if we think it's important

Verification

• Confirmed that ExporterOptions objects were the same with both the old configuration UI and the new web UI
• Confirmed that saving and loading of config in the document metadata worked
• Confirmed that joint selector and gamepiece selectors allow you to select joints and gamepieces
• Confirmed that models can be imported

---

Before merging, ensure the following criteria are met:

• All acceptance criteria outlined in the ticket are met.
• Necessary test cases have been added and updated.
• A feature toggle or safe disable path has been added (if applicable).
• User-facing polish:
  • Ask: "Is this ready-looking?"
• Cross-linking between Jira and GitHub:
  • PR links to the relevant Jira issue.
  • Jira ticket has a comment referencing this PR.

[autodesk-chorus]

Chorus detected one or more security issues with this pull request. See the Checks tab for more details.

As a reminder, please follow the secure code review process as part of the Secure Coding Non-Negotiable requirement.

[azaleacolburn]

nice work, lgtm!

[PepperLola]

Looks good and worked to export Dozer, I just have a couple nitpicks

[Dhruv-0-Arora]

doesn't seem to be happening on dev for me

[PepperLola]

I think it looks good. For some reason when I add dozer's face to the material tagging table it disappears when I close and reopen the exporter, even though other components (e.g. wheels) stay there. I think it might have something to do with it being linked from another document?

[Dhruv-0-Arora]

When I click the "save" button, I get this error

[rutmanz]

@Dhruv-0-Arora I had that a while ago in testing but thought I fixed it, do you have logs/a way to reproduce?

[Dhruv-0-Arora]

@Dhruv-0-Arora I had that a while ago in testing but thought I fixed it, do you have logs/a way to reproduce?

I wasn't able to reproduce it again. It might have been some problem with the web build that I had done previously although unlikely since I do recall rebuilding the exporter UI (because I had deleted it prior to building it)

[BrandonPacewic]

When I click the "save" button, I get this error

This looks like a bug manifested from Fusion caching stuff. I don't have any evidence for that other than my intuition of working with Fusion's python api.

Like I said before I really should have done this last summer. Looks amazing, nice work.

[BrandonPacewic]

Manually silencing chorus warning:

security/semgrep
app.chorus.semgrep.rules.njsscan.semantic_grep.crypto.node_insecure_random_generator

crypto.pseudoRandomBytes()/Math.random() is a cryptographically weak random number generator.