Additional checks and auxiliary evaluation methods.
Interface for all depreciation methods which can be plugged into the system and called by reflection.
Standard depreciation, linear on three years, for volatile electronic technologies.
Standard depreciation, linear on five years, for long-living technologies.
Result of an automated depreciation call.
Holds the central routines for evaluating a Ledger, plus some simple common subroutines.
Generated source of a graphical user interface (GUI) for command line processing.
The complete graphic user interface for the BandM booking application.
Is re-defined for to render account table data as
The field "objects" is our invention and holds AccountGroups and Accounts, in depth-first order.
BookingTable must be redefined for special rendering: color, tooltips and spanning cells.
Delivers the "Sub-Model"/Object to display when asked for a certain row/column.
MISSING FIXME background color, hori scroll GEHT NICHT !?!? Standardloesung in MessageStore scheint nicht benutzt !?!?
Tee-shaped table for one account, used in OneAccountTable and for Assets.
Moves and bps are in parallel, containing the whole move and the part related to the currently displayed account.
Main file of the "BandM booking tool".
Generated source for command line processing.
Parser and translator from XML tdom input model into the umod model.
Multi-lingual translations catalog, generated from XML source.
metatools muli package, see the translation file base/translations.muli
This tool does (currently) NOT support entering data interactively. Instead, all data (configuration, account plan and ledger) has to be entered into XML files, using the "d2d" encoding. The formats for all these files are defined in eu_bandm_booking.dd2. This is automatically translated into eu_bandm_booking.dtd.
The first step when processing the mentioned data is parsing the input text into
a tdom model.
decodes the most important infos to a more structured
a umod model.
Its structure is defined by
and also depicted by a
in the user documentation.
The tool DOES support interactive visualization, and generation of a year's balance, report and carry bookings.
The program's architecture is modular, and the top-level control flow is as follows:
Maincentral entrypoint and main code, calls and uses | (Options <-- generated from base/options.xml | (Translations <-- generated from base/translations.muli | (Book <-- generated from book/Book.umod |
Gui| | AuxCellRenderer | | (GeneratedGui <-- generated from base/options.xml
(Please cf. the user documentation, in German language)