Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||Create new branch named "cascade_methods"|
|Downloads:||Tarball | ZIP archive | SQL archive|
|Timelines:||family | ancestors | descendants | both | cascade_methods|
|Files:||files | file ages | folders|
|User & Date:||atomicules 2015-07-06 20:53:52|
|20:57||Alternative approach to code, cascading methods 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|
|20:53||Create new branch named "cascade_methods" check-in: cdb88b0318 user: atomicules tags: cascade_methods|
|13:36||Fix sorting/ordering of transactions 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|