I still don't know if silverfox would, if given the option, ever use Ancestral Lines Pairing System on an Ahnentafel report made by FTM.
I don't need examples myself of presenting genealogies along ancestral lines. I already understand it and have books in my personal library that exemplify it. I was suggesting rather that you might have better luck getting your idea implemented if you offered up a sample PDF report demonstrating the concept. If it's buried in a forum thread, it's less likely to gain traction or even be read. To that end, it deserves its own thread in the forum.
For this thread, I hope we can finally get to a discussion of the merits of Ancestral Lines Pairing System.
-------------
P.S.
silverfox:
"I can see where this would take a bit of programming to get done and probably take more memory than the current only option - the ahnentafel register report - but I think it is so much clearer to read for a reader."
Indeed this would require more time to implement because it doesn't involve substituting a new number for an existing number. It's a wholesale change in presentation. I don't think that this format, however, would inherently require any more memory than the traditional Ahnentafel and Register style reports. At the end of the day it's merely changing the order in which the *same* data are displayed. The overhead is largely the same.
(Hopefully we can keep this final exchange relegated to a post script and resume this discussion in a thread devoted specifically to your suggested enhancement. )
I don't need examples myself of presenting genealogies along ancestral lines. I already understand it and have books in my personal library that exemplify it. I was suggesting rather that you might have better luck getting your idea implemented if you offered up a sample PDF report demonstrating the concept. If it's buried in a forum thread, it's less likely to gain traction or even be read. To that end, it deserves its own thread in the forum.
For this thread, I hope we can finally get to a discussion of the merits of Ancestral Lines Pairing System.
-------------
P.S.
silverfox:
"I can see where this would take a bit of programming to get done and probably take more memory than the current only option - the ahnentafel register report - but I think it is so much clearer to read for a reader."
Indeed this would require more time to implement because it doesn't involve substituting a new number for an existing number. It's a wholesale change in presentation. I don't think that this format, however, would inherently require any more memory than the traditional Ahnentafel and Register style reports. At the end of the day it's merely changing the order in which the *same* data are displayed. The overhead is largely the same.
(Hopefully we can keep this final exchange relegated to a post script and resume this discussion in a thread devoted specifically to your suggested enhancement. )