GDBI is a genealogy program integrator. It includes an editor and the lifelines report language. It interfaces to 3 GEDCOM databases: phpGedView, GenJ, and jLifelines. At the core is a common Java API to simplify adding more databases and editors.
This release adds an import feature for reading in another GEDCOM. It also has fixes for the merge feature added in the previous release. Import and merge are similar in that they both involve a 2nd GEDCOM. Import is the relatively simple process of adding everything from the 2nd file. A merge requires finding overlapping people in the 2 GEDCOMs, and it allows you to select how much of the 2nd GEDCOM to read in.... read more
GDBI started off 3 years ago as the BK editor. On Dec 9, 2001, I checked in the first version of BKEdit.java:
It started as an add-on to jLifelines, but then I ported it to GenJ, and then John Finlay helped port it to PGV. We then moved the code out of jLifelines to GDBI, a new project focussed on using a common GEDCOM API for multiple databases and editors.... read more
GDBI is now integrated with Taurus FamilyTree:
FamilyTree gives you an explorer view of people in your database. It is run from the Ancestor button in BKEdit.
This version also allows you to maintain a list of logins to PhpGedView servers, and fixes a bug in Find when you try to link to an existing person.
GDBI now supports multiple languages. Version 7 includes Spanish and a little German, and more languages will be added in future releases.
This release of GDBI replaces the phpGedView SQL interface with the new CGI interface, which is more useful, since not many users use SQL.
Also, the BKEdit Notes panel is partly implemented.
This release of GDBI includes the LifeLines genealogy report language. You can run *.ll files on 3 different databases: GenealogyJ, jLifelines, and phpGedView.