slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: misc

Browse Source
This commit is contained in:
Simon Michael 2011-05-28 04:13:03 +00:00
parent 8c0d95bc33
commit bc8cd4d211
3 changed files with 80 additions and 132 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
HCAR-201105.tex Normal file
View File

@ -0,0 +1,53 @@
% http://www.haskell.org/pipermail/haskell/2011-April/022720.html
% http://haskell.org/communities/05-2011/template.tex
% http://haskell.org/communities/05-2011/hcar.sty
\documentclass{scrreprt}
\usepackage{paralist}
\usepackage{graphicx}
\usepackage[final]{hcar}
%include polycode.fmt
\def\EMailRepl#1#2{\DoEMailRepl{#2} #1@@\End}
\def\DoEMailRepl#1#2@@#3\End
{\if!#3!#2\else\DoDoEmailRepl{#1}{#2}#3\fi}
\def\DoDoEmailRepl#1#2#3@@{#2#1#3}
\def\EAt{ @@ }
\begin{document}
\begin{hcarentry}{hledger}
\report{Simon Michael}
\status{Ongoing development; suitable for daily use}
\participants{}% optional
\makeheader
hledger is a haskell port and friendly fork of John Wiegley's ledger. It
is a robust command-line accounting tool with a simple human-editable data
format. Given a plain text file describing transactions, of money or any
other commodity, hledger will print the chart of accounts, account
balances, or transactions you're interested in. It can also help you
record transactions, or convert CSV data from your bank. There are also
curses and web interfaces. The project aims to provide a reliable,
practical day-to-day financial reporting tool, and also a useful library
for building financial apps in haskell.
Since hledger's last HCAR entry in 2009, hledger became cabalised, had 10
non-bugfix releases on hackage, split into multiple packages, acquired a
public mailing list, bug tracker, fairly comprehensive manual,
cross-platform binaries, and has grown to 5k lines of code and 15
committers. 0.14 has just been released, with 5 code committers.
The project is available under the GNU GPLv3 or later, at http://hledger.org .
Current plans are to continue development at a steady pace, to attract
more developers, and to become more useful to a wider range of users, eg
by building in more awareness of standard accounting procedures and by
improving the web and other interfaces.
\FurtherReading
\url{http://hledger.org}
\end{hcarentry}
\end{document}

129
HCAR-HOWTO
View File

@ -1,129 +0,0 @@
From: Janis Voigtlaender <voigt@tcs.inf.tu-dresden.de>
Newsgroups: gmane.comp.lang.haskell.cafe,gmane.comp.lang.haskell.general
Subject: Call for Contributions - Haskell Communities and
Activities Report, May 2009 edition
Date: Wed, 01 Apr 2009 15:08:49 +0200
Organization: Dresden University of Technology
Dear Haskellers,
so much has happened in the Haskell world in the past months.
Therefore, I would very much like to collect contributions for
the 16th edition of the
================================================================
Haskell Communities & Activities Report
http://www.haskell.org/communities/
Submission deadline: 1 May 2009
(please send your contributions to hcar at haskell.org,
in plain text or LaTeX format)
================================================================
This is the short story:
* If you are working on any project that is in some way related
to Haskell, please write a short entry and submit it. Even if
the project is very small or unfinished or you think it is not
important enough -- please reconsider and submit an entry anyway!
* If you are interested in any project related to Haskell that has not
previously been mentioned in the HC&A Report, please tell me, so that
I can contact the project leaders and ask them to submit an entry.
* Feel free to pass on this call for contributions to others that
might be interested.
More detailed information:
The Haskell Communities & Activities Report is a bi-annual overview of
the state of Haskell as well as Haskell-related projects over the
last, and possibly the upcoming six months. If you have only recently
been exposed to Haskell, it might be a good idea to browse the
November 2008 edition -- you will find interesting topics described as
well as several starting points and links that may provide answers to
many questions.
Contributions will be collected until the submission deadline. They
will then be compiled into a coherent report that is published online
as soon as it is ready. As always, this is a great opportunity to
update your webpages, make new releases, announce or even start new
projects, or to talk about developments you want every Haskeller to
know about!
Looking forward to your contributions,
Janis (current editor)
FAQ:
Q: What format should I write in?
A: The required format is a LaTeX source file, adhering to the template
that is available at:
http://haskell.org/communities/05-2009/template.tex
There is also a LaTeX style file at
http://haskell.org/communities/05-2009/hcar.sty
that you can use to preview your entry. If you do not know LaTeX, then
use plain text. If you modify an old entry that you have written for an
earlier edition of the report, you should receive your old entry as a
template soon (provided I have your valid email address). Please modify
that template, rather than using your own version of the old entry as a
template.
Q: Can I include images?
A: Yes, you are even encouraged to do so. Please use .jpg format, then.
Q: How much should I write?
A: Authors are asked to limit entries to about one column of text. This
corresponds to approximately one page, or 40 lines of text, with the
above style and template.
A general introduction is helpful. Apart from that, you should focus on
recent or upcoming developments. Pointers to online content can be given
for more comprehensive or ``historic'' overviews of a project. Images do
not count towards the length limit, so you may want to use this
opportunity to pep entries up. There is no minimum length of an entry!
The report aims at being as complete as possible, so please consider
writing an entry, even if it is only a few lines long.
Q: Which topics are relevant?
A: All topics which are related to Haskell in some way are relevant. We
usually had reports from users of Haskell (private, academic, or
commercial), from authors or contributors to projects related to
Haskell, from people working on the Haskell language, libraries, on
language extensions or variants. We also like reports over distributions
of Haskell software, Haskell infrastructure, books and tutorials on
Haskell. Reports on past and upcoming events related to Haskell are also
relevant. Finally, there might be new topics we do not even think about.
As a rule of thumb: if in doubt, then it probably is relevant and has a
place in the HCAR. You can also ask the editor.
Q: Is unfinished work relevant? Are ideas for projects relevant?
A: Yes! You can use the HCAR to talk about projects you are currently
working on. You can use it to look for other developers that might help
you. You can use it to write ``wishlist'' items for libraries and
language features you would like to see implemented.
Q: If I do not update my entry, but want to keep it in the report, what
should I do?
A: Tell the editor that there are no changes. The old entry will be
reused in this case, but it might be dropped if it is older than a year,
to give more room and more attention to projects that change a lot.
Do not resend complete entries if you have not changed them.
--
Dr. Janis Voigtlaender
http://wwwtcs.inf.tu-dresden.de/~voigt/
mailto:voigt@tcs.inf.tu-dresden.de

30
NOTES
View File

@ -65,9 +65,6 @@ Features: reads transactions in journal, timelog, or CSV format; handles multi-c
*** website *** website
**** add related links:
http://darcsden.com/dbp/housetab-multi
**** add tables of contents **** add tables of contents
**** integrate binaries, demo, pastebin **** integrate binaries, demo, pastebin
*** faq *** faq
@ -456,6 +453,30 @@ NOTE: This is the "developers' quick bug list", which predates the
web-based bug tracker and is still used sometimes by hledger developers web-based bug tracker and is still used sometimes by hledger developers
comfortable with org-mode. comfortable with org-mode.
*** strange balancing failure
2011/01/01 Example
Assets:Brokerage:TESTA 188.424 TESTA @ $76.61
Assets:Brokerage:TESTB 1,809.282 TESTB @ $15.60
Assets:Brokerage:TESTC 384.320 TESTC @@ $5,000.00
Assets:Brokerage:TESTC 5.306 TESTC @@ $68.18
Equity:Opening Balances
$ hledger -f t.j bal
hledger: could not parse journal data in t.j
could not balance this transaction (real postings are off by $-4,931.82)
2011/01/01 Example
Assets:Brokerage:TESTA 188.424 TESTA @ $76.61
Assets:Brokerage:TESTB 1,809.282 TESTB @ $15.60
Assets:Brokerage:TESTC 384.320 TESTC @@ $5,000.00
Assets:Brokerage:TESTC 5.306 TESTC @@ $68.18
Equity:Opening Balances
*** parsing: timezone should be supported in historical price records, elsewhere ? (greenskeleton)
https://gist.github.com/972281
*** linux 32 binary fails on ubuntu 11.04 due to libc6 gconv file path change (greenskeleton)
https://gist.github.com/972289
*** #35 wludwick hledger-web startup issue *** #35 wludwick hledger-web startup issue
*** parsing: recursive file includes cause a hang *** parsing: recursive file includes cause a hang
echo "!include rec" > rec echo "!include rec" > rec
@ -532,6 +553,7 @@ http://msdn.microsoft.com/en-us/library/ms714415(v=VS.85).aspx
*** inspiration *** inspiration
http://community.haskell.org/~ndm/downloads/paper-hoogle_overview-19_nov_2008.pdf -> Design Guidelines http://community.haskell.org/~ndm/downloads/paper-hoogle_overview-19_nov_2008.pdf -> Design Guidelines
** features ** features
*** take port from base-url when appropriate
*** parsing: support --options (?) *** parsing: support --options (?)
*** parsing: canonicalise account names to be case-insensitive ? *** parsing: canonicalise account names to be case-insensitive ?
*** parsing: period expressions should allow interval at the end *** parsing: period expressions should allow interval at the end
@ -576,6 +598,8 @@ ACCOUNTS
expenses ; :number: 6000 expenses ; :number: 6000
rent ; :number: 6010 rent ; :number: 6010
or: http://furius.ca/beancount/examples/demo.ledger
*** ignore/support ledger assert statements *** ignore/support ledger assert statements
; Assertion directives Options ; Assertion directives Options
; These can occur in many places: ; These can occur in many places: