The Progress

This week I decided on a repository to work on, the telescope repository. I was excited since this was a front end development issue. I had never created my own component before, however, I have some prior experience using React. I started by creating a bottomBar component and locating where I should add this component. I located the PageBase.js, the mobile application interface, and added the component to the bottom of the page. I started by creating a div with a red background to make sure I was on the right track. since it has been a couple months that I have not worked with React, I started with the most basic tasks, such as, creating a react component, a div element, and rendering the component I made. 

   After confirming that I did not break anything, I started designing the layout of the desired BottomBar. The idea was created by agarcia-caicedo,  proposed a bottom app bar to improve mobile usability. If you're curious on the original idea you can check out his issue. He also stated that the BottomBar should include some functionality depending on if the user has logged in or not. I started by creating four icon buttons on the BottomBar. Using the "http://material-ui/icons" library I was able to quickly locate the Icons that Agarcia-Caicedo had proposed. 

    Next was implementing CSS to the center the icon spaces between each other, apply an appropriate font size for the icons, and finally adding the background colour. Another problem that I encountered was changing the background colour of the Icon that is currently selected, for this problem I created a function that checks if the current page is the site we are on. If this was the selected URL we simply overwrite the CSS applied on this element.

    Next, was the routing the links that had to be created or replaced. Since most of the code was written in another location, this part was a simple copy, paste and review, after completing the skeleton of the BottomBar I created a pull request. Proud of my work I started to focus on my other courses. 

    A few days passed without me looking at the pull request I had created, during this time I had forgotten most of the code I wrote! The professor asked that I test my pull request, which became a bigger problem than I had anticipated, since I had no clue how to create a local log in system. Telescope, the repository I was working on, uses a Passport/SAML to allow local log in testing. This was a painful experience, since I had never used SAML 2 before. I had difficulty setting up my local environment to allow me to log in. Thankfully, I had help from a Slack group with my fellow colleagues. While I was panicking, they remained calm and collected. I noticed that since they were not emotionally attached to the BottomBar project, they could see the task more objectively, which allowed them to help me discover the solution more efficiently.

Comments

Post a Comment

Popular posts from this blog

Working with others

     This week our course was given the task of creating a cli command, which included our code being reviewed by one of my classmates. Initially, this gave me some anxiety as sharing my work with others is not my strongest suit. Nonetheless, I created a post asking if anyone was looking for a partner and Michael Appeared.      It turns out that having someone look over my work was much less scary than I had initially anticipated. Working with Michael was actually fun, and having the opportunity to look over someone else's work was a great learning experience for me.       With another pair of eyes looking at my code, Michael noticed errors and instructions that I was not addressing. Some instructions I had forgot to mention include the fact that my program requires bash. It did not occur to me that most of us live in a Windows Operating System. Another missing component was my Blog link in my READme. I had forgotten to include a link to my blog! As soon as Michael notified me he w
Read more

We are off! V0.1

Initial Release V0.1  Our first Assignment was to create a command-line tool to check and report dead links in a file. Status code 200 would be considered "Good", 400 and 404 is "Bad", and all other status codes are considered "Unknown." My first experience creating a release was nerve racking. With no instructions on how to approach this problem, I started to brain storm ideas, and eventually started questioning my abilities. Inevitability, I chose to do my assignment in bash since it would allow me to colour my code, as well as create a command line tool. Overall, the first assignment was fairly simple to use. Simply clone or fork the repository, open up bash, and run the command. Command : ./cliCommand <filename> NOTE: This project will need Bash installed on your machine. Mac OS has bash built in, however, Windows OS may need to install Bash. Please feel free to play with codes, if you have a crazy idea, then pull request :) Usage and Features Us
Read more

Lab 2

     Started my morning a little rough, however, I managed to get online to start my lab 2. I randomly selected  https://github.com/yuanLeeMidori/OSD600.GoodLinkOrBadLink as a repository to begin with. As I kept reading I noticed this project was not for me, I have never worked on .NET platform and do not plan to anytime soon. However, upon reading the READme file I noticed some sentences that could use some grammatical help. I took this opportunity, to practice how to create a pull request. I knew this wouldn't count for my lab 2, however, decided it was worth the experience. I followed the given instructions and successfully created a pull request. Later on I'll talk about all the requests that have been accepted or not. Here's the rest of my story: Who did I help? Roger.  What was Rogers Project? Roger was working on Cligon a program that stands for Check if Link Is Good Or Not. how did I contribute to Cligon? I added a requirements.txt file to Rogers Repository. This r
Read more