Aaron Laws writes:
[snip]
> It would, of course, require a casual user (single desktop
> user with one data file) to have to have a server and client process
> running. In general, I think it would be a needless source of complexity
> since the earlier approach I mentioned (single-processes
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
> 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 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
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
