top of page

Braeden Timlin: Milestone 1

Writer: Braeden TimlinBraeden Timlin

Updated: Jan 29, 2019

This week was the beginning of the Design Studio 3 Term Project. My largest project for the last week was setting up our GitHub Repository, as well as determining the Git workflow we will use. We will be creating branches for new features and bug fixes, then creating a Pull Request when the ticket is Ready for Review. Another team member will then review the PR and test the functionality of the feature added. Once the PR has been approved is will be merged into our "develop" branch. Our develop branch will be our main branch that we merge new features into, and will serve as our main branch. Each time we have a release to provide we will merge a stable build from develop into the master branch and submit the work that is in the master branch. This allows our team to have an added level of security when adding new features.

I also updated our ReadMe file on our Repository to contain Environment Setup instructions as well as instructions on regular git usage, such as creating and grabbing branches, as well as creating PRs and merging them. This was created as a reference tool for team members that are unfamiliar with Git, so I can share my knowledge and experience with them. There is PR currently Ready for Review that contains these changes, another team member will review the ReadMe to determine if the instructions are clear enough. The PR will get merged into develop once approved.

We originally were going to be using a series of Trello Boards to track our project: Backlog, Sprint Board, and Retro Board. Our Backlog would contain all new stories as well as any bugs logged. The tickets would then be triaged and planned for an upcoming sprint or moved into the current sprint scope if time allowed for it. The Retro Board would have been for if we determined that we needed to discuss how the team was working we could hold a meeting and discuss what has been going well, and what needs to change in the upcoming sprints.

I created three screens of a preliminary design for the mobile UI, as well as a preliminary design for the UI pop ups in the VR Environment when the user hits the training Dummy. These designs are test designs so they will go through many more iterations before they are finalized.




On the actual project side I have two PRs for new features that are currently Ready For Review: Kendo Sword 3D model, and Initializing the A-Frame Environment. The Kendo Sword Model was created with Maya, and it is modeled, UV mapped, and textured. As soon as the PR is approved by another team member it will be merged into develop. The other PR that I have Ready For Review is for initializing the A-Frame Environment. This code simply launches the A-Frame environment and places a cube in at origin for testing.

<html> <head> <title>Kendo School</title> <script src="/js/aframe-v0.8.2.min.js"></script> </head> <body> <a-scene> <a-entity id="box" position="-1 0.5 -3" rotation="0 45 0" scale="1 1 1" geometry="primitive:box; width:1; height:1; depth:1;" ></a-entity> </a-scene> </body> </html>


Overall I have spent about 14-20 hours in the last week setting up our project and working on a few small parts of the actual project. Moving forwards I will begin working on implementing VR controls in the A-Frame environment, as well as work on designing the UI elements in the VR environment.

Commentaires


Les commentaires ont été désactivés.
Post: Blog2_Post

©2019 by Kendō Gakkō. Proudly created with Wix.com

bottom of page