Changeset 754 for trunk/FamilyTreePlugin/data/TWiki/FamilyTreePlugin.txt
- Timestamp:
- 11/17/08 00:31:02 (4 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/FamilyTreePlugin/data/TWiki/FamilyTreePlugin.txt
r529 r754 17 17 Union topics similarly have a standard include (!StdUnion) and a form. Union topics are named for the couple they represent, male then female, separated by a capital 'X'. Children of the union are listed in a simple one-column table in the union topic. 18 18 19 The plugin installs a new web, called [[FamilyTreePlugin.WebHome][FamilyTreePlugin]]. This web contains some standard topics, an example family tree (a small fragment of my own family tree), a left bar topic, and two "creator topics", !NewPerson and !NewUnion, that help you in creating person and union records respectively. You should *not* edit directly in this web, as it will be overwritten if you ever upgrade the plugin. Instead you should create your own new web based on the FamilyTreePlugin web (see TWiki.ManagingWebs) and then remove all topics in the new web with 'Currie' in the name.19 The plugin installs a new web, called [[FamilyTreePlugin.WebHome][FamilyTreePlugin]]. This web contains some standard topics, an example family tree (a small fragment of my own family tree), a left bar topic, and two "creator topics", !NewPerson and !NewUnion, that help you in creating person and union records respectively. You should *not* edit directly in this web, as it will be overwritten if you ever upgrade the plugin. Instead you should create your own new web based on the FamilyTreePlugin web (see %SYSTEMWEB%.ManagingWebs) and then remove all topics in the new web with 'Currie' in the name. 20 20 21 21 The schema of the database was inspired by the standard LDS "GED" format, so translation back and forth from this format should be fairly straightforward. It would be great if someone could write some scripts to do this.....!
Note: See TracChangeset
for help on using the changeset viewer.
