-
Notifications
You must be signed in to change notification settings - Fork 430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved Descendant Tree and Ancestor Tree new features #1873
base: master
Are you sure you want to change the base?
Improved Descendant Tree and Ancestor Tree new features #1873
Conversation
new Descendtree.py was based on recently outdated code. Just re-applied changes to the new version.
This PR should have been named "Improved Descend Tree". It is my mistake. Please let me know when I can create another PR for a similar Tree (Ancestor Tree) that depends on the new gen/plug/report/utils.py pushed by this PR #1873. |
To help explain the nature of the PR, let me share the test results: test_descend_chart_withcolor.pdf |
You should implement colour options in the same way as the graph reports. Perhaps it is time to create a standard option for this? |
In the beginning, I was thinking of doing that too. I wanted to implement a common function in report/utils.py. However, due to the way this Tree Chart uses box styles, I was not able to dynamically modify the box color for each person's gender. To make it work, I end up creating a set of 2 boxes for each gender (normal and bolded) at the outset. There are other graph reports based on graphviz that seem to be able do that. Their names are specific to each report. Maybe there are other ways. I am open to suggestions, to learn more about how the boxes work. PS: I may also handle the creation and switching of the personbox names in a function in utils.py. I feel that in doing so, I am putting a distance between the report and its person boxes. Ideally, I would like to get some help if we can dynamically modify the box color as we navigate along the tree. |
Hi Nick, I refactored the creation and invocation of styles by gender and family boxes to the utils class. I am still using style sheets to control the box color. Is it possible to consider this as a stop-gap solution, for the time being? I am also looking at using graph reports such as family-line and hour-glass. It would be a major rewrite, in my estimation. I like their extra capability, and I am thinking of creating graph-based reports for ancestors and descendants that allow "scale to fit page width only", which is important for me, considering the huge number of nodes for my family. But this is going to take a lot of research and coding. I am not confident that I can do it on my own.
Fix list declaration
Hi Nick, Please review my note on "Re-submit after refactoring" about a stop-gap solution. |
The colors are a nice touch, but comparing the files, the non-color PDFs show the marriage event but the color PDFs seem to duplicate one of the spouses rather than show the marriage event. |
Even though this is a different report, it is also dependent on the same report/utils class, as the result of refactoring the function to handle the color of the boxes. The code changes are similar between the 2 reports. I am requesting that this feature be extended to this report as well. It will make it easier for the reviewing and approval process of the PR easier than having to deal with two.
Test Results for Ancestor Tree Chart |
You can read about the public preview on the GitHub blog. It's mainly for people who merge pull requests, but the improved layout of checks may help developers. |
Fixed by moving the set box color to the end of the method. See new test results
Great to know. Even though it is not for me. Thanks.
…On Fri, Jan 31, 2025 at 11:12 AM Nick Hall ***@***.***> wrote:
Is the link "Try the new merge experience" supposed to be used by the
author of the PR?
You can read about the public preview
<https://github.blog/changelog/2024-12-03-improved-pull-request-merge-experience-now-in-public-preview/>
on the GitHub blog. It's mainly for people who merge pull requests, but the
improved layout of checks may help developers.
—
Reply to this email directly, view it on GitHub
<#1873 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2TV3NKNFEV2B25WPPH36D2NOVHRAVCNFSM6AAAAABV3PIXEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRXHAZTKNZZGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Dave Khuon
|
Add try / except to handle bad data
new Descendtree.py was based on recently outdated code. Just re-applied changes to the new version.