summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Set CFLAGS for the libintl.a buildJohn Wiegley2009-11-241-0/+3
|
* Don't migrate commodity details from pricing entriesJohn Wiegley2009-11-241-1/+1
|
* Optimized Mac build of Ledger now 32-bit and 64-bitJohn Wiegley2009-11-241-13/+24
|
* Whitespace fixJohn Wiegley2009-11-241-2/+4
|
* Don't link libintl.a against the Python ledger.soJohn Wiegley2009-11-241-1/+1
|
* Moved up to Boost 1.41John Wiegley2009-11-242-106/+52
|
* Added even more missing virtual keywords!John Wiegley2009-11-222-2/+2
|
* Merge branch 'next'John Wiegley2009-11-2133-49/+693
|\
| * Added several more missing virtual keywordsJohn Wiegley2009-11-216-6/+6
| |
| * Added a missing virtual keywordJohn Wiegley2009-11-211-2/+1
| |
| * Added some more notes to README-1STJohn Wiegley2009-11-211-4/+22
| |
| * Default to 40 transactions per screen in server.pyJohn Wiegley2009-11-211-3/+3
| |
| * server.py now wants a query stringJohn Wiegley2009-11-211-11/+9
| |
| * Removed an explicit path referenceJohn Wiegley2009-11-211-2/+4
| |
| * The Python web server now uses jQuery TablesorterJohn Wiegley2009-11-2117-27/+567
| |
| * Fixed a regression test due to changes in amount.hJohn Wiegley2009-11-201-6/+6
| |
| * Fixed Ledger/Python byte vs. char Unicode bridgeJohn Wiegley2009-11-207-22/+54
| |
| * Added string conversion op for amounts and balancesJohn Wiegley2009-11-202-0/+12
| |
| * Extended python/server.py, which now uses CheetahJohn Wiegley2009-11-201-2/+45
|/
* Merge branch 'next'John Wiegley2009-11-2033-303/+924
|\
| * Updated test/input/sample.datJohn Wiegley2009-11-201-12/+22
| |
| * Added baseline test for "sample.dat" contentsJohn Wiegley2009-11-201-0/+91
| |
| * Several changes to the sample.dat fileAristid Breitkreuz2009-11-201-12/+18
| |
| * Don't rely on the integral value of a booleanJohn Wiegley2009-11-201-2/+5
| |
| * Normalized the value() method for Python numericsJohn Wiegley2009-11-203-27/+37
| |
| * Added more documentation to python/demo.pyJohn Wiegley2009-11-202-60/+239
| |
| * Python is enabled by default if building via acprepJohn Wiegley2009-11-191-1/+1
| |
| * Many improvements to Ledger's Python bindingsJohn Wiegley2009-11-1927-207/+449
| |
| * Updated system dependencies listsJohn Wiegley2009-11-192-42/+112
| |
| * Some improvements to README.textileAristid Breitkreuz2009-11-191-11/+21
|/
* Merge branch 'next'John Wiegley2009-11-1920-607/+1744
|\
| * Added an --unrealized option, for use with bal -VJohn Wiegley2009-11-196-15/+94
| | | | | | | | | | | | When this option is on, then in balance report which show market values, any gains or losses in value will be balanced into a pair of accounts called Equity:Unrealized Gains and Equity:Unrealized Losses.
| * Fixed a debug stringJohn Wiegley2009-11-191-2/+1
| |
| * Don't auto-sort transactions for the balance reportJohn Wiegley2009-11-191-4/+0
| |
| * Changed several pointers to references in filtersJohn Wiegley2009-11-193-50/+48
| |
| * Renamed bool controlling running total calculationsJohn Wiegley2009-11-183-6/+6
| | | | | | | | | | | | It used to be "account_wise", since it only happens for non-account-wise reports. Now it's called just "calc_running_total", so anyone can request it.
| * Decompile all amount expressions for accounts reportsJohn Wiegley2009-11-181-0/+6
| | | | | | | | | | This happens after running through all the post handlers, before running any of the account handlers.
| * It's OK for a report query to be emptyJohn Wiegley2009-11-182-28/+20
| | | | | | | | It's always possible the user only specified a display predicate.
| * Whitespace fixJohn Wiegley2009-11-181-2/+1
| |
| * Changed only_preliminaries to for_accounts_reportJohn Wiegley2009-11-182-5/+5
| |
| * Added an ACCOUNT_GENERATED flagJohn Wiegley2009-11-181-3/+4
| |
| * Allow ! and - operators on sequence valuesJohn Wiegley2009-11-181-0/+14
| |
| * Wasn't serializing date_range_t::end_inclusive memberJohn Wiegley2009-11-181-0/+1
| |
| * Guarded some debug codeJohn Wiegley2009-11-181-0/+2
| |
| * The new period parser is passing all testsJohn Wiegley2009-11-1810-160/+283
| |
| * The new period parser is implemented, but untestedJohn Wiegley2009-11-183-629/+883
| |
| * Added a "range" member to date_interval_tJohn Wiegley2009-11-182-30/+34
| | | | | | | | | | | | This is used to define the beginning/ending ranges of the time period, before it becomes fixed (by calling stabilize()) and then sets the values of start and end.
| * Added several new types for working with dates and rangesJohn Wiegley2009-11-172-0/+615
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | date_specifier_t :: This is like a plain date_t, except it knows what wasn't specified. For example, if 2008/06 is parsed, it becomes date_specifier_t which knows that no day was given. If you ask for the begin() date of the specifier, it will be 2008/06/01; the end() date (which is exclusive) will be 2008/07/01. date_range_t :: A date range is a range of two specifiers, either of which (but not both) may be omitted. This makes it possible to represent expressions like "from june to july", where no day or year is given. The exact dates will be inferred by using the current year, and fixing the range from YEAR/06/01 to YEAR/07/01. That is, the range goes from the begin() of one date specifier to the begin() of the other. date_specifier_or_range_t :: A variadic type that can be either a date_specifier_t or a date_range_t. It's just a wrapper to represent the fact that ranges can be implicit via specifiers (such as, "in june"), or explicit via ranges ("since 2008").
| * Moved date_interval_t::duration_t to date_duration_tJohn Wiegley2009-11-172-108/+106
| |
| * Added a date_traits_t typeJohn Wiegley2009-11-172-26/+68
| |
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-09 07:26:41 +0000