diegonetto / debtcrunch-node Goto Github PK

Should be simple to add this logic.

When one value takes up such a high percentage of the Pie Chart, the other slices can become so infinitesimally small that attempting to draw an arc breaks the Pie Chart.

Detect this and draw a circle instead. Consider flashing a message to inform the user.

The debt types that have a minimum monthly payment requirement should check against the current principle balance before returning a value.

Build a 'FAQ' page and show what equations were used in which calculations, and describe the various stipulations of the specific loans (minimum monthly payment requirements, etc).

Have a section for each type of loan and describe in detail what works for each generalization (i.e. fixed rate mortgages, etc).

Maybe < $0.0001 or something along those lines will suffice.

Although some debts have explicit minimum monthly payment calculations (credit cards, student loans), the ones that don't still have an implicit one.

Specifically, the minimum monthly payment should cover at least the interest accumulated each month.

Hitting tab inside of a form-cell debt-input should focus the next input/button.

Since the inputs are hidden and changes are scrapped, the inputs cannot be highlighted in red. Instead, draw attention to them by performing a Red-Fade animation.

Adjust absolute positioning and floating.

Steps to Reproduce:

1. Edit a debt inline and change only repayment value.
2. Edit any of the input values to include a period.

Add a mechanism to disable client side logging in production mode.

Clarify to the user that this is the MAXIMUM amount their monthly payment will ever be.

Elaborate in FAQ section.

Add additional validation to prevent duplicate debt titles.

This should represent that a debt has been paid off and can be marked as completed.

Remove hard-coding of canvas size for the overview pie chart and implement re-sizing in the pie chart library.

Use Backbone.Router and Backbone.History to leverage HTML 5 History API.

Instead of flashing an alert-info, use a blue-fade animation on the debt amount.

Have the overall AppView decide when to create and destroy the Organize and Strategize Views. This should make the application more responsive.

Check for memory leaks and zombie views.

Reference: http://lostechies.com/derickbailey/2011/09/15/zombies-run-managing-page-transitions-in-backbone-apps/

This causes the wizard or clocks to be hidden. Must diagnose the root cause.

Clear up some room for a Total Sum label which adds the total lifetime interest to the principal.