UI Continuity

[LucaHaverty]

Description

Cleaned up all of the UI and standardized it across the whole product.

Objectives

• Tweak colors to be closer to what's on the figma
• Remove access to the theme editor (sorry Julian, it's very cool but we don't have the time to fix it at the moment 😢)
• Rename everything to be less technical and more accessible to young robotics students
• Add tooltips on settings that users found confusing or misunderstood
• Make UI more dynamic for a more enjoyable user experience (hover effects, click effect, etc...)
• Fix the bug causing a robots scheme to not be set if it was selected while the robot was importing
• Fix the scroll zoom bug

Note

I am not a visual designer and I think there is still a lot of room for improvement, so please comment on anything you think should change, no matter how big or small, both in the UI design and user experience.

Screenshots

(A little has changed since the screenshots were taken so definitely pull down the branch and mess around with it)

Tooltips

Settings Modal

Before	After

Spawn Asset Panel (demonstration of the new colors)

Dynamic UI Demo

Untitled.video.-.Made.with.Clipchamp.5.mp4

Questions for reviewers:

Important

Feedback I'm looking for:

• I'm not a big fan of what I did with the accordion button, let me know if you have better ideas!
• Do you all think the name "configure assets" and "general settings" will make sense to users lacking technical experience?
• Do we want to keep debug tools in the build that is released? If so, we might want to add info tooltips to all of the options.
• Should we keep sequential joints as a separate configuration interface than configuring motor speeds and torques or merge them?
• Any suggestions for the intake, ejector, and scoring zone config panels?

Control scheme bug Jira issue
UI Fixes Jira issue
Info Buttons Jira issue
Scroll Zoom Bug Jira issue

[BrandonPacewic]

Do we want to keep debug tools in the build that is released? If so, we might want to add info tooltips to all of the options.

@HunterBarclay Are we going to have two separate urls up? One for release and one for dev?

If we have two versions up then I think we should add a tag that will remove it from prod builds, if not then perhaps we should just keep it for now.

[a-crowell]

I'm not a big fan of what I did with the accordion button, let me know if you have better ideas!

Yeah something is a little off, but it's hard to tell what. This might be a simple icon change like to a simple arrow (>) instead.

[a-crowell]

🧗

[Dhruv-0-Arora]

yummy

[BrandonPacewic]

@LucaHaverty This PR does not close AARD-1846. I realize that my issue title was definitely too general but the description describes a different problem.

[LucaHaverty]

@LucaHaverty This PR does not close AARD-1846. I realize that my issue title was definitely too general but the description describes a different problem.

@BrandonPacewic You're right. I think that should be addressed in another pr that addresses several other issues caused by the panel system, so I'm removing it from this one.

[BrandonPacewic]

@BrandonPacewic You're right. I think that should be addressed in another pr that addresses several other issues caused by the panel system, so I'm removing it from this one.

Awesome, I absolutely agree, just wanted to make sure that we kept track of the task. Nice work!