GedSite News #006

GedSite Version 1.1.2 Released

This is a free upgrade with one new capability and several minor enhancements. I recommend that all users upgrade to this version.

GedSite now imports Tag Type information from Family Historian GEDCOM files including sentence and role definitions. This means that Family Historian users can build sites using event sentences defined solely in their Family Historian project.

There is one caveat: Family Historian users must install a plug-in and use the plug-in to export a GEDCOM file for use with GedSite. See the details on the Family Historian help page.

Tag Types, known as "Fact Definitions" or "Event Definitions" in some programs, define global sentences. They are global because they affect all the tags of a given type. In contrast, a local sentence affects only the tag where the sentence is defined.

To enable the use of Tag Types loaded from the GEDCOM file, enable the Database.Use Global Sentences property.

See the Change Log for other details.

RUG Presentation

I will be presenting at this month's meeting of The Roots Users Group "RUG" of Arlington, Virginia on Saturday, December 10, 2016, from 9:00 am to 12:00 am. For people who are not in the Washington, DC area, presentations are available online via the "Join.Me" application. Instructions for using Join.Me are on the group's home page.

I'll be doing two sessions with a short break between:

•  9:00 am-10:15 am Introduction to GedSite
• 10:15 am-10:30 am Break
• 10:30 am-11:45 am Advanced Usage of Second Site
• 11:45 am-12:00 pm Questions

All times are US Eastern time, UTC-5.

GedSite Version Numbers

I am actively developing GedSite and there will be frequent releases. I typically recommend that users keep up to date and install each new version when it is released. In rare circumstances, I may recommend that customers who are near a significant deadline for a publishing project should wait until after the deadline to upgrade. For example, if there are major changes to GedSite, a person who is a few days from the date of a family reunion, and is planning to distribute CDs, should probably defer upgrading until after the CDs are produced.

Because there are frequent releases, it may help customers to know how GedSite's version numbers are constructed. GedSite version numbers have three components, major, minor, and build number. Here's how they are used.

Major

The major component represents the primary version of the program and is also present in the program's formal name. So, for "GedSite 1", all releases will have a version number where the major component is 1. Licenses are sold for major versions, and a license is valid for all the releases with the same major version.

Minor

The minor component is updated when there are significant, user-visible changes such as new features.

Build Number

The build number component is updated whenever I create a version of GedSite for either the beta team or all customers. If GedSite is released and only the build number is changed, that version typically will contain only minor enhancements and bug fixes.

If the minor component number is updated (see above), then the build number component is reset to zero. When the build number is zero, it's usually left out of the version number. That's true of the last release, v1.1.

How to Download

Existing customers may download the current version from the Downloads page.

To use the current version, you need a license for GedSite 4.

How to Buy

For purchasing information, see the Purchases page.

Prices and policies mentioned on this page were current when the page was published. Prices and policies are subject to change. See the GedSite home page for current version and price information.

---