Project News Story Screenshots Download/CVS Manual About Postcards Summary

About Features QHacc isn't exactly feature-rich. It's small and simple, and somewhat fast. But it does have some things that I think are worth mentioning: Atomic Operations Account Reporting Support for multiple currencies Sub-Accounting Line/Bar/TwoBar/Pie Graphs of accounts (snapshot) Printing of reports and graphs Cut-Copy-and-Paste transactions User configurable transaction types American, European, or Year-first date formats Configurable interface Memorized transactions Double-Entry or Single-Entry bookkeeping Split transactions Auto-increment check numbers on checking accounts Type-Ahead text boxes Reconciliation window Drag and Drop Auto-completion of frequently-used transaction entries MySQL database support PostgreSQL database support SQLite database support Internationalization-able. Import/Export to/from various sources, like XML or QIF Support for CVS Generally pretty stable. (At least, more stable than many things which are less stable.) Based exclusively on QT, so it should be widely compilable (it's not just for Linux) QHacc or KHacc? QHacc recently split into two projects: QHacc and KHacc. The two projects are share an enormous amount of code, but there are some differences. Most notably, KHacc features very tight integration with the KDE project. QHacc, on the other hand, doesn't rely on any libraries besides Qt's. Generally, KHacc is meant to be run totally from the GUI provided in KDE, while QHacc features more command-line functionality. What does this mean? QHacc has the following added features: Better interface for some plugins The Cliimp! command-line transaction entry Command-line options for: All reports, including journals Transaction lists Account lists and balances Conversely, KHacc has some stuff QHacc doesn't, like: Default accounts on startup Code to avoid common user errors Tight integration into KDE: KDE's help system KDE's print system KDE's i18n and l10n support Potentially larger user base So, which is right for you? Who knows? Looking purely at downloads, it appears that KHacc is enjoying faster acceptance from the masses, and this could mean more help in the future if you run into problems. Personally I still like QHacc more, and all my development is on QHacc initially and then ported to KHacc. The code is virtually identical for both projects, and in fact, the data files are completely interchangeable between them, so it's really a matter of preference.