Open MichalVasut opened 1 year ago
The different methods in the first two instances are really down to the fact that the first group are using one of the graphic libraries, whereas the second group is using 'ordinary' html.
I think as we develop the facility library we will have the objects such as the popup detail window as a standalone widget ready to use by all views. This will make it easier to lend a consistency to the overall project. Through the Hacktoberfest we have not really had chance to fully develop these themes and so there are half a dozen or so ways of doing most things currently represented within the codebase. Over the coming weeks we will have an opportunity to analyse and report on what can be done to place a better unification on structures and standards.
This is a stage that all codebases go through as it moves into a more mature state and is nothing that we cannot cope with provided we all work together.
Sure, therefore I've created the issue - not to necessarily solve it immediately, but to not forget it. 😉
It would be nice to agree on some consistent behaviour (not only) in using person detail info. What I mean? There are multiple variations how the person detail behaves:
Dynamic tree
,Ancestor Webs
,Fanchart
,Fractal Tree
Family Group View
,Surnames List
,Ahnentafel Ancestor List
Family Timeline
Printer Friendly
(yeah I know about this, but I'll fix it when this issue will be solved)