Scrum Report 5

[MattWanJH]

Include your INITIALS (that match your Canvas name) in your post (so we can give you a grade!) Answer 3 questions:

• What did you work on this past iteration (2 weeks)?
• What were any major issues/challenges you ran into?
• What do you plan to work on for this coming iteration (2 weeks)?

Other

• These are individual, so you are tracking your OWN work
• Can use this as a resource when you’re writing about your project on your resume or LinkedIn -> look back and remember details about implementation
• We are having this due AFTER each workshop so that you are better able to understand the technology you’re going to be using
• The real effort comes from talking to your group and planning your next steps!
• Keep it short, succinct, and summarize the key points

[MattWanJH]

Matthew Wan MW

1. This past iteration, I worked on generating and storing thumbnails, refactoring our database / endpoints to save all the new scene information we have now, and enhancing the user flow by being able to create new scenes through the editor page.
2. One of the tricky issues we ran into while working on the project was that thumbnails and downloading images were being generated with a black background when the background was specified with white on Firefox browsers. The reason this happened was that Firefox interprets a white canvas as transparent which it then renders transparent as black, so we had to instantiate a white background when generating base64 images.
3. For the coming iteration, I hope to be working on making the main landing page more user friendly and updating the tutorial page to be in depth for any new user. I will also help with linking the user page to the editor, the newly generated scenes should save to that user's account.

[AidenKerr]

Aiden Kerr AK

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

• Streamlined ability to add new shapes by designing configurable shape data config
• Added matrix transformations, allowing for new transformations like rotation.
• Added users page
• Page deployment w/ Render.com and Github actions

What were any major issues/challenges you ran into?

• Lots of weird things w/ deployments. For example, page navigation didn't work properly on the deployed version. Needed to change settings on render.com for that. Also, login worked differently on the deployed version.
• Getting the Editor to work with matrices and also save the correct info on the DB was interesting...

What do you plan to work on for this coming iteration (2 weeks)?

• Add a live gOOpy scene to the main page
• Update documentation
• General cleanup and presentation preparation
• Maybe: Camera controls

[sl-81]

Shiyu Li - SL

1. For this past iteration I worked on implementing user login authentication using OAuth2 and a user session so that the user's work can persist upon refresh/browser closing. I've also implemented endpoints to fetch user data from the frontend and integrated it into our frontend
2. The trickiest issue was the implementing of user sessions and figuring out how to store session data, and tweaking with the proxy and cookie settings of our backend so that the user session can persist and the frontend can retrieve the information of the logged in user at any time.
3. For our last iteration I plan to be working on styling changes and optimizing the frontend and user workflow. As well as overall project cleanup including removing console logs and auditing todos

[jlacsamana]

Jacob Lacsamana - JL

1. For this past iteration, I worked on resolving some extant style issues with the editor UI, improving its responsiveness. I also reworking some routes on our back-end to allow users to save scenes to their account properly, and integrated that functionality with the frontend.
2. The trickiest issue was working through the CSS styling issues. It was a challenge debugging the effects on different parts of the scene styling changes would have.
3. For the last iteration I plan to continue working on both parts of the stack to extend functionality of routes and integrate the new functionality with the frontend.