I created this because other sites I used to track and compare debt payoff plans were missing a few features that I thought would be good to have. For one, I wanted to quickly see how minor changes to my payment plans would have a big impact in the long run. Second, I wanted the ability for the loan info to save locally, so that the next time I went to the site I could view my info without needing to log in or re-enter my info. Lastly, I wanted a schedule that told me exactly how much I should pay to each loan for each month, and to get this schedule in an easy to read format.
The site might still have a few bugs, and it could definitely use some optimization. However, I have been excited creating this and using it myself that I felt I should share it now before I added it to my list of abandoned projects.
Thanks for checking it out! Yes to both of your questions. I do want to let others contribute, but I also have more features I want to add that I haven't gotten around to just yet. One would be mobile/tablet support.
I could be wrong, but there is one bug which doesn't stop you from putting in a loan which would never be paid off--based on the balance, APR, and minimum payments entered. I need to put in an evaluation before the details are submitted and pop up an error message if that's the case, but right now it locks up the browser.
In Photoshop you can increase/decrease a value with more control by holding Shift (+/- 10) or Option (+/- 0.1). Similar shortcuts might aid in finer value control without adding anything to the UI.
Nice! One minor tweak that reduces redundancy in the CSS: You can set 'background-color: inherit' on the :before and :after pseudo-classes for the icon links and it works the same way without having to apply the background-color on the element and it's :before/:after.
As I said earlier, I didn't mean that Chrome is completely, literally broken. I meant in the sense of a user having just updated their version of Chrome, going to a site, and not being able to do anything. For me and a few coworkers, this was exactly what happened to us when we started noticing these two issues last night. These two relatively minor CSS bugs have broken the functionality of a site we have been working on to the point where it is unusable.
I've been using chrome beta for a while (so i'm at 23 now and was at 22 a while) and never saw those problems.
How many sites do you know that are broken, apart from your own project?
Adding "clear: left;" to the h1's style seems to yield the expected result, perhaps the problem isn't with the floated items but instead with the blocks? Is there some new rule about the default clear behavior?
interesting - that first one looks like it might be a bug. When you inspect it in the debugger, the h1 is entirely within the container, though the text is well outside.
Oh, that's what happened? Apologies for the alarmist title, but depending on your site's CSS this can completely destroy its usability. I meant it in the sense of a user saying everything on a site is broken, not that everything in Chrome 22 is literally broken.
I agree. Add too much salt to the food and people will say that you've ruined it. Some people won't notice it because they are less sensitive or for other reasons but the food, for some, is ruined.
This happens a lot with the software development where one simple bug in your application makes the user say that "it doesn't work". We, as developers, tend to get mad when all our work is deemed unfunctional because of a simple error but we usually don't see that it is a "simple error" only from our perspective.
It's available to stream on Youtube: https://www.youtube.com/watch?v=dADUBcoEEHw&list=PLBA8DC67D5...