mostlyfabulous/runtime

Find time to exercise depending on the weather and your schedule!

runtime's Issues

History

• fix rendering bug
• add stats

Weather

• fix weather event updates
• set meteor server to periodically update weather
• store weather by city
• change to DarkSky API

Username is undefined when signing up through Google

User cannot choose username

Scrum Report - Workshop 2

Napat's (u4b1b) Scrum Report

What did you work on this past iteration (2 weeks)?

• Categorized the project requirements (minimal, standard, stretch) and divided the requirements into iterations with my group.
• Create a prototype from the hand-drawn draft in Adobe XD.

What were any major issues/challenges you ran into?

• I'm new to prototyping and I'm only used to layers while Adobe XD uses components too, so it took more time to figure out.

What do you plan to work on for this coming iteration (2 weeks)?

Note: Andrew W. is also working on these issues.

• Integrate FullCalendar with our webpage.
• Set up the React components for each web page (2 for now) and hardcode values.

Scrum Report - Workshop 3

Napat's (u4b1b) Scrum Report

What did you work on this past iteration (2 weeks)?

• Got weather data (from API call to openweathermaps.com) saved into state when page loads and displayed in the Info (3-hour forecast) component.

What were any major issues/challenges you ran into?

• I got an email saying we were making over 700 API calls a minute and our account got suspended. Turns out render is doing background work and refreshes the actual page when it detects the change, and the background work is what's making the frequent API calls.

What do you plan to work on for this coming iteration (2 weeks)?

• Integrate Redux state and help Andrew with more calendar functionalities. Add users functionality if time permits.

Preferences

• set up table
• add temperature colouring settings

User prefs not created when a user signs up

After signing up, the user prefs page doesn't load as their is no entry in the DB to return

Scrum Report - Workshop 6

Andrew's (h7h0b) Scrum Report

What did you work on this past iteration (2 weeks)?

• Fixed history chart bugs due to dates
• Added lifetime stats to home page

What were any major issues/challenges you ran into?

• When combining properties from all runs to get the stats, some of our old runs were missing fields or had incorrect formats and could not be easily reduced

What do you plan to work on for this coming iteration (2 weeks)?

• Deploy app
• Help implement scheduling algorithm
• Improve UI (probably use material design)

Remove Insecure

• Define Meteor methods to handle database calls
  https://www.meteor.com/tutorials/blaze/security-with-methods

Algorithm

• schedule closest to current time
• 3 options shown on calendar
• preferences

Calendar's 'today' color blends with background event colors

Currently, the calendar highlights today with:

Which causes color blending on the current day column:

Disabling the today color, fixes this but at the cost of user experience:

UI Design

How should we collaboratively design the UI?

Can we use a shared jsfiddle?

https://jsfiddle.net/mostlyfabulous/cebd6Loj/#&togetherjs=LuAPNImoE1

Also, we should try and figure out a color scheme:
https://coolors.co/676366-df9a47-f87d4a-ba9160-d7b066

This might be a starter interface to build on: https://getbootstrap.com/docs/4.3/examples/dashboard/

Home page

• total distance run / stats
• suggest run to add to calendar
• fancy stuff

UI

• pretty precipitation ???

Pat:

• user defined colors for temps
• use google icons

A.W:

• use weather icons in topbar
• reactstrap modal for user prompts and confirm
• add comments to runs, hovering on the event will display the comment

A.C:

• make prefs full size
• change chart to Scatter plot

Scrum Report - AW

What did you work on this past iteration (2 weeks)?

Project design elements, finding a JS calendar library with suitable API calls, researching a suitable weather API and some overall UI design (dashboard bootstrap as inspiration).

What were any major issues/challenges you ran into?

Integrating distance and time metrics into the project.

What do you plan to work on for this coming iteration (2 weeks)?

Setting up the calendar for use as a React component.

Sub-components starting separate subscriptions

Refactor subscriptions to start and stop in Main component when a user is logged in.

Scrum Report - Workshop 4

Andrew (h7h0b) Scrum Report

What did you work on this past iteration (2 weeks)?

• Added data chart and displayed run information in the history page

What were any major issues/challenges you ran into?

• Categorizing runs by date in the chart was more difficult than using regular indices, especially when dates were relative to the current day

What do you plan to work on for this coming iteration (2 weeks)?

• Begin to create algorithm to suggest runs
• Help adapt our logic to work with Mongo
• Start working on home page

Scrum Report - Workshop 5

Andrew W's (p0w0b) Scrum Report

What did you work on this past iteration (2 weeks)?

• Mongo integration: Added actions and reducers for calendar to subscribe to runs & weather events from Mongo Atlas and pass them to Redux. Events can be modified and their properties saved to Mongo Atlas and the store by dragging or clicking on the calendar.

• Transferred OpenWeather API request calls to Meteor server so that client will eventually only pull data from Mongo Atlas through Meteor server

• Added initial logic for server to update weather events dependent on how much time as passed. Have timezone considerations to factor into logic.

• Basic React Transitions for EventEditor component.

What were any major issues/challenges you ran into?

• Connecting to Mongo Atlas and getting Meteor server to link with collections in our database.

• Learning how to use meteor-redux-middlewares to synchronise data between Minimongo and the Redux Store

• Learning how to use Meteor's withTracker() to create component containers that pass props reactively and learning about Higher order Components

What do you plan to work on for this coming iteration (2 weeks)?

• Improve weather event processing, add location and other fields to current weather event object

• Improve calendar:

  • Delete events
  • Highlight currently selected event
  • Add event 'stretching' calling back to change event duration

• Work on scheduling algorithm.

• Set-up Oauth 2.0 process for Google Calendar API calls client-side and pull Google Calendar events into user's Redux Store

Some events don't have end time

Fix calendar

• colouring (weather + runs)
• delete event
• stretch event handler
• add end times
• calculate duration
• fix event editor behaviour