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

• Yes, I am willing to submit a PR