Any rework will require stabilising the reports first, removing
unintelligible hacks, and updating to modern scheme (which is now
approaching V8 quality and speed). The current state of report code
reflects the tooling available about 20 years ago.
So the following will be on the TODO list before
I don't know how it fits into this rework, but I would like to see a more
general framework which supports reports with 'items' down the side and
'periods' across the top. I put them in quotes because they are a bit
general. I've worked with an accounting system in the past which allowed
general
> On Jun 7, 2018, at 1:14 PM, John Ralls wrote:
>
>
>
>> On Jun 7, 2018, at 12:49 PM, Carsten Rinke wrote:
>>
>> Hi,
>>
>> this takes up a discussion with John and Christopher in PR#360 (and I am
>> happy to see that is was merged :-D )
>>
>> As the discussion turned away from the
Op donderdag 7 juni 2018 22:14:34 CEST schreef John Ralls:
> We'd like to better separate the data retrieval and summarization from the
> presentation, perhaps with an intermediate format. We'd also like to be
> able to use something lighter and more portable than WebKitGtk for
> in-program report
> On Jun 7, 2018, at 12:49 PM, Carsten Rinke wrote:
>
> Hi,
>
> this takes up a discussion with John and Christopher in PR#360 (and I am
> happy to see that is was merged :-D )
>
> As the discussion turned away from the actual proposal of a test for the
> report definition, I'd suggest to
Hi,
this takes up a discussion with John and Christopher in PR#360 (and I am
happy to see that is was merged :-D )
As the discussion turned away from the actual proposal of a test for the
report definition, I'd suggest to move it to this channel.
John:
You were mentioning that you and
