Treebard Genealogy Software Code Repository

Double-click this file name in your Windows file explorer to run Treebard. First install Python 3.8 or greater, and pip install Pillow. Install the SQLite terminal tool. All of which my grannie could do. There's no excuse for not giving yourself the Treebard experience.

This module handles creating new sources, citations, and assertions, and includes a class that opens assertions dialogs from SOURCES buttons on the events table and the names tab.

This module enables the user to change color schemes app-wide instantly without restarting the app, and includes the Colorizer class which displays the color scheme controls in the preferences > colors tab.

This module takes care of letting the user choose date formats, storing and editing dates, and there's a class that populates the preferences > dates tab with controls.

Provides the Treebard developer with 1) a printing tool that lets the dev make print statements that include line numbers and descriptive strings, without extra typing, and 2) an easy way to make timestamped copies of any Python file when things are going well, in case the dev should want to roll back to this version.

This is a class that displays controls on the little TabBook where the person image gallery is opened, on the right side of the person tab. The user can record, prioritize, and delete to do list items specific to the tree where the do list appears.

This module creates the conclusions table on the persons tab, which displays the user's conclusions about events and attributes linked to the current person.

This module populates the families table on the person tab above the conclusions table.

These are file utilities that allow the user to create, copy, rename, and delete family trees.

This module creates a dialog which can display images linked to a current person, current place or current source.

These constants, functions, and queries are used in `gedcom_export.py` and `gedcom_import.py`.

Treebard exports its data to any genealogy application that can import GEDCOM v. 5.5.1.

Treebard imports most specs-tag data from GEDCOM v. 5.5.1 and puts the rest into an exceptions log with suggestion for how the user might get the data into Treebard via the user interface.

This module will allow the user to perform simple modifications to images such as resizing, cropping, adding borders and text, or to link captions to an image.

This module initializes display of specific parts of the Treebard interface.

This module helps the user put images and other media into a tree and link them to elements of the tree. It also lets the user select from default or user-selected default images for male, female, unknown gender, place, and source, for those elements which he has no image for.

These are strings imported to the various modules where error messages are used.

These are strings used to populate the right-click context-sensitive help dialogs.

When the user creates a new family tree, this module populates a UNIGEDS database with Treebard's built-in types and a few other elements that Treebard needs in order to run.

This module contains a class that opens Treebard's notes dialog, where the user can create, delete, link and edit notes. In Treebard, any note can be linked to any number of elements instead of the user's having to copy and paste notes that have to be repeated from element to element.

This module opens the splash screen and opening dialog when the app is first started.

This tool is used to generate fictional names, birth dates and death dates when adding people to the tree for testing purposes. This simple tool is the only thing that prevents me from creating tree people with names like "Fardwick Pleabargain Cheesebottom IV".

This module takes care of sorting through a person's various names and appellations as well as letting the user create and delete people.

This module lets the user create places and place names. It has a class that populates the new and duplicate places dialog which gives the user a chance to make places with the same name without having them be the same place. Nested places are taken care of, such as "Paris, France" vs. "Paris, Texas" so they are two completely different places. Also, Treebard allows Dallas to have two different enclosing places--e.g. "Texas, USA" and "Republic of Texas"--to be Dallas' parent place without creating two different Dallases.

SQLite queries are isolated here so the Python code will be more readable.

This module redraws pertinent portions of the Treebard interface when the user adds, deletes, or edits a field.

In addition to tracking related people, Treebard lets the user add unrelated people to the database along with the role they played in family events such as "flower girl", "arresting officer" or "neighbor". These folks are treated exactly like anyone else in the tree, which will come in handy when Doris next door turns out to be AUNT Doris.

This class has been used to create a person search dialog and can be used to create search tools for other elements also.

This is a start on the TYPES tab in the main notebook of the interface. It stores function where collection of name types, event types, role types, etc. can be added to by user input.

There are a few utilities here that are imported to other modules.

Treebard uses custom widgets that can be detected by sub-class so that color schemes can be instantly changed app-wide without restarting the app.

The tables in this database store data that is used app-wide no matter which tree project is currently open. On the other hand, databases which store information specific to a single family tree always have the extension `.tbd`.

This empty Treebard database works with the UNIGEDS schemas. It is copied when the user makes a new tree, and the copy is given a name suggested by the user.

This is a hodge-podge of imaginary characters, some related to each other, some linked to public domain images, and mostly created during development for testing purposes. There was an initial attempt to create a storyline for the first few persons that were input. It's actually a pretty interesting story. There's no connection between the persons depicted in the public domain photos and the fictional people in the sample tree.

These are the images that the user adds to the tree which can be linked to persons, places, and sources.

These are Treebard's built-in default images which display for persons, places or sources that the user has not linked any images to.

The two-tone icons I've been using on Treebard's icon menu were created by interactivemania. These are the copies I use, as well as the image used on Treebard's splash screen.

These are images previously used on the SE-corner resizing button, the title bar resizing and close buttons, and the Treebard logo which is still used.

These are the public domain tree images that take turns appearing on Treebard's opening dialog when opening the program.

This is the specially-formatted icon that displays the Treebard logo on title bars and browser tabs.

This is the collection of two-tone menubar icons I use in Treebard's main view. The collection is included here in order to comply with interactivemania's licensing requirements.

This is the .ged file I've been using during development.

This README file and the Unlicense are the only parts of Treebard which still exist at the Github repo. The README file is the most comprehensive and up-to-date summary of what Treebard is all about.

Treebard is free, open-source, public domain software. You can use this code for any purpose without permission, paying royalties, restriction or acknowledgment of where you got the code. You can donate for Treebard's contribution to your project (if you can find me). "No corporate empires were harmed in the making of this app."

I've added to this file of instructive examples just about every time I had to look up how to do anything with SQLite. By now I rarely have to look anywhere else for examples of how to use SQLite.

Some notes on HELP topics for a Treebard Users Manual that hasn't been started.