University-of-Basel-Studentprojects/Programmierprojekt
Archived
1
0
Fork 0
Code Issues 17 Pull Requests Actions Wiki Activity

Lobby UI – Display Lobby Status and Update Button Images #36

New Issue
Closed
opened 2026-04-01 13:17:25 +02:00 by jona.walpert · 6 comments
jona.walpert commented 2026-04-01 13:17:25 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

Task

Summary

  • Implement lobby status handling in the Lobby UI so each lobby button shows one of two images depending on its current state (CREATED or RUNNING). Add a status‑query function (currently a placeholder that returns a random status), a helper to map statuses to image resource paths, and a method to refresh all button images based on the latest statuses.

Context

  • Component: User interface – Lobby / Lobby Button Grid.

Current Progress

  • planned
  • started
  • testing
  • finished

Notes

Checklist

  • I outlined checkpoints describing phases of my work related to this task
  • I added relevant labels
  • I linked to other issues or branches that must be completed first
## Task <!--The reccommended type is: Task--> ### Summary * Implement lobby status handling in the Lobby UI so each lobby button shows one of two images depending on its current state (CREATED or RUNNING). Add a status‑query function (currently a placeholder that returns a random status), a helper to map statuses to image resource paths, and a method to refresh all button images based on the latest statuses. ### Context * Component: User interface – Lobby / Lobby Button Grid. <!--Examples: Networking, Game-Engine, User interface, ...--> ### Current Progress - [x] planned - [x] started - [ ] testing - [ ] finished ### Notes <!--Optional: Implementation hints, links to prior design discussions, etc.--> ### Checklist - [x] I outlined checkpoints describing phases of my work related to this task - [x] I added relevant labels - [x] I linked to other issues or branches that must be completed first
jona.walpert commented 2026-04-01 13:17:25 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

changed start date to April 01, 2026 and changed due date to April 04, 2026

changed start date to April 01, 2026 and changed due date to April 04, 2026
jona.walpert commented 2026-04-02 22:02:05 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

marked the checklist item started as completed

marked the checklist item **started** as completed
jona.walpert commented 2026-04-02 22:28:16 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

mentioned in commit 42b5344059

mentioned in commit 42b53440593ead1e74000170631d0a4dcb35e768
jona.walpert commented 2026-04-09 13:35:14 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

coding finished. Testing will be done in the future when the backend is fully implemented.

coding finished. Testing will be done in the future when the backend is fully implemented.
jona.walpert commented 2026-04-13 03:02:35 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

mentioned in merge request !126

mentioned in merge request !126
jona.walpert commented 2026-04-13 03:07:54 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

mentioned in commit 6f345cc51e

mentioned in commit 6f345cc51ed22f55a9d35c5e26253e86f1a99845
jona.walpert (Migrated from git.scicore.unibas.ch) closed this issue 2026-04-13 03:13:00 +02:00
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
achievement
Tasks related to milestone achievements
 bug
Issues related to programming errors on both client and server
 ci
Issues related to problems with the gitlab ci (incorrect or missing jobs)
 client
Issues (To-Dos and tasks) related to the client
 commands
Issues and tasks related to commands and thier infrastructure (CommandHandler, CommandParser, ...)
 documentation
Issues related to the documentation (for new or unclear, incorrect or incomplete entries)
 enhancement
Issues related to enhancements (also known as feature-requests)
 game-engine
Issues related to the game engine (incorrect state transitions or move validations)
 linting
Issues related to linting i.e. false detections, too generous linting, ...
 messages
Issues and tasks related to the messages and chats
 network
Issues and tasks related to the network (SessionReader / SessionWriter, Parser, ResponseBody, ...)
 outreach
Issues and tasks related to the outreach website and everything directly related to it
 server
Issues (To-Dos and tasks) related to the server
 task
Issues outlining and discussing a general task or implementation
 templates
Issues related to GitLab templates
 ui
Issues and tasks related to the client-side ui
 unit-test
Issues related to missing or already planned unit tests
 user
Issues and tasks related to the user management
No Label client task
Milestone
No items
No Milestone Milestone 4
Assignees
Clear assignees
lars-winzer (Lars Winzer)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: University-of-Basel-Studentprojects/Programmierprojekt#36
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?