In the latest version of FamilyTreeView (v0.1.109), I added a feature that has been requested several times (here and here by @Urchello): a way to display dates compactly. The two images below show dates and their compact representation. Please keep in mind that the representation is just a first attempt/draft.
Possible improvements, open questions and discussion:
-
~ is used for three modifiers (estimated, calculated, about). Are there any ideas for using other symbols that are more intuitive to understand? I was thinking about using the following mathematical symbols (and their meaning in maths):
- ± (plus-or-minus)
- ≈ (almost equal to)
- ≃ (asymptotically equal to)
- ≅ (approximately equal to)
The problem with all of them will be that it’s not intuitive which symbol means what (maybe not even for those who know the different mathematical meanings of the symbols).
I also feel that “calculated” is more of an indicator of the interpretation of the source(s)/citation(s) of the date, rather than an indicator of the quality of the date. So maybe it is acceptable to ignore “calculated” in the compact date representation?
-
If “estimated” and “after”/“before” appear together, the combinations ⪆ or ⪅ could be used to save one character (more compact)
-
I’m not sure if the suffix + and − are intuitive (meaning “from” and “to”). As an alternative, I can think of using … before the date for “to” and after the date for “from”, but I’m not sure that would be more intuitive either. I’m open to your suggestions.
-
In the current implementation, – is used for a range (“between A and B” → “A – B”) and … for a span (“from A to B” → “A … B”). I think … for a span is not very intuitive, but I cannot think of a better alternative. Maybe – and … should be swapped in their meaning?
The current implementation for the compact date display is just only a draft as far as the symbols used are concerned. As always, please let me know your suggestions.
I also want to let you know that as of v0.1.104 there is a new option (in the Interaction tab) to hide the expanders when printing/exporting, and padding is added when printing/exporting to ensure that everything (e.g. all badges) is exported correctly.
[This post was copied from the original one which was moved to a new topic.]