Goal: To really get a handle on glimmer and developing robust web apps. It also is supposed to make you think about how to design an app that real members will use based on a set of instructions. Think about how you would use this app with your friends. I expect that each assignment will have multiple unique aspects to it.

Remember to supply a readme describing your work, what youve done

Instructions

• Think of a very (very very) light version of the Splitwise app. Splitwise is a calculator app that takes in a bunch of shared expenses (dinner, movie, cab) and names of participants, and spits out how much each participant owes at the end.
• Design a cost breakdown calculator that allows the users to add up to 10 names to a list of participants.
• Then allow the user to add spending events. Each spending event must be assigned to a person. (i.e dinner or a movie is each a spending event. imagine we all went to dinner as a class, only one person is allowed to pay for dinner, and one person is allowed to pay for the movie)
• When the user clicks the Tally Up button, the final output will be a list of all the names and how much each person owes. ( see example logic below)
• You are expected to horizontally center the calculator in the center of the page no matter how wide the browser window is
• You should be able to delete a spending event you added
• Color code the outputs and sort them. People who are owed money should be in green font in the final list and people who owe money should be in red.
• Implement a minimum of 3 helpers to your project. These helpers should be useful in formatting, calculations and/or styling. anything really. they will help you for sure :)

Example Logic

Person A Paid 100 Dollars for dinner

Person B Paid 50$ for Cab/Transportation

Person C Was not assigned to any spending

FINAL LIST:

Since there are 3 people in this party, and a total of 150$ was spent, that means each person is supposed to pay $50.

Person A: +50 (indicating person A is owed 50$ from the part)

Person B: 0 (Indication person B does not owe and is not owed)

Person C: -50 (indicating person C owes the party 50$)

Extra Credit

• (+1.5 point to final grade) Instead of having a tally up button, lets have the final list update itself as we add participants and spending events to the list. For example, in the above example I gave, lets say we only added Person A and person B. The result list would show that only 2 people spent a total of 150$, thus each one should have paid 75$ (person A is owed 25$ and person b owes 25$) without having to click a tally up button. But when we add another person, person C, the final output list would show the FINAL LIST in the example logic section above. Keep in mind that you also want the final list to update if we delete a spending event.
• (+2 point to final grade) This is a bit harder than it looks, since there are many combinations of final outputs the more people we have in the participants section. The output list should say who owes who what. For example, in the Example Logic section above, the final output with this extra credit would be
  • Person A: is owed $50 by person C
  • Person B: does not owe and is not owed
  • Person C: Owes person A 50$