Rough roadmap, thoughts, known issues

The point of this issue is so that I can write down my thoughts publicly. I'm currently preparing the module for release, and I'm noticing some things that won't meet some people's use cases or preferences. I'm not going to deal with all of them now, but if it's written here, you're welcome to open an issue and complain about it.

Development on this module will be very complaint- and patch-driven and probably fairly impulsive. Don't expect too much, but know that it's worth a try. I use this, so stuff that I want myself will have an advantage. Stuff that would get in my way will be prioritized lower.

In theory. This philosophy will change if the module actually gets somewhat popular. I'm not expecting it to and not really trying to make it so (I'm mostly publishing it for my own benefit), but who knows?

Stuff I've noticed

• You can't configure how tax and R&D are calculated. Tax is calculated by rounding up to the next whole unit. R&D is rounded up to the next 1/100th. So if your R&D percentage for an income item is 10% and the income is $111, R&D will be $11.10. If it's NOK 12345.99, R&D will be 1234.60. This is the formula I use for myself, so it's low priority for me to change this myself. You know what I'm going to say next........yep, patches welcome. Though I should document this behavior in #1918600: Document expected workflow.
• The module assumes you use SQL storage (and probably implicitly assumes MySQL). Seriously; I call functions from Field SQL Storage. Works for me, but patches welcome.
• (WARNING: If you have Locale enabled, you should apply the latest patch from here to Computed Field Tools: #1587676: Not setting language field. Otherwise, you will be a sad site builder and be frustrated for hours.) If you delete Payments, Amount Remaining will be wrong on the income and expense that the payment pointed to. The Rule I created to handle this doesn't work right. So just install Computed Field Tools and recalculate field_remaining. That's what I do.
• This module won't work with Content Access at the moment. I'll fix this eventually. It's because of the Rule that saves income after it's been saved so that the calculations happen properly.
• Some decorative dependencies (like Autocomplete Deluxe) could be removed and just recommended on the project page.
• I should specify dependencies more specifically (http://drupal.org/node/542202#dependencies). It is possible to require certain versions. So if one breaks, I could put a (<7.x-brokenversion)" as the dependencies[] line.
• I'd love to be able to add new tax types right from the node edit form. However, Inline Entity Form doesn't do the trick here. The widget should still offer checkboxes and radio buttons.
• I currently use Prepopulate, but it looks like Entity Reference Prepopulate could do the trick for my needs. The only fields I currently prepopulate are the income and expense when creating a new payment from the Income or Expenses page.
• http://drupal.org/project/auto_entitylabel could be cool to use instead of Automatic Node Titles (auto_nodetitle), but it isn't a big deal right now. I only use it for giving titles to Payments.
• I forgot to include my pathauto and redirect settings, but when I think about it, they aren't needed too badly. For now they'll just be recommendations. I'll probably put these into the optional Cash Flow Deluxe submodule if I need them.
• There's a little bit of pollution in Cash Flow Core, particularly around the Remember Filter Value settings for some of the exposed filters. They contain the role IDs to remember. I should see if there is a good way to include some roles with Cash Flow and make the Cash Flow Core export automatically figure out and use the correct IDs (since they might vary from site to site). I think this is possible with hook_features_export_alter(), but it is low priority for me. The workaround — edit the Views, change the values, and create a Features Override module — is easy enough. If people complain about getting illegal form values or something, then I'll remove them outright and do this myself. Remembering values is neat when one is taken away from the page and then back in order to preserve context.

Roadmap-like thing

• I guess I should document my workflow a little bit. In fact, this one gets an actual issue! #1918600: Document expected workflow
• Better internationalization would be nice. Right now, I try to keep it fairly currency-inspecific. A custom form to change all the relevant settings might be nice (stuff like regional settings in the fields, etc.) Or maybe just use Custom Formatters. Something for internationalization; I don't care much, but I do use one instance of this for USD and one for NOK myself.
• More computed fields for stuff I ask myself every time I update the finances. Currently, this is mainly, "How much do I transfer from my business account to my personal account to cover expenses I pay personally?" I already store the necessary information (the Business field on the expenses and which income will pay which expense).
• BUDGETING FUNCTIONALITY. The spreadsheet I used to use had some really neat budgeting stuff in it. I never got that implemented here; I just use another spreadsheet now.

  Of this, the most important is lists of recurring groups of expenses and savings accounts of some sort to track how much money is set aside for R&D. When creating income, one would be able to specify which of these savings accounts the auto-saved portion should go to. So for me, it'd be the R&D savings.

  Calculations would be nice too. e.g. how much pre-tax income do I need to pay my expenses? But I am not too worried about that; spreadsheets are decent tools for that kind of thing. It's secondary.

• Speaking of auto-saving, I'd like this to be separated out somehow. I auto-save in two separate ways now. I set up auto-saving (field_r_d) when I only had one. But if I implemented the savings account thing, I'd need to figure that out. Maybe I could use a field collection for them so that I could specify the rate per account. Something like that.

These used to be on the project page:

• DONE! 7.x-1.0-rc2 "How much to transfer to personal bank account" computed field
• Reports — Expenses vs. Income (by date)
• More automation! Auto-copy expenses by tag (e.g. "monthly"), but auto-fix dates, or allow grouped editing of expenses right after creation.
• Other stuff — I'll add it in once I publish the first release