User:Gioto/Genealogy/TMG


 * http://en.wikipedia.org/wiki/The_Master_Genealogist

TMG 8
In v7.04.000's release notes Bob Velke mentions "We're working on TMG v8, including a fix to the word processor and HTML output problem under the 64-bit version of Windows Vista"

Easter Egg

 * In various forms many versions of TMG (and also FTST) have had a secret easter egg
 * In version 6 and up you need to click on the "Ink & Feather icon" in help/about  The pictures are of "Vladimir Shevchenko and Vladimir Shershakov. Also Kent Riggens (no picture), Louise Hassel, Lissa Soergel and Bob Velke."

Family Tree SuperTools (FTST)
Family Tree SuperTools is view only version of TMG. Due to the inclusion of GenBridge, FTST can is an add-on for other family tree programs. FTST allow you to share your existing TMG database without exporting to GEDCOM with other researchers.
 * v1.0 introduced 28 Jan 2001


 * Upgrade/Patches
 * v1.1 released 06 Nov 2001
 * v2.0 released 17 Dec 2006 (U.S.A and UK Editions)


 * FTST Mailing List

GenBridge
GenBridge is used by TMG to recognise and import many common genealogy data format files from other programs directly into TMG, this minimises the lose of data, instead of when transferred through GEDCOM. While the GenBridge program will do native imports of datafiles, the GenBridge in TMG will not export back to those formats.

As of TMG 7.04 GenBridge can import from the following:
 * GEDCOM versions
 * GEDCOM v4.0, v5.5 (*.GED)
 * Genealogy Programs
 * Family Gathering (*.PRO)/BACKUP (*.SQZ)
 * Family Origins (*.FOW)/BACKUP (*.ZIP)
 * Family Tree Maker (*.FTW)/BACKUP (*.FBK)
 * Family Tree Maker 2008/2009 (*.FTM)/BACKUP (*.FTMB)
 * Generations (*.UDS)
 * Legacy (*.FDB)/ BACKUP (*.ZIP)
 * Personal Ancestral File v3-5.x (*.PAF)
 * Personal Ancestral File v4-5.x BACKUP (*.ZIP)
 * Roots IV & V (*.PRO)/BACKUP (*.SQZ)
 * Ultimate Family Tree (*.PRO)/BACKUP (*.SQZ)
 * Visual Roots (*.PRO)/BACKUP (*.SQZ)

GenBridge Software Development Kit (SDK)
GenBridge Software Development Kit (SDK)    can be used by programs listed below to recognise and import many common genealogy data format files from other programs directly. (need to find out if they can they export back to the original format?)


 * List of products using GenBridge (SDK):
 * Family Tree SuperTools
 * Ancestry Family Tree (AFT)
 * MudCreek Software Inc's Genealogy Software Utilities
 * GedStar (Palm OS Application)
 * Pocket Genealogist - genealogy program for Windows Mobile and PocketPC
 * Family Tree Maker 2008/2009

''For most researchers, data transfer just isn't a problem - not because their data isn't being corrupted with every transfer but because they don't know it. They are constantly told that GEDCOM "does a good job for basic data" and they believe it, having no sense (or care) for how bad the problem really is.'Bob Velke''

History
Bob Velke wrote TMG

Bobs view on tmg RootsWeb: TMG-L [TMG TMG design vs external utilities:From: Bob Velke Date: Sun, 07 Dec 2003 08:40:07 -0500] John Cardinal has done an excellent job of filling in some of the gaps in >TMG. In that sense I consider him a leader. I see no reason why TMG >can't include the functions that John has put into his utility. It would >improve TMG and further remove the necessity to close TMG to perform those >functions.

Now that I've gotten a little sleep , I can weigh in on this subject....

As you know, TMG tries to accommodate researchers with a wide range of experience. While many novice researchers use TMG, a significant core of our user base is made up of professional researchers, educators, and lecturers, many of whom are attracted to TMG because it emphasizes high standards of scholarship. The latter group often recommends TMG to the former because it helps them to be better researchers and it avoids some of the conceptual pitfalls that are common among some of the most popular programs.

For instance, they are attracted to TMG precisely because data entry isn't centered around a dubious definition of "family," it treats each parent/child relationship as independently worthy of citation, and it encourages researchers to treat data as evidence rather than as "facts" (among many other examples).

For example, you'd be amazed to know how many TMG users initially have a hard time wrapping their heads around the idea that "people" and "names" are different things. Once introduced to it, they have no trouble with the concept and they quickly understand its significance. But while you and I know that tracking names over time, dealing with spelling variations, name changes, etc., are natural and absolutely integral elements of good research, those ideas don't come naturally to many users because they've been _taught_ what is important by programs which use the terms "people" and "names" interchangeably and which deal with name variations as afterthoughts, if at all.

There are lots of other examples but there is no doubt that people who transition from certain other software have much more trouble with TMG than those who use it as their first program and a large part of the so-called "steep learning curve" of TMG is the culture shock of changing the way one thinks about genealogical data. Those who survive the process  are the first to say that they are better researchers as a result.

Those same users are the first to cringe when someone asks a public forum about what software to use and the most common advice is to start with something "easy" (or free) and then graduate to something better over time. While, in many ways, it is _easier_ (for developer and researcher) if a program shields the user from as many nasty realities as possible, those who have been through it know that such programs aren't doing the researcher any favors. That advice to start with something "easy" is typically based on a count of features (i.e., "you don't need all of the bells and whistles" and "learn to walk before you learn to run") while ignoring the fact that a new researcher's choice of software has a significant impact on the way he *thinks* about genealogical data. That translates directly to the way in which he conducts his research and the quality of his data, to say nothing of the complications he can expect if/when he "graduates" his data from one program to another.

All of this has taught us to have a certain sense of stewardship; a sensitivity to the message that TMG sends not only by what it does but by what it doesn't do.

For instance, we get a lot of requests for a feature which will allow users who, having discovered the "correct spelling" of a surname, want to change all of the names in a line at once. Other users want to create a marriage event for every couple who had children together. Still others would like to see TMG's sort dates automatically adjusted so that evidence of events always happened in a specified order. Some people will read these examples and say, "What's wrong with that??" and "Who are you to judge whether I should do that?" and "As long as it is an option, people could choose whether or not to do it." But those are examples of the kind of things that, it is safe to say, TMG will never do because merely _having_ such features would send the wrong message about what experienced researchers consider to be scholarly research. (I think that this is what Teresa meant when she said that some features would make Bob "nervous").

That is NOT to say that individuals couldn't make an argument that one or more of those features is appropriate under certain isolated circumstances. It is about maintaining certain minimum standards, preserving the respect of professional researchers, and not corrupting the thinking of novice users.

Some such issues are black and white. But then there is a long list of similar features that fall somewhere in between: those that would be valuable features for the careful and experienced researcher but would be dangerous, unwise, or encourage sloppy research when in the hands of someone who doesn't understand their effects, doesn't care about scholarship, or simply doesn't know any better.

I'm the first to admit that some features in TMG (e.g., applying the surname of the father to a child, assuming a married name, setting the living flag, etc.) make me uncomfortable because they straddle or cross the line and could encourage sloppy research. In those few cases, there is almost always an option to control it. Maybe they were implemented in a moment of weakness , as a result of a particularly convincing or persistent argument, or practicality just overcame principle. And some of the features that are currently only available in an external utility might work their way into a future version of TMG. I don't pretend that there aren't a lot of grey areas here. But neither do I accept the argument that, since some such dubious features exist, we should dispense with all efforts to encourage standards of scholarship.

So here's my main point: I don't want to prevent people from doing _anything_ that they want to do with their data - but some features are better outside the program than in it. There's even some benefit in putting the user through the process of closing TMG to use external utilities. It distances the features from the design principals of the program and it serves to emphasize to the user that they are performing unusual or especially dangerous functions that require their special attention.

This is especially true of features that are not really designed to facilitate research but to clean up data problems that were introduced by other programs. While very valuable to those who need them, such features are relatively rarely used, involve a high risk of data corruption if used inappropriately, and would add unwarranted complications if included in the main program.

I'm not opposed to supporting those types of features but if we were to do so, it would probably be in an external utility. John Cardinal just beat us to it . That is, John didn't develop his utilities over my stubborn objections. He did it with my full cooperation, support, and encouragement. And since his utilities are free (or "donorware") for TMG users, I see no point in duplicating his work when we have so many other exciting ideas about how to enhance TMG.

John Cardinal's TMG Utilities: http://www.johncardinal.com/tmgutil And yes, Wholly Genes has contributed in John's name to the Jimmy Fund, will continue to do so, and wholeheartedly encourages any user who finds value in his utilities to do the same.

Hope this helps.

Bob Velke Wholly Genes Software -->


 * Bob Velke on GEDCOM 5.3 Draft

Features
Event based ???? ... different to most other genealogy programs in the way you can collect and display information.
 * Information is displayed like a spreadsheet. With no set space for any piece of information, this allows you to record conflicting information you may collect, eg.If a civil birth record states John Doe born:1/1/1900 England. And Church record Birth 30/12/1899 baptism:2/1/1900. you may record and display each birth not beginning restricted to deciding which one is correct. ...expand on this why this matters...


 * 1) Database is evidence oriented:
 * 2) enter all data as is from a source & assign surety levels
 * 3) mark most reliable data for printing
 * 4) color-coded flags, research planning aids


 * Visual Chart Form (VCF) - Charting. (note:VCF uses GenBridge to communicate with TMG


 * Custom Report Writer (CRW) <-- TMG v4.x and earlier only.


 * In TMG v5.x and later report configurations are defined and saved via the Report Definition Screen, or RDS. and use R&R Report Writer


 * Whollygenes Genealogy Software Comparison Chart (with more the 350 categories) (Updated 28 Dec 1998)

Reviews

 * The Master Genealogist Gold 6.12 for Windows Software Review - By Rick Crume (This review originally appeared in the October 2002 Family Tree Magazine.)
 * About.com's page on TMG
 * Modern Software Experience - 2008-01-15 The Master Genealogist Version 7
 * ZDNet: Wholly Genes The Master
 * Cruise Reviews
 * SHOESTRING GENEALOGY: Wholly Genes Cruise 2006 - by Dae Powell
 * Articles
 * Genealogist Gold Edition 4.0 Full Review:From PC Magazine / June 8, 2000, By Sally Wiener Grotta]
 * Distribution of People Report in The Master Genealogist
 * Maintaining Consistency of Place Names in The Master Genealogist
 * Pictures
 * http://ourwebsite.org/photos/genealogy/photogallerygentech.shtml
 * Patent Issues
 * TMG's Commsoft's Patent Issue 1995
 * Interview
 * Ancestry.com - Interview with Bob Velke, Owner, Wholly Genes Software: by – David Birley - Genealogical Computing 7/1/1997 - Archive Summer 1997

TMG NEWS
TMG NEWS was an exclusive newsletter for registered users of The Master Genealogist. Editor: Lissa Soergel
 * Volume 2, Number 2, Summer 1995
 * Volume 2, Number 3
 * Combined:Volume 2, Number 4, and Winter, 1995 / Volume 3, Number 1 and Spring, 1996
 * Volume 3, Number 2, Summer, 1997
 * Vol. 3, No. 3, Winter 1998

Wholly Genes Newsletter
Wholly Genes Newsletter is the current newsletter for users of The Master Genealogist.
 * Wholly Genes Newsletter - from 22 December 2004 to Present.

Technologies Used

 * bennet-tec.com


 * mivamerchant.com


 * Amyuni Technologies Forum Index -> Amyuni PDF Converter (PDF Printer Driver)


 * R&R Report Writer


 * Roots Magic also uses the same "Object Views" tool kit to create their charts as VCF


 * Leadtools developers. current version LT.


 * DynaZip by Innermedia who went out of business in March 2008.  TMG7.04 uses Dzactx.dll version 5.00.03 DynaZIP-32 ZIP ActiveX Control (According to InnerMedia, DynaZip versions prior to and including 5.00.03 are vulnerable. )