Client meeting and other things

We had another client meeting yesterday and I think that it went fairly well. We had a demo working so I think this helped a lot since it shows what we've accomplished as well as what we still have to work on. Prof. Ackley brought up some good points, which Fernando put down in a Google doc so we can reference them. One of the suggestions was to change the Success button to be called "Check-in" since this is the term we had been using everywhere else so it made more sense. Fernando and I will also need to add some sort of confirmation modal or popover to the Check-in button so that the user can confirm that they really want to check-in, which should help prevent accidental check-ins on the part of the user. Or, we could figure out a way to "undo" an accidental check-in (one way would be to use the Paper Trail plugin).

This weekend, we plan to have a group meeting to start working on and (hopefully) implementing so basic overall design concepts (color, layout, etc.) so we can have some these for the next client meeting. Have a website that looks appealing, is easy to use, and is fully functioning is going to be very important for the final demo. We have most of the functionality complete so design will be our main focus over the next several weeks.

Fernando and I were able to get the check-in timing/verification mostly complete. The code now allows the user to check-in at any time on the first day of the current week (which is especially important if the challenge has 7 check-ins since, otherwise, the user would not be able to complete all the checkins before the week is up). The code also allows, at most, one check-in per 24 hours since the maximum number of check-ins per week is 7 (which was a design decision on the part of our team). This new code is working with the code that we had added last week, which will have the user retake a week if they miss one or more check-ins for that week. This code was modified slightly to fix a bug that was creating the "redo" week with a start date equal to the end date of the previous week. This was a problem if the user missed some check-ins for a given week and then completely missed the next week. It was also a problem if they had to do 7 check-ins for the week because then they would be "cheated" out of time or else the redo week's start and end times would have already passed if they had missed an entire extra week. Thus, the redo week is now created with a start date equal to the current time to avoid these problems.