My collection and it’s information is getting bigger and bigger and the reports (PDF) are getting more and more confusing with every every information added. So I had some ideas regarding the styling of the PDF-reports lately, but I don’t know whether any (or all) of them are feasible or not. Nevertheless I’m gonna share my thoughts with you.
Idea one: Add a grouping level to the report
It would be nice to have the possiblity to add a grouping-attribute to one of the selected fields (in my example, it would be the very first one “Interpret/Gruppe”)
Idea two: Add stacking-option to fields
The fields are getting smaller and smaller the more you add to a report - and sometimes you really need them and can’t get rid of some informations just to maximize the field lengths. Therefore it would be nice to add a stacking-attribute to some fields, means: stacked fields are not displayed one after another, they are displayed one below other (in my example, I made 4 groups of stacked information and a last one with no stacking).
Idea three: add minimal styling options to fields
It would be nice to have the possibility to add at least bold- and italic-settings to fields.
I’m adding some documents (export from clz, quick-and-dirty exmample to visualize, settings) to show what I mean (and I’m sorry that I forgot to change the language before creating the example).
I’m wondering what you guys think about these ideas.
It looks pretty cool. With a good user interface that is understandable (and doesn’t require the user to learn their field selection screen again) it would be very awesome.
Would you like choose a field, and always be presented with “one stacking” option for an extra field?
Or would you just select 20 fields, and it would just stack the “11th” one under the 1st one?
I’ll take your idea for the ideas list. Thank you!
Nice to hear that the idea has cleared the first hurdle and made it at least to your list
I think it would be enough if one can just stack fields that are mentioned below each other in the UI. It doesn’t make any sense to stack field 11 under field 1 (and I think this would make the UI too complex). As an Idea: I would just give every field a boolean-selector for the stacking and if this is true, then the field would stack on the report just below the field mentioned before in the UI.
To take my example: If I should do something similar, I would do it the following way:
