Treebard GPS
Skip Navigation
Home
Help
Search
Welcome Guest. Please
Login
or
Register
.
Treebard GPS
Oops, there was an error!
current-code
todays-commit
python-modules
root
assertions
colorizer
dates
dev-tools
do-list
error-messages
families
files
findings-table
gallery
graphics
images
links
main
messages
notes
message-context-help
opening
person-maker
persons
places
query-strings
repositories
right-click-menu
roles
scrolling
search
toykinter-widgets
utes
widgets
sqlite
global-db
default-new-tree
great-lakes-heatons
sample-tree
gregory-tree
default-untouched
global-untouched
images
tree-images
default-images
menu-icons
titlebar-images
openpic-images
favicon
extra-default-images
interactivemania-icons
misc
readme
license
use-sqlite
gui-features-oughta-be
features-good
intuitive
gedcom
misfeatures
reviews
mis-assertions
set-record-straight
named-twice
poor-skeleton
brick-wall
stumped-no-more
brick-wall-registry
treebard
treebard-thinking
treebard-code
treebard-samples
treebard-philosophy
feature-requests
programming-gui
widgets
functionalities
coding-general
General
General Discussion
forum-instructions
Treebard GPS:
setting the record straight since 2020
How genealogy software should work
Oops, there was an error!
You must be logged in to access this feature.
Click here
to login.
Treebard Genealogy Forum is for suggesting changes in family tree conclusions and software design.