BetterTimetable

I started with changing the login a little bit. Now you get an error if the username or the password is missing or it’s incorrect.
The main part of this devlog was the bottom bar which will be the way to navigate. Currently I have following buttons: timetable (the main one), customize (where you can customize your timetable), upcoming events (like exams or important things), news (i am not sure about that, maybe a placeholder) and settings (where you can change settings)
I want that if you click on a button, for exampel the settings button, the button should be different (highlight). First I thougt, lets make the texture button change its texture. That seemed like complicated work. But i realized i could set the disabled texture to the highlight texture and then when the button is clicked, the button gets disabled (via code) and therefore is highlighted. yay
for now all the buttons lead to the timetable page, but this will change. The buttons are equally seperated and centered, i am not sure about the thickness though

I implemented the login screen. I made a custom theme for the elements. I am not sure about the theme tho. You can enter the username and password and if the login is succesful, you get redirected to the main page which I’m now working on. I realized I forgot to save new data. I was kinda confused why my login wasn’t saved but now it works. When the username / password is incorrect you get an error message

This devlog covers the first setup, I go with a clean design probably. White background (probably dark mode too) and dark blue as the main color? See the devlog attachment to get a feeling for the design
When starting the app you see a loading screen now. The progress bar is not a 100% real progress bar but it looks cool :) but what really happens: The app checks whether the user is verified / logged in. To do that I added a data saving thingy, writing data to a file to save e.g. the username or later settings. I can easily add it to any scene where I want to access the stored data (it is safely stored on the device, not in the cloud).
Next up is the login screen / func and probably implementig my schools api, we’ll see