Adding in directions progress. Users can cycle through directions one by one using 'previous' and 'next' buttons. Next steps: integrating the FourSquare API to enable real directions, setting current location as the start point, and the FourSquare location as the endpoint
Adding notes to the JS file, as well as switching the start position to the user's current position
Adding a couple more clarifying notes
Added in places model, and am able to send user's location to the server, and retrieve the FourSquare response on the front end
Added in location form to either get user's current location, or allow them to input a different one
Added in MapQuest Directions Matrix request. Need to figure out a way to make the API key secret, and how to format the venues from the FourSquare response
Adding in matrix API call
Adding in basic stylings for three views.
Adding a map and two markers to it for the current directions. Next steps: moving next and prev click listeners within map function scope to re-render with new directions each time
Added in code to make the map recenter to the new markers added for each leg of the journey, deleting the former markers from the map first.
Added in working conditional for 'next' button that checks against the length of the directions instructions array
Adding in map styling
Added edits to map styling, and changed the polyline color
Added in placeholder user icon
Added venue name to 'arrived' page
Added in destination upon click of the 'wander' button
Adding in functional radio and checkbox buttons to location form
resolve merge conflict errors, merge google maps
add layout script refs and css styling, update adventure ctrl to reflect google maps angular work
styling fix