For this weeks retrospective, I really felt as though my group and I got a lot done. A majority of what we had decided to do was to look up some more skeleton code. Our plan for this Sprint was to finally get started on some code and getting things running. While talking with Professor Wurst we realized as whole for this project that each group with each of their components will make a separate branch for that component and work separately in that branch. From there we would make a pull request to the AMPTH repository where they can other members from other group can view our code and see if it compatible with the rest of the code.
To go in more detail on our specific branch, for Team Rocket I created a branch named ‘Tabs’. I did this by going into the project through the terminal. Then by running ‘git checkout -b Tabs’. From there I needed to create an empty commit - ‘git commit --allow-empty -m”Create a Tabs branch’. This just shows that we created a branch and committed it right away with nothing in it. After the branch was created Professor wurst told us that we will need to install some angular app materials that would be useful in creating our component. Everything that we will be using in our project comes right from angular, so it would be smart to download these tools. We got this information from https://auth0.com/blog/creating-beautiful-apps-with-angular-material/.
The main things i ran in the terminal inside the project was 'npm install @angular/material @angular/cdk' and 'npm install hammerjs'. The second one was from the angular/material tutorial.
After installing these tools, the plan for the weekend was for all four of us to use some of the skeleton code that we had found and implement it into our code to make sure everything was running smoothly. This just ensured that we had the right libraries and dependencies while running the final project. The skeleton code that we decided to use was from https://material.angular.io/components/tabs/overview. After this weekend, Daniel Ryder from our group had created a simple tabs component from the website listed above. The problem that we had with this was just that Daniel had created this inside of a simple angular project that was not connected to the project that we were working on. Ryan also found some useful form skeleton code that we would need for the forms of each tab in the future. We found out that we still do not know what is needed inside of each of the forms, like what the patient needs to fill out but we could include the overall code of a simple form into the code. Samuel Bryan, the other person in the group had worked with James on the website Zeplin which thoroughly explains what Greg Schmidt would like from us and each of the components. It very easy to understand and much more detailed than the videos. That website can be found https://app.zeplin.io/project/5c7fe3c5826def62505ec3b8. Since Daniel needed to put the code into the branch, and the blank angular project I had was from the project, I decided to generate the folders that would be needed for the tabs function. From there Daniel cloned the project from the repository and then started to move the code he had started to working on, into the new cloned project while in the Tabs branch.
