#Ifinance mac how to#
#Ifinance mac update#

They should be available as properties for template authors though. Checking one of the 'Inherit' checkboxes will disable the respective color selector. 'Close' button is not required since the window controls can do this already. On click on a category, or the '+' icon, the right side would be activated. Initially, the right side elements would be empty & disabled. Īctually, I'd prefer to have one window for browsing and editing with automatic commitment of changes without 'OK' button: That should definitely be changed, especially for a finance app. This is also good because then the 'selected row' bgcolor can be applied to all remaining columns and there's confusion as to what is selected.

Here's an example mockup which works if we just color the category column. If MMEX were written in Javascript I'd probably have it half finished by now. My C++ is limited unfortunately, I'm more at home with web development and scripting languages. Looked at it, can parse most of it, but broke everything trying to do small modifications. If you are going to develop this then I would suggest splitting the keyword matching and changes to import logic from the category coloring as they are two independent features. Sure there are a few other items to consider. I would suggest further refining the requirements/behavior and generating a few mockups of the changes. Unfortunately, I don't think the ListView in wxWidgets supports individual cell color highlighting so we couldn't highlight just the category with the color. How the coloring interacts with the existing transaction coloring that is supported by the application. If you want to use the colors for the reports. Maintenance of the colors and keywords in the category dialog: There is no automated test suite as far as I'm aware! Do you also want to color budgets for various categories in the budget setup?

Also, a recurring transaction list needs to be considered. Need to also consider what you want to do with asset and stocks/shares transactions. The main transactions grid is generated here. Need to consider how 'split transactions' are colored. I have some ideas but I'd like to avoid going into a completely absurd direction by mistake. I would appreciate any hints where to start looking. I found a Travis CI config, but no test suite, where is it? The test suite needs to be updated to ensure that keywords are correctly read, edits cause category rescans, no race conditions occur when editing AND manually setting the category, and so on. When displaying transactions, the colors need to be applied to the transactions grid. after adding a keyword) should be possible using a context menu item.ĭisplay.

Also, selecting a number of transactions and replaying automatic category assignment (e.g. What would be the best practice to insert this code? Preferably (of couse) in one central place, as a before-save or before-commit hook. When editing transactions, this should not happen to enable users to still override the automatic assignment. Import & Create hook: When importing or creating transactions, KEYWORDS will need to be scanned and if recipient or notes or any string custom fields match any keyword, the category_id needs to be set. How do I add these and ensure MMEX will pick up the new format upon startup? Just add another.

#Ifinance mac how to#

I'm asking for some advice how to get started.ĭatabase migration: CATEGORY_V1 will need three more string columns: BGCOLOR, FGCOLOR, KEYWORDS. For starters, I'll plan to implement those two. So I'm planning to switch.īut before that, MMEX will need to get killer features: automatic category assignment based on keywords, and automatic coloring of transactions based on category.

#Ifinance mac update#

I was using iFinance (Mac) before but now my primary computer is Linux, and iFinance also seems not too well maintained (no update in several years). I just got started with MMEX and I like the approach. Copied from forum post (which was then deleted, to track all communication related to this issue here)