Smile Bank to Ledger

Keep pre-processing in Vim which is dumb/lazy. check-in: ed7740affc user: atomicules tags: trunk

Really I don't need all that class stuff in there anymore, but I thought I
would retain and re-use what I could. Now it simply parses the csv file that
Smile provide for download and converts that to Ledger format. Sob-sob - I
loved being able to logon on the command line and download transactions. check-in: 4ca78e73c4 user: atomicules tags: trunk

I'd forgotten to commit these. Committing for reference since none of this
works anymore. Only option is to use a webbrowser and download the csv. Will be
changing this into a CSV parser. Maybe. Might even just do that in Vim. check-in: ce95ff0dde user: atomicules tags: old-smile-site, trunk

Sob. Sob. Not that I ever want to see them though.

I'd inadvertently assumed I'd only ever see a positive balance. Need to regexp
to get the negative that Smile put at the end of the balance and stick that in
the right balance, but only if a negative - it seems Ledger doesn't understand
a plus sign in front of numbers. check-in: e176864222 user: atomicules tags: trunk

Thought I had worked around this, but need to explicitly check for page.form
and then also explicitly return the initial page check-in: 786c2c8c74 user: atomicules tags: trunk

Since methods make no sense on their own, make each method call the method
before it so requirements cascade all the way back. Since each method now
returns `page` there is no need for `page` to be an instance variable. So
perhaps this is a bit cleaner? Leaf check-in: 1905cd0eb7 user: atomicules tags: cascade_methods

Need to get things in the right order for checking whether we've gone far
enough back and also for appending to the main transactions array and then
again for writing out.

Also add appropriate Expenses/Income placeholder check-in: 5bdd7b804f user: atomicules tags: trunk

I'm not entirely sure whether a class structure is appropriate for this. At the
very least because I'm only ever creating one of them, but also because
although it's nice having the separate methods for each stage of the logon
process, etc, they don't really make sense, and cna't be used, as standalone
methods. I'm also not sure about the use of instance variables. Splitting
things out into methods almost requires them as passing arguments would be a
bit clumsy, but then it is almost like using global variables. So, all in all,
I've attempted to make it more Ruby-ish, but I think I've failed.

- I'd got credits and debits the wrong way round
- Adds in dealing with memorable date logon details check-in: 5454406454 user: atomicules tags: trunk