Providing a condensed "engineering" report format #217
Unanswered
RichardPfr
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Here some features, ideas and contents to be included in such a report from our/ my side: possible features
contents
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Note
This post is supposed to be a collection of ideas and a place to discuss them, whether these ideas are feasible or not. For the actual development of this see pyroll-project/pyroll-report#19
Idea
As was hinted at in recent discussions a more condensed report format may be necessary which, in contrast to the current report, only shows the most substantial dimensions. As an "engineering" report it should provide a quick overview over the most needed dimensions, optimally also in graphically form. If more informations are needed one can still decide to output the current "scientific" format which contains all dimensions, as is the case currently.
One limitation of this might necessary be that this "engineering" report is less flexible and more static. The dimensions to be shown may need to be set beforehand and therefore may not be able to be changed easily. While the "scientific" one extends dynamically with additional packages beeing loaded, an "engineering" one like this might not.
This is all to be seen when developing it though.
Question
For this reason we ask you, what...
Below we already gathered some ideas from our side.
Please feel free to also give us your opinion on any ideas we or others posted.
Beta Was this translation helpful? Give feedback.
All reactions