I've tried Treebard many thousands of times, almost every day for over six years, and I liked it better by the year. When I didn't like it, I contacted the staff at Treebard University and guess what? Treebard just kept getting better. But then they blocked my email so I'd stop sending feature requests. For a detailed description of the features I like, see www.Treebard.com .
I was happy to learn that even the GEDCOM features work already in both the .PY and the .EXE version of Treebard, even though the staff at Treebard University have suggested nicely that GEDCOM might consider taking a flying leap at Lake Michigan. I also enjoy reading and rereading Luther's 99 Theses: The GEDCOM Deconstruction. You can quote me: working on GEDCOM import code is like relentless fingernails screeching on a chalkboard. It's like trying to enjoy a romantic picnic in a hurricane. Thank goodness someone has seen fit to not only complain about GEDCOM's shortcomings, but also analyze these shortcomings so the rest of us can understand what the problem is... why GEDCOM needs a replacement right now (actually a long time ago).
Three cheers for UNIGEDS, the replacement for GEDCOM, which is ready to become the back-end for any genieware vendor who still wants to be a genieware vendor 20 years from now.
