November 24-25

Monday: 12:55-2:30
Tuesday: 12:55-2:30

   During my two day week this week, I started to code small parts of the app. I started with the calendar feature that would be used for athletics events, lunch schedules, club and school events, etc. It sounded easy enough, but became slightly more complicated when incorporating leap years and the day of the week each month begins on and then using that day to determine which day the next and previous months begin on. I decided to display the calendar by coding a table in HTML to start, but the boxes of the resulting table will probably be too small to hold all of the information we want them to hold. So, I have started thinking about some alternative options. We could code the calendars as a list of the days of the month, which would be scrollable to give as much room as necessary for each month, or we could have each box in the calendar contain a button that would be disabled if there were no events for that day of the month. Each of these buttons would take the user to a page displaying the events on that specific day. The former seems better to me, but it might not be as aesthetically pleasing and I might end up having to scrap all of my code. So, to remedy my indecision, I'll ask the rest of the group for their opinions.During the weekend, we will be meeting with a former student of our club advisor who has experience making apps so that we can get his input on some of the aspects of the app that we don't understand. Hopefully, since we have a long break for Thanksgiving, we will also be able to get together to start working.
     I'm excited that I got to start coding this week! Getting to actually code was very refreshing. It was a really small project that I took on, but I am definitely appreciating the programming aspect of this project rather than the organization side, which can get exhausting. Maybe once we get on a roll, the organization will come more easily.