They are both about handling core gnucash objects. Qof was once split out
in an attempt to make it a separate library. This hasn't worked out so there's
no good reason any more to keep this artificial separation.
A few considerations:
- The qof tests are merged into the engine test directory but they are kept as
a separate test entity for now. Several assumptions made in the qof tests
are no longer valid in the context of the engine. (For example if the
pricedb test is added in the same test executable as the qofbook test,
the book creation test fails because it now has 2 collections (pricedb and
book) instead of only one. There are plenty of others like this so merging
the tests needs more careful review and is perhaps best done while converting
to c++/Google test.
- I had to use unique names for the MockBackend classes because apparently the tests were
using a MockClass from another file in the cmake builds, causing several
tests to fail.
This adds unnecessary overhead and also serves as an initial experiment
to greatly reduce the gnc-module based modularization.
Oh, and it fixes the autotools make check failure in standard-reports
which I introduced in the previous commit. The fix was to either
fully gnc-modularize business reports or to go to de-gnc-modularize
standard-reports. I chose the latter as I don't want to add any new
gnc-modules any more at this point.
Changed the names of the register parts and added to the class_init
function gtk_widget_class_set_css_name for use with Gtk+ 3.20 and also
a procedure to use gtk_style_context_add_class for earlier versions of
Gtk+
After the register is loaded, when you first click on a arrow button
the popup appears but the arrow disappears, subsequent pressing and the
arrow toggles as expected. To fix this pack both arrows on the button
and hide the one not active.
Add vertical-align top.
Previously, text fields would have vertical-align:default = centre. This means long transaction descriptions would cause all other fields to be vertically centred. This amendment will ensure the transactional report text are aligned from the top.
Grid lines will be generally be drawn by subtracting 0.5 from the x and
y values apart from the left border of the first column cell has 0.5
added to the x value and the first row cell has 0.5 added to the top
border y value. By doing this the overall dimensions does not change
and all borders are visible.
