The current Nav Log is completely inappropriate.
certainly it outputs the main data segment by segment.
However personally and it seems to me that the columns: true track, true heading are of no use to us in flight. the one that interests us is the Magnetic Heading which certainly comes from the previous ones with wind drift.
The boxes are far too small to write in since, like almost everyone, we use an A5 format as a flying board!
As for the missing data, they are legion:
Frequencies, altitudes (min, nominal, max), customizable comments, segment or reporting point, etc.
As for the information, the fonts are unreadable, as for the beacons I think that with some exceptions this information is no longer useful to anyone (GPS has been there) however the frequencies would be more appropriate.
The data in the upper banner is a good idea but also unusable in a cockpit and incomplete missing QFU/code/Chrono/hora/QNH exchanged with the control.... and others with large boxes to write.
It would be good and judicious if the user could define a model of their choice (example Navigation of Foufou allows this). While offering a standard model. Or at least customize. I know this requires defining fields...
Currently I do not use your nav log after generation I export it to reimport it in a model according to my needs.
I will give you an example of e that I use.
I make this remark because a flight generation tool is made to prepare a flight it seems to me, it must therefore be able to generate the usable documentation which is necessary for the flight