WINNY IN CLASS

 This week I have hit a few more milestones within my code. I managed to display the locations on the homepage map. I also managed to change the default marker icon to my branded markers. Please see below: This was a challenge as I could not figure out why the api url wasn't valid to display all of these locations. After a lot of debugging, I came to the realisation that the api url had the (userSelectedDate) property which was not necessary/connected to the home page. I created a seperate api url for the homepage and after doing so, the code was successful. I also spent some time fixing the constraints of each controller.  My next step is to display the data on the homepage when a user clicks on a marker. I am in the middle of the code and at the moment the code is not successful. Once this is done, I will have the most important elements of the app complete. 

 This week I have had a major break through. I have finally figured out how to display the data on the screen! This was a big milestone for me and the feeling was amazing! Here you can see the live data from the WillyWeatherAPI being displayed on the screen: I learnt a lot about debugging to figure this out, I pulled apart every line of code and wrote many print statements until I found out where the issue was. Now that I have the information displaying successfully, the rest of the build should be rather easy. I will focus on the Google Maps SDK API integration on Friday to show the Hours and Klms on the screen.

 This weeks class was spent trying to work out how to display the data from the WillyWeather API onto the UI View Controller table view cell. This has been a very challenging step of the process and I am still yet to figure it out. After spending a few hours on it, I decided to leave it and work on the front end displays, I changed colours and alignment and added some new labels and UIImages. 

This week, my main focus was to review and ensure the functionality of the tasks I had completed earlier. I dedicated time to check everything I had implemented so far, identifying small errors and missing elements, and addressing them accordingly. The specific areas I worked on included: - Hiding password characters - Validation conditions to ensure that each textfield of the sign up meets the criteria. Eg. Postcode can only be 4  digits - Testing the forgot password functionality by sending the recovery email to my real email address and following the steps. I also made progress in implementing the SWELL search features. I created a UI view controller called SwellSearch, which is similar to SunSearch but includes an extra search feature for swell size. Currently. I have successfully designed the view and working on activating the 'swell size' drop down menu. Unlike the 'location' dropdown, which contains manually entered locations, the 'swell size' drop down r...

 This was a very successful week for my app! I have finally figured out how to print out the data retrieved from the WillyWeather API. This is a major milestone as I can now focus on the UI views and showing the data through the screens.  After a lot of trial and error, I realised that the reason I was unable to retrieve the data was because I was not copying the structs correctly from the API Reference manual. Once I understood the correct format of the structs, the data started to print. Here is the output:  My next step is to print the data onto the UI Views. Once I have printed all of the SUN data, I will start to work on the other tab SWELL which will be a lot easier and quicker as I have now figured out the necessary steps.