Scrum Updated #6

[awctw]

What did you work on this past iteration (2 weeks)? What were any major issues/challenges you ran into? What would you plan to work on for the project in the future (hypothetically)? Name & CSID

[awctw]

Annabelle Wang c1s2b

In the past two weeks I have been working on cleaning up uneeded imports, fixing bugs that appeared in test runs, and revamping the UI. A major issue that we ran into was that sign-up would cause the site to crash sometimes which we discovered was due to the incorrect formatting of when storing to session storage. Some possible improvements in the future I would like to add would be gamification to the website, this was originally one of our stretch goals. I would love to see users having their own levels and gain experience as they study more.

[HeinzUBC]

CS ID: r4e1b Peter

1. What did you work on this past iteration (2 weeks)?

During the past iteration, I have done mostly debugging work on my TODOList module.

• Fixed the Calendar view of TODOList so that the TODOs icon added to a calendar date tile does not mess up the date tile's content formatting
• Fixed the Calendar view of TODOList so that if a user selects a date tile and then un-selects it, the "selection colour" applied to that date tile is removed
• Fixed TODOs icon colour so that it turns green if all TODOs for a given date tile are marked as finished; icon turns red if at least some TODOs for the same date tile are marked as pending

2. What were any major issues/challenges you ran into?

The main challenge was learning to remove the "selection colour" applied to a given date tile when a user un-selects that tile. The issue was that the CSS styles that I needed to adjust was not well documented by react-calendar. It was a learning curve, but I was able to successfully reference examples online to figure out how to fix the issue.

Another challenge was figuring out how to position the TODOs icon to the top-right corner of a given date tile. That was difficult, cause react-calendar has no documentation on how to do this. Through referencing other resources, I figured out how to apply the correct CSS styles to both the date tile and icon to make them work.

3. What would you plan to work on for the project in the future (hypothetically)?

For the most part, the TODOList module is essentially complete.

I plan to help modify the firebase config files with Kush so that StudyDash can be compatible with firefox.

[AlanZhangDev]

Name: Alan Zhang csid: g2e2h

In the past iteration, I worked on developing the habits module further, including creating the habit heat map tracker. The major issue I faced was getting the habits to persist and store the dates the user selected. This was because on deployment, the server clock could be different than the client's, which I did not keep track of, and it was not present when locally run. However, I managed to fix this by using UTC time. Hypothetically in the future, I would work on further developing the habits module so that you would be able to edit the habits as well as see statistics on your habits.

[kush458]

Name: Kush Arora csid: l8i3b

In the past iteration, I worked on overhauling our app's UI and fixing multiple bugs that we encountered. One major hurdle that we ran into was that a user would receive duplicate notifications for a single message and that was happening because a controller that was responsible for storing a chat message and sending notifications was being called twice - once on the receiver's end and once on the sender's end. As for some hypothetical future improvements, I would further work on refining our group chats feature to allow sharing of resources (eg: todos, flashcards etc) and maybe also improve our flashcards feature so that users also have the option to import data and automatically generate flashcards.

[leungkenneth]

Name: Kenneth Leung csid: c4o1b

This past iteration I worked on ironing out the remaining issues with the Gantt Chart (e.g. overwriting conflicting styling that only appeared on deployment) and refactoring its code to use the new 'Color' property added to Categories. I also performed code cleanup of commented out code, unused variables, logs, etc. One challenge I ran into was in the timing of code cleanup merges as indentation and code style changes caused massive conflicts with my Gantt Chart code and code changes after my own cleanup efforts meant that the they needed to be repeated again on the changed files. If I were to keep working on the project, I would work on Category integration into Habits (so that Habits could be associated with a color and category) and pursue our stretch goal of gamification so that StudyDash would be more unique compared to other study aids.