Repository navigation
Team Viewer Meeting Minutes
Template:
Attendance: <people’s names>
Absent: <people’s names>
Note taker:
Notes:
Action items: <bullet points on what you will do, ideally linked to issues>
Attendance: DallaliRim, YehJordan, benjaminsunliu, Nolan, JenLys
Absent: NONE
Note taker: JenLys
Notes:
- For the first iteration, the team has planned to learn PixiJS since none are familiar with it and document it on the side to make it simpler for future project collaborators to follow along and be able to advance Rena Engine
- The way the rendering works has also been discussed:
PixiJS works well with React, there's this component of PixiJS called Canvas--> this will hold the rendering.
In total, our team will have 2 Viewers: the Live Viewer (aka Standard Viewer) and the Playback Viewer.
At the start, we fetch the information about the game's setup, its texture, etc to render it to all participants linked to that game (Live Viewer)
The Live viewer is there for the participant to test out their code against the hosts' pre-coded agent. We take the actions from the server and render it. *The Live viewer page needs to have a scoreboard and must have the ability to be personalized (by the host/competition creator--- they need to enter the UI specs at the beginning (we fetch those during init))
Then there is a Competition mode. After the user submits their code, nothing will be rendered as we will try to save as much of the resources as possible. The user will see a loading screen. In this mode it's PvP (a user against another assigned user). The user will later be presented with a screen letting them download a file (TBD exact format) containing the list of game actions. The user will have the option to upload this file (likely JSON) and be presented with a Playable Viewer (takes in the actions from the file, reads them to render). This screen will show a play/pause/fast forward progression bar. The user will be able to play/pause etc the game replay to learn and improve for their next tournament game.
Action items:
- Create a designated wiki sub-section for the documentation of PixiJS (collaborator User Manual)
- Create discussed user stories & split tasks for Iteration 1
Attendance: DallaliRim, YehJordan, benjaminsunliu, Nolan, JenLys
Absent: NONE
Note taker: JenLys
Notes:
- Assigned story points for remaining 2.2.# Tasks and assigned points to new Issue 2.3 tasks
-
- Wait before creating 2.3.6 as it's a testing task (see screenshot above)
- For Release 1 we need to have a full Live Viewer (and maybe a bare bones Playback Viewer if we have enough time to advance task 2.4.1 and Issue 2.5)
- At the end of Iteration 3 - Beginning Iteration 4 we will see if we can start tasks for the Playback Viewer --> if we can, do the following in this order Task 2.4.1 (come back to the rest of 2.4 after (the pause, play, etc is not a priority for Release 1)) and then start Issue 2.5
- Whenever we use AI's help, mark that in the commit
Action items:
- Each person will work on their assigned tasks for the upcoming iteration