Skip to content

Customize OpenMCT UI with crazy styles #8059

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Pruthviraj-sawant
Copy link

Closes

Describe your changes:
This PR introduces creative UI changes and improvements, focusing on vibrant and dynamic visual effects for a more engaging user experience in Open MCT.

Key Changes:

Bold animations: Various UI elements now have smooth, engaging animation transitions, including rotating, flipping, and sliding effects that make the interface more visually dynamic.

Enhanced styles: The design has been updated with bright colors, vivid gradients, and hover effects to create a fun and energetic look, without altering the original class names.

Backgrounds, icons, and buttons have been tweaked to add a modern and interactive feel.

Improved message and alert components: New vibrant styles for message popups and alerts for better user interaction.

These changes are intended to revitalize the interface with a unique and bold aesthetic while maintaining its functionality.

All Submissions:
Have you followed the guidelines in our Contributing document?

Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Is this a notable change that will require a special callout in the release notes? For example, will this break compatibility with existing APIs or projects that consume these plugins?

Author Checklist
Changes address original issue?

Tests included and/or updated with changes?

Has this been smoke tested?

Have you associated this PR with a type: label? Note: this is not necessarily the same as the original issue.

Have you associated a milestone with this PR? Note: leave blank if unsure.

Testing instructions included in associated issue OR is this a dependency/testcase change?

Reviewer Checklist
Changes appear to address issue?

Reviewer has tested changes by following the provided instructions?

Changes appear not to be breaking changes?

Appropriate automated tests included?

Code style and in-line documentation are appropriate?

Copy link

codecov bot commented May 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.24%. Comparing base (573bbb0) to head (96eb8e9).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #8059      +/-   ##
==========================================
- Coverage   57.69%   56.24%   -1.46%     
==========================================
  Files         678      678              
  Lines       27476    27476              
  Branches     2694     2694              
==========================================
- Hits        15853    15454     -399     
- Misses      11282    11679     +397     
- Partials      341      343       +2     
Flag Coverage Δ
e2e-ci 59.55% <ø> (-3.15%) ⬇️
e2e-full 23.61% <ø> (-18.58%) ⬇️
unit 49.21% <ø> (-0.05%) ⬇️

see 45 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 573bbb0...96eb8e9. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant