Mar 10, 2015 - RostarSynergistics/ShinyExpenseTracker GitHub Wiki

Agenda

  • Add tests that fail
  • Add menu plus button
  • Ask Alex about Imodel implementation

Team Meeting

ADAM

DID:

  • Almost Nothing. Really sorry.
  • Should've worked on the weekend
  • Will work on it hardcore this week

WILL DO:

  • A hell of a lot more than last week (hopefully)
  • Going to do grunt work

BLOCKERS:

  • No blockers

ALEX

DID:

  • Nothing
  • Gave our stuff a bit of a look

Will Do:

  • Deal with hostility within the ranks
  • Get synergy back on track -Increase productivity

BLOCKERS:

  • No blockers
  • Go over how he'll mark and give feedback

RAJAN

DID:

  • Merged ExpenseClaimController
  • Worked on Manage Tags
  • Dealing with Merge Conflicts: With add tags

WILL DO:

  • Finish that issue
  • Work on whatever needs to be done

BLOCKERS:

  • Other assignments

TRISTAN

DID:

  • The ExpenseListView: Displays all the claims
  • Code review.

WILL DO:

  • Yell at Ramish/Sarah

BLOCKERS:

  • Just 2 midterms

SARAH

DID:

  • CreateExpenseItem and Tests for that
  • In review

WILL DO:

  • Other issues involving any Expense Items

BLOCKERS:

  • None

###OLEG

DID:

  • Implemented addition of tags
  • Made UI for that
  • Tag Controller
  • Reason for Rajans problems

WILL DO:

  • Other tag stuff

BLOCKERS:

  • Rajan

Note on Pull Request: When you make a comment on something, assign the pull request to someone else

RAMISH

DID:

  • Implemented the ExpenseClaim
  • Test are not working. So I gotta work on that.

DO:

  • Whatever's assigned
  • Fix the tests

BLOCKERS:

  • Tests

Other Stuff

SINGLETON DESIGN PATTERN

  • If you're dealing with design classes, it's not OOP.

IMODEL IVIEW:

  • IModel is a generic interface which is paramterized with a view interface
  • Completely delete the IModel interface
  • Don't need any abstracting. No interface required
  • In Java we only have single inheritance. IModel only works with multiple inheritance
  • A Generic IModel class
  • If our model classes don't extend anything, add extended

MISC

  • Each class should have a comment what it does, how it's used, an example, what classes it relates to/is related to.
  • Any method that's doing anything of interest should have a comment,