Skip to content
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

Migrate Raw CSS to Tailwind CSS for Better Responsiveness #59

Open
1 of 17 tasks
naman9271 opened this issue Feb 15, 2025 · 3 comments · May be fixed by #71
Open
1 of 17 tasks

Migrate Raw CSS to Tailwind CSS for Better Responsiveness #59

naman9271 opened this issue Feb 15, 2025 · 3 comments · May be fixed by #71

Comments

@naman9271
Copy link

naman9271 commented Feb 15, 2025

Issue: Migrate Raw CSS to Tailwind CSS for Better Responsiveness

Description

The current UI implementation in GDB-UI is not responsive, as it relies on raw CSS instead of a utility-first framework. This results in inconsistent styling, lack of scalability, and poor adaptability to different screen sizes.

Proposed Solution

  • Migrate all existing raw CSS styles to Tailwind CSS.
  • Utilize Tailwind’s utility classes to ensure a fully responsive design.
  • Improve consistency in spacing, typography, and layout across different screen sizes.
  • Remove unnecessary CSS files and streamline the styling approach for better maintainability.

Expected Benefits

  • Enhanced responsiveness, making the UI adaptable to various devices.
  • Faster development and easier maintenance with Tailwind’s utility-first approach.
  • Improved user experience with a cleaner and more modern design.

This migration will significantly improve the UI quality and maintainability of the GDB-UI project. Let me know if any modifications are required!


Migration Plan: Raw CSS to Tailwind CSS

Phase 1: Setup and Initial Migration

  • Set up Tailwind CSS in the project.
  • Migrate basic layout components:
    • Header
    • Footer
    • MainScreen
  • Ensure that the basic structure is responsive.

Phase 2: Component Migration

  • Migrate GDB components to Tailwind CSS:
    • GdbComponents
    • Threads
    • BreakPoints
    • LocalVariable
    • MemoryMap
  • Ensure that each component is fully responsive and maintains functionality.

Phase 3: Cleanup and Final Adjustments

  • Remove all unused CSS files and styles.
  • Conduct thorough testing across different devices and screen sizes.
  • Make any necessary adjustments to ensure consistency and responsiveness.

You can see UI is not responsive at all

20250215-2142-40.3381486.mp4

  • Yes, I am willing to submit a PR
@naman9271
Copy link
Author

hey @Shubh942 @Niweera @sonodew please assign this issue or review it so i start working upon this

@naman9271
Copy link
Author

@Shubh942 do you need these change ??

@naman9271
Copy link
Author

naman9271 commented Feb 22, 2025

@Shubh942 i have make the migration plan for this and i am thinking to raise a PR for each phase and as the each PR will getting merge so it will getting tested the changes

  • Kindly review it and tell me if you need some change in this

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