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

Select and lock a specific lecture or tutorial time #26

Open
zac-k-03 opened this issue Feb 2, 2025 · 0 comments
Open

Select and lock a specific lecture or tutorial time #26

zac-k-03 opened this issue Feb 2, 2025 · 0 comments

Comments

@zac-k-03
Copy link
Collaborator

zac-k-03 commented Feb 2, 2025

As a student, I want to be able to select and lock a specific lecture or tutorial time so that it doesn’t change in new schedules.

• UI Interaction:
	○ Provide a clear control (e.g., a “lock” button or checkbox) next to each lecture/tutorial option in the schedule view.
	○ Allow users to click on a specific class section to mark it as "locked."
	○ Confirm the action with a visual cue (e.g., a color change or lock animation).
• Data Persistence:
	○ Store the locked status of the selected class section in the user’s profile or session data.
	○ Ensure that the locked status is retained across sessions (if applicable) and visible when the user revisits the timetable.
• Algorithm Integration:
	○ When generating new timetables, incorporate locked sections as fixed constraints.
	○ The scheduling algorithm must preserve all locked sections and only modify unlocked sections.
• Testing & Validation:
	○ Verify through unit tests that when a section is locked, it remains unchanged during schedule regeneration.

Simulate multiple schedule generations to ensure locked sections are consistently maintained.

@zac-k-03 zac-k-03 converted this from a draft issue Feb 2, 2025
@zac-k-03 zac-k-03 moved this to Todo in BetterTimetable Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant