Ben, Actually, now I understand a little more about what you are asking. You are wanting something very basic that is like Hazel (rule utility for the Mac). Except for personal finance.
I envisioned the functionality you described as MUCH more indepth and involved; sort of a sit back and let your financial management handle itself kind of approach. (I'm sure that should be hyphenated!) I can be wrong, it happens a lot, but I would think that this would be the most problematic from the bank side: polling for triggers from the bank when many banks seem to not even have OFX working yet. To truly make it useful it would have to have some sort of messaging would it not? Some way to let you know what was going on? I don't know if I would be one to trust a system to that level any time soon. So, don't take my comments as scoffing on a dream. More like, I simply don't understand the reason "why" you would want it because I want to make my finances simpler to manage with a very low amount of room for technical error. (If there's an error, I want to make it!!) : ] Dave On Dec 11, 7:06 pm, bvz <[email protected]> wrote: > Of course. That make sense. Thanks for all the quick replies. It > bodes well for my user experience when I buy MW! > > Ben > > On Dec 11, 3:36 pm, Kevin Hoctor <[email protected]> wrote: > > > On Dec 11, 2008, at 5:31 PM, bvz wrote: > > > > I can appreciate the difficulties. Looking forward to a Wells Fargo > > > compatible version. > > > > One last thought/idea/request/on-my-knees-begging-session: Could some > > > of the usability I am looking for be exposed via applescript? > > > Basically, make the app scriptable and include the raw information > > > such that someone with the programming chops (like, say, me!) could > > > extract the necessary data and then code the interface/warning system > > > themselves? > > > > One would need to be able to (via applescript): > > > > automatically make MW download the latest info from the selected > > > banks. > > > be able to parse the downloaded transactions for the individual data > > > items they need (transaction type, transaction recipient, amount, > > > date, etc.) > > > be able to parse the entire database for the same info > > > > obviously security would be an issue, but perhaps each of the > > > applescript calls would have a username/password argument embedded in > > > it. > > > > This would sort of put the pain/risk of my system on the end user, but > > > still make it possible. > > > > I can totally respect that you most likely have bigger fish to fry... > > > just hoping and wishing here. > > > Hi Ben, > > > I'm quite aware of the rule to make every Mac application scriptable > > so customers can make it do more all by themselves but given the > > target audience for MoneyWell, I have to push that type of > > functionality down the priority list a bit. Sorry. I'll review this > > ability again when coding the 2.0 release. > > > Peace, > > > Kevin Hoctor > > [email protected] > > No Thirst Software LLChttp://nothirst.comhttp://kevinhoctor.blogspot.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "No Thirst Software User Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/no-thirst-software?hl=en -~----------~----~----~----~------~----~------~--~---
