Skip to content

feat(chess): implement premium board UI, framer-motion drag-and-drop,…#74

Merged
ianmacalinao5 merged 2 commits intomainfrom
TASK-F501/Chess-UI-Components/wacky
Mar 24, 2026
Merged

feat(chess): implement premium board UI, framer-motion drag-and-drop,…#74
ianmacalinao5 merged 2 commits intomainfrom
TASK-F501/Chess-UI-Components/wacky

Conversation

@wendev27
Copy link
Copy Markdown
Collaborator

feat(chess): complete F501 UI overhaul with drag-and-drop and material tracking

  • Built custom responsive chessboard using Tailwind CSS and chess.js
  • Implemented native HTML5 drag-and-drop with Framer Motion physics
  • Swapped text pieces for scalable SVGs with light/dark mode drop-shadows
  • Added material advantage calculation and captured pieces UI
  • Restructured game screen to a centralized, premium Lichess-style layout
  • Refactored game alerts to an always-on status panel
  • Fixed clock initialization to start only after the first move

Swapped text pieces for scalable SVGs with light/dark mode drop-shadows

image image

drag-and-drop with Framer Motion physics

image image

Added material advantage calculation and captured pieces UI

image image

game alerts to an always-on status panel for example king is on check

image image

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest separating the chess types to keep the store cleaner. You could also move the helper code to the utils directory.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks ill be working on it po,currently imm almomst done with the backend rin po ^^ just need to add some exit button

Copy link
Copy Markdown
Collaborator

@ianmacalinao5 ianmacalinao5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested the draggable pieces on my end and everything works well. This should be ready to merge once the suggested changes are addressed.

Nice work!

@wendev27
Copy link
Copy Markdown
Collaborator Author

pushed the updates po. let me know po if there's any more room for improvement ^^
thanks po.

@ianmacalinao5
Copy link
Copy Markdown
Collaborator

pushed the updates po. let me know po if there's any more room for improvement ^^ thanks po.

You can follow din sa next PR mo one of the best practices by applying prefixes sa branch name like fix/, feature/, chore/, and so on.

@ianmacalinao5 ianmacalinao5 merged commit b1ed6ba into main Mar 24, 2026
@wendev27
Copy link
Copy Markdown
Collaborator Author

will do po thanks po

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.

2 participants