Hi Geert,
just two bits of thoughts from my side:
Am Sonntag, 24. Dezember 2017, 17:34:51 schrieb Geert Janssens:
> 1. Use of namespaces.
> ... nested namespaces ...
Yes, absolutely. I have quite some experience with C++ libraries and
applications and I made very positive experience with this s
Op maandag 25 december 2017 00:34:39 CET schreef John Ralls:
> > On Dec 24, 2017, at 8:34 AM, Geert Janssens
> > wrote:
> > We can debate whether our internal code can/should have "namespace gnc;"
> > in
> > headers only or in source files as well. For libgnucash I'd go for the
> > latter. It The
Op maandag 25 december 2017 00:34:39 CET schreef John Ralls:
> > On Dec 24, 2017, at 8:34 AM, Geert Janssens
> > wrote:
> >
> > 2. Versioning.
> >
> > We currently use a version scheme gigantic.major.minor[-build]. Like
> > 2.6.19
> > (and an optional -2 if we had to release more than once to ge
Op maandag 25 december 2017 17:34:22 CET schreef Christian Stimming:
> Hi Geert,
>
> just two bits of thoughts from my side:
>
> Am Sonntag, 24. Dezember 2017, 17:34:51 schrieb Geert Janssens:
> > 1. Use of namespaces.
> > ... nested namespaces ...
>
> Yes, absolutely. I have quite some experien
> On Dec 25, 2017, at 9:24 AM, Geert Janssens
> wrote:
>
> Op maandag 25 december 2017 17:34:22 CET schreef Christian Stimming:
>> As for the namespace aliases such as "namespace gia =
>> gnc::import::aqbanking", those must not appear in header files, but may
>> appear in cpp files. However, I
On Mon, 2017-12-25 at 17:34 +0100, Geert Janssens wrote:
> Agreed indeed. For example in my work on the importers I have
> introduced a
> strict separation of import functionality and gui. So the non-gui
> parts of the
> importer should move to libgnucash eventually as I want them to
> bepart of
> On Dec 25, 2017, at 1:01 PM, Lincoln A Baxter wrote:
>
> On Mon, 2017-12-25 at 17:34 +0100, Geert Janssens wrote:
>> Agreed indeed. For example in my work on the importers I have
>> introduced a
>> strict separation of import functionality and gui. So the non-gui
>> parts of the
>> importer
On Sun, Dec 24, 2017 at 11:34 AM, Geert Janssens wrote:
> While we're working hard to get 2.8 ready for official release, the current
> state of the code keeps reminding me of a few design related topics I would
> like to discuss for the development cycle after 2.8 has been released.
>
> We're st
On Mon, Dec 25, 2017 at 6:26 PM, John Ralls wrote:
>
>
> > On Dec 25, 2017, at 1:01 PM, Lincoln A Baxter
> wrote:
> >
> > On Mon, 2017-12-25 at 17:34 +0100, Geert Janssens wrote:
> >> Agreed indeed. For example in my work on the importers I have
> >> introduced a
> >> strict separation of import
