The following packages should be installed if you intend to translate or do any development (addons etc): geocodeglib 1.0 (Passed: version 1.0 or greater installed.)įor addon Networkchart, font White Rabbit provides an extremely readable result.GExiv2 : 0.10 (Exiv2 library : not found).Python Image Library (PIL) is needed for cropping images and LaTeX output. rcs installed TBD (Requires version 5.9.4 or greater installed.GtkSpell not found (Requires version 3.0 or greater installed.) (enchant module: not found).Gtkspell enables spell checking in the notes. python-fontconfig not found, (Requires version 0.5.x).osmgpsmap 1.0 (Passed: version 1.0 or greater installed.).The following packages are STRONGLY RECOMMENDED to be installed (needed for geography and charts): language-pack-gnome-xx (Manual check see instructions link) for your Language.librsvg2 (Manual check see instructions link).xdg-utils (Manual check see instructions link). SQLite Database library (sqlite3: 3.31.1) (Python-sqlite3: 2.6.0).Berkeley Database library (bsddb3: 5.3.28) (Python-bsddb3 : 6.2.7).Pango 1.44.7 (Passed: version 1.29.3 or greater installed.).Pycairo 1.16.2 (Passed: version 1.13.3 or greater installed.).Cairo 1.16.0 (Passed: version 1.13.1 or greater installed.).PyGObject 3.36.0 (Passed: version 3.12.0 or greater installed.).GTK+ 3.24.20 (Passed: version 3.12.0 or greater installed.).Python 3.8.10 (Passed: version 3.3.0 or greater installed.).The following packages MUST be installed (Requires the minimum version or greater.): Congratulations, you have the current version. Here is the current output of the Prerequisites Checker:ĭiagnostic Gramplet to help evaluate if Gramps has all prerequisites installed. I have not yet automated the process of jumping from one partial chart to another one.Ĭonsidering the difficulty to get a satisfying global chart, I’d rather recommend you create several partial charts with clear indication of where these charts meet. I wrote a bash script to patch the resulting chart (I chose SVG format to integrate them to my NarrativeWeb server) and add clickable hyperlinks to reference the people pages. I also have many ancestor charts which have the advantage of a predictable number of persons at each generation (except with implexes): 2 n. For instance, I have a descendant chart from the oldest ancestor, but in general descendant charts collect too many people and after ~10 generations the chart becomes too wide. What I finally came up with in recent years where my DB is on the order of 6000 people and still growing is to create smaller “focused” charts on selected parts. This only marginally improved the clarity of the graph, not speaking of the readability of the boxes which were rendered rather small. I output the complete DB as a GraphViz report and I tried to tune the GraphViz source (which required to learn and understand this source) to minimise crossings (if possible) and also to group in different sections of the paper whole branches of the ancestry. Inter-generation connectors tend to cross, making impossible to follow lineage. The mess comes from the fact that a complete family DB is no longer a tree because generations have not the same duration and implexes become relatively frequent when more and more people are involved. I tried this many years ago when I could use a roll-paper A0 plotter but result wasn’t great at all because there were too many people on the graph (only 600 at that time).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |