The latter is the prefix format prescribed by gsettings itself. The former never
was an issue until flatpak decided to not accept the shorter prefix when
requesting a settings migration from host system to flatpak sandbox.
In order to allow for migration, keep the old schema around in
org.gnucash.GnuCash.deprecated.gschema.in
While we're at it, make the new prefix an internal implementation detail.
There's no need for it to be visible to the rest of the gnucash code.
- Move Macos specific bits to its own source file. As this is objective-c use .mm extension
- Use common function signature for Macos and Windows init function and include via common header file
This is just a first start, more refactoring will follow in later commits.
The idea is to have an application class that provides the basic framework
gnucash and gnucash-cli will become specializations of this class adding their
specific functionality. I'm splitting this over several commits to be able to
keep track of all the many changes.
This tool is intended to expose certain gnucash functions to a command line interface.
The first one is --add-price-quotes. This option currently also exists in gnucash.
It will be marked deprecated there. Future extensions to this can be things like
report generation, non-interactive imports,...
When the path head is changed the associations are not updated so this
change adds a dialog to ask if you want the old relative paths updated
to absolute ones and whether to update existing absolute paths to new
relative ones.
None of these gnc-modules have any particular construction or destruction
code except for loading the modules they depend on. These dependencies
are all loaded anyway in other ways so for these libraries the gnc-module
wrapper code brings no benefit.
Simple report to visualise lots (business and non-business) in a
spreadsheet. Each column is a unique lot, and each row is a unique
transaction. The lot balance, and the associated lot invoice are also
included.
Each transaction is analysed to render the split in the lot column,
and non-lot splits are rendered in a last column.
An account must be chosen in options, and all splits in the specified
date range will be scanned to find unique lots which are all reported
in order of first appearance.
A heavy APAR account will lead to an impractical number of columns
signifying multiple lots, therefore date-range filtering and
description filtering are both encouraged to narrow down the list of
transactions.
