Copy and paste this code into the official Treebard file structure (see treebard.com/repo.html) with the official designated Treebard file names and you're good to go. Each file's correct name and path, as well as its last-changed date, will be found at the top of that file.

Sub-boards: root, assertions, base, dates, dev-tools, do-list, element-types, events-table, families, gallery, gedcom-constants, gedcom-export, gedcom-import, graphics, main, media, messages, message-context-help, new-tree, notes, opening, person-maker, persons, places, redraw, roles, search, setup, sources, query-strings, user-formats, widgets

These are sample database files that work with the current version of Treebard which can be read here or downloaded from https://treebard.com/download. See treebard.com/repo.html for the app's directory structure.

Sub-boards: tbard-db, unigeds-db, sample-tree, sample-untouched

Descriptions of the various directories where Treebard stores images, and their respective reasons for existing.

Sub-boards: tree-images, default-images, menu-icons, openpic-images, favicon, extra-default-images, interactivemania-icons

Treebard is the first genieware to use UNIGEDS as a back-end. UNIGEDS means "Universal Genealogy Data Structure". It can be used by any genieware for its primary data. The topic is for posts about essential database design considerations such as relationships between data (cardinality), and normalization, in the context of genealogy. Like Treebard, UNIGEDS is public domain, free, and open-source. It's also meant to replace GEDCOM: "Don't share GEDCOM, just share the whole tree!"

What genieware should be able to do or do better.

Genieware should be easy to learn and use, no matter how many complicated things it has to do behind the scenes. That "steep learning curve" you've heard so much about is an excuse for not taking the user into account when designing the software.

It's not necessary to say where you found the misfeature, but please register your opinion here so Treebard can demonstrate a correction if applicable. What's wrong with existing genieware, applications, online and stand-alone?

Here's what Treebard looks like so far. Not up to date.

I'll be using this as a blog or venting post to talk to myself and anyone who's interested in genealogy software about why the Treebard project exists and what it's intended to accomplish.

This is the opposite of the case where two real people are combined into one pseudo-person. In this case, one person is treated as two or more people due to a name change or double identity.

After years of creating websites and then using Python to make my own standalone app, I'm still a beginner. I'm not here to brag about my code, but some of the functionalities I've developed are worth passing on. Improvements are always welcome.