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. Ben On Dec 10, 3:32 pm, Kevin Hoctor <[email protected]> wrote: > On Dec 10, 2008, at 5:16 PM, bvz wrote: > > > > > I'm surprised that people think my idea is that complex (although what > > do I know? I have never actually written any software even 1/100th as > > complex as MW). It seems like most of the work is already done. MW > > can download transactions. MW already classifies different > > transactions based on some set of internal (and user defined) > > criteria. This would simply (hah! there's that word again) extend it > > a bit. > > > I guess that I am just an interface nazi because most software seems > > to miss the mark for me. I actually have a "thinking" box parked on > > the desk in front of me but I still have to "do" everything myself. > > It is analagous to power steering. It may be assisted, but I still > > have to steer - which really seems to shortchange the possibilities we > > have with such powerful and interconnected machines. The mission > > statement shouldn't be "make steering simpler"... it should be "get to > > destination with less effort". All too often I think our software > > goals are to mimic analog methods too closely rather than think about > > what the ultimate purpose of the activity is in the first place. > > > Of course, once again, I have never actually written such a complex > > piece of software so please treat this as a "hmmm... wouldn't it be > > interesting" comment rather than a criticism. > > Ben, > > It's not that it's hard to create something like this, just that it > would be difficult to make the interface simple. Most rule-based > systems need a way for users to set the rules, which means, they need > to have lots of choices that are understandable. That's the tricky part. > > 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 -~----------~----~----~----~------~----~------~--~---
