✍️
Team FitBob
  • Introduction and Foreword
  • Motivation
  • Features
  • Tech Stack
  • Software Engineering Practices
    • Requirements
    • Software Design Patterns
      • Model View Controller (MVC)
      • Abstraction Occurrence Pattern
  • Deployments
    • Trying Our App
  • Activity diagram
  • Frontend
    • Login
    • User Registration
    • Client Screens
      • Client Dashboard
      • Client Profile
      • Eating History
      • Meals
    • Personal Trainer screens
      • Personal Trainer Profile
      • Personal Trainer Dashboard
        • Clients
        • Meal plans
        • Meals
    • Recipe screens
    • Search screen
    • Searching for Restaurants
    • Notes on BeautifulSoup and Flask
    • Request/Success/Failure Cycle
  • Backend
    • Notes on Django
    • API
    • Entity relationship diagram
  • Testing
    • User Testing
    • Backend
  • Project Limitations and Constraints
  • Closing Thoughts.
  • Project log
  • Poster
Powered by GitBook
On this page

Was this helpful?

  1. Frontend
  2. Client Screens

Eating History

Displays a list of food consumed on the selected date. Default date set to current day.

PreviousClient ProfileNextMeals

Last updated 3 years ago

Was this helpful?

The list of consumed foods belong to the user, and is obtained through a GET request to the API end point.

The user can also click on the individual consumed items and carry out actions such as:

  • Edit calories of the consumed food

  • Remove consumed food

There is a minor issue with this page, as the Date picker modal adapts to the device's appearance theme. If the user's device is on Dark mode, the words on the picker turns out to be the same colour as its container, which is white. The words are then not visible in the date picker. We have tackled this issue by going to the root file of the date picker modal, but when the dependencies are rebuilt, the file is overridden to its original copy.

Popup of actions after pressing on a consumed meal