[GNC-dev] About Experimental Reports

[Christopher Lam]

Any further preferences or opinions onto the fate of old vs experimental
reports swapping places? I personally don't mind keeping the status quo;
the senior devs suggested the swap. Old reports can either be removed
completely or hidden into the --extras flag until 5.x.

On Tue, 28 Apr 2020, 3:25 am Christopher Lam, <christopher.lck at gmail.com>
wrote:

> Saved configurations, the following can apply:
>
> Most relevant options are transferred unchanged eg account selection,
> dates chosen.
>
> Options which are not present in upgraded reports are ignored.
>
> New options are set to a useful value by default.
>
> The layout of most upgraded reports will be slightly different.
>
> There is no 100% valid upgrade strategy that will satisfy all users.
>
> On Tue, 28 Apr 2020, 12:08 am Adrien Monteleone, <
> adrien.monteleone at lusfiber.net> wrote:
>
>> What happens to saved configs of old reports?
>>
>> Does GC choke when you try to run one?
>>
>> Is an error message generated?
>>
>> If the reports are renamed (and maybe relocated) will this auto-map so
>> the configs still work? Or will that just blow them up entirely anyway?
>>
>> I’ll presume the configs won’t work on new reports since some options
>> either won’t exist or have been changed.
>>
>> I rarely run a default report except for testing or to see what a new
>> user sees when they need help or someone thinks they found a bug. For my
>> own use I have customized configs. (not so many I can’t re-create them, but
>> it will be some effort to figure out how to re-create those reports with
>> the new versions) I’m sure some users out there have extensive saved
>> configs.
>>
>> Regards,
>> Adrien
>>
>> > On Apr 24, 2020 w17d115, at 10:08 PM, Christopher Lam <
>> christopher.lck at gmail.com> wrote:
>> >
>> > Dear Users
>> >
>> > We hope the revamped reports have been useful and welcome to the
>> community.
>> >
>> > With 4.0 round the corner, it is time to consider replacing the old
>> reports
>> > with the experimental ones.
>> >
>> > Balance Sheet and Income Statement (Multicolumn) reports are now well
>> > tested, and can replace the previous ones; however not all options will
>> or
>> > can survive the merge. This means most options will remain unchanged
>> > - accounts selection
>> > - target report currency (optional in new report)
>> > - some display options
>> >
>> > and obsolete options ignored/renamed e.g.:
>> > - asset/liability/equity individual labels/totals
>> > - accounting style rules
>> > - too many subtotal options
>> >
>> > Also the various business reports Customer/Employee/Vendor reports and
>> > Aging reports are now upgraded, and can supplant the old reports
>> > immediately. The newer reports do NOT need to specify an AP/AR account,
>> and
>> > can show related business transactions.
>> >
>> > The question is how to handle old reports: hide (behind a seldom-used
>> > --extras argument), rename, or remove altogether. Any preference?
>> > _______________________________________________
>> > gnucash-devel mailing list
>> > gnucash-devel at gnucash.org
>> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>> >
>>
>>
>> _______________________________________________
>> gnucash-devel mailing list
>> gnucash-devel at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>>
>