https://www.gramps-project.org/wiki/api.php?action=feedcontributions&user=GulliblePangolin&feedformat=atomGramps - User contributions [en]2024-03-28T23:48:00ZUser contributionsMediaWiki 1.31.3https://www.gramps-project.org/wiki/index.php?title=User:GulliblePangolin&diff=81048User:GulliblePangolin2020-10-02T21:27:57Z<p>GulliblePangolin: So long and thanks for all the fish.</p>
<hr />
<div>[[Category:User|G]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Addon:Import_Merge_Tool&diff=81047Addon:Import Merge Tool2020-10-02T21:26:17Z<p>GulliblePangolin: </p>
<hr />
<div>{{Third-party plugin}}<br />
{{man tip|Released for Gramps 5.0.x or greater versions}}<br />
[[File:ImportMerge.png|thumb|right|350px|Import and Merge tool]]<br />
The Import and Merge tool will {{man label|Import and merge a Gramps XML}} family tree derived from your own [[How_to_make_a_backup|Gramps XML family tree]] backup file.<br />
== Purpose of this tool ==<br />
This tool was specifically written to make importing and merging a Gramps [[Genealogy_Glossary#family_tree|Tree]] derived from your own Tree easier. <br />
<br />
Make no mistake, merging is '''''hard'''''! And this tool is not magic, it does not make the process simple but it ''is'' easier than the alternatives.<br />
<br />
{{man note|Important Note|This tool this requires that the Family Tree being merged must be a Gramps Family Tree ''derived from a version'' of the currently loaded Family Tree.}} <br />
<br />
A situation occurs occasionally after giving someone a copy of your tree in our native [[Gramps XML]] format. Then each person makes changes to the copy in their possession using Gramps locally. (You can verify the Trees differ and log those revisions with the [[Database_Differences_Report|Database Differences]] add-on report.)<br />
<br />
Programmers call this a 'fork.' (As in: when travelers come to a 'fork in the road' and each chooses different paths.) But the bottom line is that you now have two tree variants derived from a common Tree and you want share your updated Tree. You can't just give the person a fresh copy of your Tree because then their changes would be overwritten.<br />
<br />
At some point, you may want to merge the forks into a common tree... without losing the useful changes from either tree. That synchronization is what this tool is designed to facilitate. It depends on the two Trees sharing common internal handles (not just the user-editable IDs) to simplify ignoring unchanged records. Then the tool focuses you on just the changes.<br />
<br />
But say the other user doesn't use Gramps, so you exported with [[Gramps_and_GEDCOM|GEDCOM]] (or another format) and got it back? Sorry... this tool won't be any easier than a manual merge after a standard import. You'd still need to hand compare every record.<br />
<br />
The derived trees need not be limited to those edited by someone else. I often take a copy of my tree on my laptop when traveling and sometimes I make updates while on the road. But then I may forget to copy it back to my home desktop computer until after I've made more updates. This tool helps to merge these back together.<br />
{{man warn|1=Warning: Data Corruption Risk |2=Mass changes mean more potential for mangling the data. Back up your current tree BEFORE using this tool to merge.<br />If something goes wrong, you will have a way to go back and start over. See [[How to make a backup|make a Gramps XML backup]].}}<br />
<br />
==Usage==<br />
The tool can be installed like any other Addon; see {{man label|[[Third-party_Addons#Installing_Addons_in_Gramps|Installing Addons in Gramps]]}}<br />
<br />
Once installed, it is run by using the {{man menu|Tools -> Family Tree Processing -> Import and Merge tool...}}.<br />
=== Running the Import Merge tool ===<br />
The tool will start with an 'Undo history warning' that suggest that you back up your work.<br />
<br />
You are then presented with the import file dialog, which shows '.gramps' files from your import location.<br />
<br />
When you have selected a file to import, the main tool window comes up and some progress meters pop up indicating the import and comparison process. When this is complete you end up with a three part window. The bottom part provides control and 'Action' buttons and a hint that changes depending on what you are doing.<br />
<br />
=== Top Pane ===<br />
The top pane is a scrollable and selectable view of individual items that were found to be different in your import. Items that were the same (since they were derived from the common Gramps tree) are not shown.<br />
<br />
[[File:ImportMerge.png|thumb|right|569px|Import and Merge tool]]<br />
The top pane shows a 'Status' which is one of '''Different''', '''Added''', or '''Missing'''. '''Different''' items were found in both the current and imported trees, but had been changed in some way. ''Added'' items are found only in your imported tree. And '''Missing''' items were found in your current tree, but not in the imported tree.<br />
<br />
The top pane also shows the ''Object'' type ('''Person''', '''Family''', '''Media''' etc.), its Gramps ''ID'', an ''Object Name or Description'', and the selected ''Action'' (more later).<br />
<br />
You can search for items by Name by just typing characters to match. The top pane must be active for this to work. For example if you are looking for 'Smith, Magnes' in the 'sample.gramps' tree, you could type 'smi' which would jump the selection to the first of the lines containing these characters, and then use cursor up/down keys to find the 'Smith' you are looking for. Or type 'magn' which is more likely to land on the right place.<br />
<br />
You can search for items by 'ID' field by typing '#' and then the characters to match. For example type '#I0103' to search for the individual with ID I0103.<br />
<br />
You can sort the top pane by ''Status'' (''Object'' will be a sub-sort), ''Object'', ''ID'', ''Object Name/Description'' (will be grouped by ''Object'') and ''Action''. Click on the column header to change the sort.<br />
<br />
=== Lower Pane ===<br />
When an item in the top pane is selected, the lower pane shows the specific differences. If no ''Action'' is made yet, the pane will show the 'Original >>' and 'Imported >>' state for each sub-object and item that has a difference. If an ''Action'' has been selected, the pane also includes a 'Result >>' for each sub-object and item that has a difference.<br />
<br />
Sometimes it may be difficult to determine enough about the difference to figure out what is going on. If so, you can check the {{man label|Show more details}} checkbox to see more about the difference.<br />
<br />
The lower pane tries to present the information as concisely but informatively as possible. Apologies if the information seems a bit hard to interpret at times. One area that might be confusing is when there are differences in 'lists'. Many of Gramps objects have lists of other objects, families have lists of children, persons have lists of events or notes etc. When a list has changes, the left side will have a list position number preceded by '#'. For example:<br />
{|<br />
|Person, Event References #1, Event<br />
| <font face="monospace"> Original >> </font><br />
|your tree Event: [E0012] Death: Smith Gus<br />
|-<br />
|<br />
| <font face="monospace"> Imported >> </font><br />
|your tree Event: [E0011] Birth: Smith Gus<br />
|-<br />
|Person, Event References #2, Event<br />
| <font face="monospace"> Original >> </font><br />
|your tree Event: [E0011] Birth: Smith Gus<br />
|-<br />
|<br />
| <font face="monospace"> Imported >> </font><br />
|your tree Event: [E0012] Death: Smith Gus<br />
|}<br />
In this example list of event references, the imported tree somehow got the Birth and Death events swapped, compared to the original tree.<br />
<br />
==== Control buttons ====<br />
<br />
{{man button|Help}} brings up this wiki.<br />
<br />
{{man button|Edit import}} allows editing of the selected item. Any changes are temporarily saved in your imported data, and will be kept only if that data is merged into your current tree. If your editing creates new items, they will appear in the top pane list when you finish editing. Changes here cause the 'Action' to be cleared, so be sure to choose an Action when finished.<br />
<br />
{{man button|Unmark}} clears any current Action. If an item remains unmarked when you are done, it will be treated as if 'Ignored', that is, there will be no changes to your tree for that item.<br />
<br />
{{man button|Ignore}} sets the action for the item so that there will be no changes to your tree for that item. This is the same as leaving the item unmarked, but makes it clear that you have looked at that item.<br />
<br />
{{man button|Done}} tells the tool that you are finished marking the various actions. The tool will bring up a confirmation dialog, allowing you to save your work, cancel and return to marking, or abandon it.<br />
<br />
The remaining buttons are considered 'Actions' and depend on the Status of the item.<br />
<br />
{{man button|Add}} appears for items with an 'Added' status. When added, the imported data will be added to your current tree.<br />
<br />
{{man button|Delete}} appears for items with a 'Missing' status. When selected, the data in your tree for this item will be deleted.<br />
<br />
{{man button|Replace}} appears for items with a 'Different' status. When replaced, the imported data for the item will completely replace the same data in your current tree.<br />
<br />
{{man button|Merge Original}} appears for items with a 'Different' status. When selected, the imported data for the item will be merged with the original tree. The portions of the data that cannot be merged will remain as it is in your current tree data.<br />
<br />
{{man button|Merge Import}} appears for items with a 'Different' status. When selected, the imported data for the item will be merged with the original tree. The portions of the data that cannot be merged will be replaced by the import data.<br />
<br />
When you select an 'Action' with one of the buttons, a hint will appear that states the action in more detail.<br />
<br />
You can change the 'Action' at any time on any item, it may be instructive to see the results of choosing the various choices in the lower pane.<br />
<br />
In general I recommend that you start marking your items with the 'Different' items first. Within these, doing '''Families''' and '''Persons''' first will usually minimize the amount of work to merge your tree. This tool starts up with the sort set to put these items first, so starting at the top is easy.<br />
<br />
=== Automatic Mark ===<br />
<br />
This tool includes the ability to automatically mark those items that are 'referred to' by the item you are currently marking. For Example, if you {{man button|Add}} a person, the events, notes, media, citations and families that the person refers to will also be added. The same process is applied for each of the various 'Action' buttons.<br />
<br />
The marks that are automatically generated are shown in the top pane action column with a '*' preceding the action.<br />
<br />
Occasionally you may mark items that create a conflict in the automatic marking. For example you {{man button|Add}} a person that refers to a media, and then later {{man button|Ignore}} a person that also refers to the same media. In this case, the media item will be marked with a '?' and the action that tends to conserve more data will be used. This means that Adds have priority over Ignore, Ignore over Delete etc. <br />
<br />
You should review any items marked this way to make sure that you agree with the program.<br />
<br />
Note that families and persons in particular usually have a lot of references to other families or persons. In fact if your imported file contains a whole new branch of your family tree, selecting any one of the people or families in that branch will automatically mark all the new people and families at once. This is usually desirable, but not always.<br />
<br />
==== Automatic mark with Families ====<br />
This tool is not ideal for selecting only parts of a tree for merging, but it can be done. If you wish to include a person, but not his family (spouse and children) then you can uncheck the {{man label|Automark Families}} checkbox. This applies to all persons found via the Automark as well. The effect is that you can get ancestors (if {{man label|Automark Parent Families}} is checked) included but not all the descendants of those ancestors.<br />
<br />
If you wish to get a set of spouses and descendants included when adding a person but not all the ancestors of the spouses, then you can uncheck the {{man label|Automark Parent Families}} checkbox and leave the {{man label|Automark Families}} unchecked.<br />
If you don't want any family or parent families automatically included, leave both {{man label|Automark Parent Families}} and {{man label|Automark Families}} unchecked.<br />
<br />
=== Finishing up ===<br />
When you have marked up as many items as you want and reviewed the automatic marks to make sure they are what you desire, you can press the {{man button|Done}} button.<br />
<br />
The tool will bring up a confirmation dialog, allowing you to save your work, cancel and return to marking, or abandon it. If you abandon, your markings are lost and no changes are made to your current tree.<br />
<br />
If you decide to save your work, the tool will perform a series of checks as it saves your work. These checks make sure that any conflicts that may have been created will not result in errors in your database. For example, if you selected a person to add, but decided to ignore a note attached to that person, the tool will 'clean up' the reference to the note on the person before saving it.<br />
<br />
== FAQ ==<br />
;Why would I want to use the {{man button|Edit import}} button?<br />
: If you had an item with a difference, where both the current tree and the imported tree made changes. Because of some limitations of Gramps and this tool, you cannot choose between current and imported for every detail within an object. For these details, you can only choose to keep your current data with {{man button|Ignore}} or {{man button|Merge Original}}, or use the imported data with {{man button|Replace}} or {{man button|Merge Import}}. In either case some changes will be lost. For example, if you have edited a Person and added a Nickname, and the imported tree had edited the same person to add a LDS Ordinance, you can only keep the information for one side. In this case you might want to edit the imported person to change it to add the Nickname so that data will not be lost.<br />
<br />
;Why does the import file have to be derived from the same original source?<br />
: If it is not, then the matching process will not find any items that are the same or even different. Every item in the import file will end up showing as 'Added', and every item in the current tree will show as 'Missing'. You can use this tool to add in part or all of the imported data, but it is not ideal for this purpose. You would be better importing the data into a new tree, using all the Gramps views and filters to find what you do or don't want, make any deletions or edits and export to a new XML before importing that into your tree the usual way.<br />
<br />
;Why can't you use a GEDCOM file as the import source?<br />
: One of the things that make this tool work is that every 'object' in the Gramps database has a unique ID called a handle (this is different than the ID shown in the GUI for each object). The tool can compare objects with matching handles relatively easily, much more easily than guessing if John Smith in your tree is the one from 1722, 1854, or 2012. <br />
: At this time Gramps GEDCOM import and export has no way to save these handles to make this sort of matching possible. A few of the other family tree tools can import and export the so called '_UID' GEDCOM tag (which is not standardized) which might be usable for this, but most tools will simply discard them or modify them to be unusable. Even if these were available and not lost in translation, Gramps data model does not always match with GEDCOM data model. So a GEDCOM export/import, even without any changes made by the user, would have a lot of differences.<br />
<br />
== Notes ==<br />
If you are not sure exactly what an imported tree contains, you should use Gramps to examine it before using this tool. Import the tree into a new family tree, and look it over with the various charts (I like the relationship chart myself) to see if there are branches that you don't want. It is frequently easier to use Gramps filters or editing tools to remove items than to use the tool to exclude them, although the tool will suffice for simpler cases. Even then you should take notes on the IDs of people or families that you don't want, to make it easier to find them with this tool.<br />
<br />
This is a new tool and fairly complex. Please report any issues or desired enhancements to paulr2787 at gmail.com<br />
<br />
I have included a French translation of the tool, mostly as a test of the internationalization code. Since I don't speak French (USA Texas version of English only), please excuse my French.<br />
<br />
==See also==<br />
* [[Database Differences Report]] - allows a mostly complete comparison between the currently opened database (Family Tree) and a Gramps XML file.<br />
<br />
[[Category:Plugins]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Addon:Database_Differences_Report&diff=81046Addon:Database Differences Report2020-10-02T21:25:16Z<p>GulliblePangolin: /* See also */</p>
<hr />
<div>{{Third-party plugin}}<br />
<br />
[[File:Database-differences-report-example-50.png|thumb|right|450px|Database Differences Report example output]]<br />
<br />
The {{man label|Database Differences Report}} allows a mostly complete comparison between the currently opened database (Family Tree) and a Gramps XML file.<br />
<br />
=== Usage ===<br />
<br />
[[File:Database-differences-report-ReportOptions-tab-defaults-51.png|thumb|right|450px|Database Differences Report - Report Options tab example defaults]]<br />
<br />
Open the family tree you want to compare then<br />
<br />
Select {{man menu|Reports > Text Reports > Database Differences Report...}} from the menu.<br />
<br />
On the ''Report Options'' tab select the ''Family Tree file:'' to be compared against.<br />
<br />
Check or Uncheck the options you want to test for in the report eg: '''All are checked by default'''<br />
* [x] Show items that different<br />
* [x] Show items missing from file<br />
* [x] Show items added in file<br />
<br />
====Limitations====<br />
<br />
The Database Differences Report is focused on the principal elements of the Database.<br />
<br />
There are a number of other types of 'metadata' that are not examined during the Database Differences Report. <br />
<br />
* researcher<br />
* custom types<br />
* gender name maps<br />
* base path for media<br />
* surname mapping for the "Group As" surname feature<br />
* etc.<br />
<br />
Some of these 'metadata' are not 'regular' in the way they are stored, comparing them would be a fair amount of additional code work.<br />
<br />
Also note that some of the 'metadata' would be difficult to compare because they are not stored in the backup XML files, but rather in the Gramps initialization files.<br />
<br />
====Note regarding older backup files====<br />
In the past Gramps allowed data to be input in ways that are no longer allowed. When you import an older backup file, many of these issues are silently corrected for you. For example, Gramps used to allow leading and trailing spaces in name fields. Gramps now removes the leading and trailing white space when the data is entered.<br />
<br />
The Database Differences Report performs it's work by creating a temporary Database and importing the backup file that you specified. A side effect of this is that if your Gramps Database has been around for a long time, it may still contain things that are not currently allowed. But the comparison will be done against the backup file that has all of those issues fixed. Each correction has the potential of showing up as a difference, but on examination they look the same. It is quite hard to see those leading/trailing spaces.<br />
<br />
There are 2 solutions:<br />
* backup your database, create a new empty Database and import backup you just made, then go ahead with the report.<br />
* run the [[Gramps_{{man version}}_Wiki_Manual_-_Tools#Clean_input_data|Clean input data]] tool on your Database, then do the report.<br />
<br />
==See also==<br />
* [[GEPS_009:_Import_Export_Merge#Import_Export_Merge]]<br />
* {{bug|2623}}: Import Export Merge (GEPS 009) comment: [https://gramps-project.org/bugs/view.php?id=2623#c25242 ''...A Database Differences Report has been added to gramps35/trunk (marked as 3.5):..One can now see the raw differences between an exported file and the current DB...'']<br />
* [https://sourceforge.net/p/gramps/mailman/message/30345408/ (Gramps-devel)Towards database syncing], From: Doug Blank - 2013-01-13 17:16:25, ''...allows a mostly complete comparison between the current database and a Gramps XML file...''<br />
* Addon - [[Import Merge Tool|Import and merge a Gramps XML family tree]] derived from your own Gramps XML family tree backup file.<br />
<br />
==Issues==<br />
* help button does not come here.<br />
* See issues and features tagged: [https://gramps-project.org/bugs/tag_view_page.php?tag_id=369 DatabaseDifferencesReport] on the bugtracker.<br />
<br />
<br />
[[Category:Plugins]]<br />
[[Category:Developers/General]]<br />
[[Category:Reports]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=User_talk:GulliblePangolin&diff=81045User talk:GulliblePangolin2020-10-02T21:23:22Z<p>GulliblePangolin: Blanked the page</p>
<hr />
<div></div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=User:GulliblePangolin&diff=81044User:GulliblePangolin2020-10-02T21:22:58Z<p>GulliblePangolin: Blanked the page</p>
<hr />
<div></div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=User_talk:GulliblePangolin&diff=78930User talk:GulliblePangolin2020-06-07T01:47:36Z<p>GulliblePangolin: /* Thank you & for Addon:GenealogyTree Can you check instructions please? */</p>
<hr />
<div>==Add Wikipedia:Citation_templates==<br />
<br />
@Sam888 Would it be possible to install Wikipedia's:[https://en.wikipedia.org/wiki/Wikipedia:Citation_templates Citation_templates] or https://en.wikipedia.org/wiki/Template:Reflist on the Gramps wiki? (We don't need the full template just a minimal version that allows us to do reflist would be good? The instructions are [https://en.wikipedia.org/wiki/Template:Reflist/Transwiki_guide here] I'd do it but it talks about needing extensions on mediawiki enabled. [[User:GulliblePangolin|GulliblePangolin]] ([[User talk:GulliblePangolin|talk]]) 22:00, 24 January 2020 (UTC)<br />
<br />
:: I'll investigate what I need to do, but I believe yes this should be possible. sorry no ETA on when I can do it. [[User:Sam888|Sam888]] ([[User talk:Sam888|talk]]) 00:22, 26 January 2020 (UTC)<br />
::: Thanks :) [[User:GulliblePangolin|GulliblePangolin]] ([[User talk:GulliblePangolin|talk]]) 23:28, 26 January 2020 (UTC)<br />
<br />
==Inconsistent Terminology ==<br />
Is there a reason you want to add an interface term '[https://en.wikipedia.org/wiki/Disclosure_widget disclosure]' which is from another GUI system to Gramps vocabulary? The developers have directed us to use the GTK interface widgets nomenclature where possible.<br />
<br />
Google says the use in the [[Gramps_5.1_Wiki_Manual_-_Categories#Sources_Category|Sources section]] would be the ONLY incidence of 'disclosure' in the Gramps wiki.<br />
<br />
In the [[Gramps_5.1_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|visual Guide to the interface]], the term 'expander' is used. This matches the GTK names. Variations of expand & collapse are use to describe its use and the mirror action.<br />
<br />
And why do you want to change to rollover tooltip backdrop color to neon green? The black background with reversed text matches the rollover color scheme in the default GTK GUI and with the default '[[Addon:Themes|Adwaita]]' theme with the Themes addon.<br />
<br />
-brian<br />
[[User:Bamaustin|Bamaustin]] ([[User talk:Bamaustin|talk]]) 07:20, 29 May 2020 (UTC)<br />
::I gave my reason and black is not suitable it really does not convey it is a tooltip, yellow or green or another non black choice would be good that is why the typographical conventions page is for to provide a legend to what it means, I'm not going to get into [https://en.wikipedia.org/wiki/Wikipedia:Edit_warring edit warring] with you, but the example screenshot shown on the page you linked to on wikipedia is for the same GTK gui toolkit used by Gramps ??? so do what you want!! If this project wants helps why are you actively trying to discourage people, looking at your history you have issue(s) with others also!! I'll take a break for now as I'm upset at your inconsistently even in your reply to this! [[User:GulliblePangolin|GulliblePangolin]] ([[User talk:GulliblePangolin|talk]]) 01:46, 7 June 2020 (UTC)</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=User_talk:GulliblePangolin&diff=78929User talk:GulliblePangolin2020-06-07T01:46:58Z<p>GulliblePangolin: /* Inconsistent Terminology */ do what you want.</p>
<hr />
<div>==Add Wikipedia:Citation_templates==<br />
<br />
@Sam888 Would it be possible to install Wikipedia's:[https://en.wikipedia.org/wiki/Wikipedia:Citation_templates Citation_templates] or https://en.wikipedia.org/wiki/Template:Reflist on the Gramps wiki? (We don't need the full template just a minimal version that allows us to do reflist would be good? The instructions are [https://en.wikipedia.org/wiki/Template:Reflist/Transwiki_guide here] I'd do it but it talks about needing extensions on mediawiki enabled. [[User:GulliblePangolin|GulliblePangolin]] ([[User talk:GulliblePangolin|talk]]) 22:00, 24 January 2020 (UTC)<br />
<br />
:: I'll investigate what I need to do, but I believe yes this should be possible. sorry no ETA on when I can do it. [[User:Sam888|Sam888]] ([[User talk:Sam888|talk]]) 00:22, 26 January 2020 (UTC)<br />
::: Thanks :) [[User:GulliblePangolin|GulliblePangolin]] ([[User talk:GulliblePangolin|talk]]) 23:28, 26 January 2020 (UTC)<br />
<br />
==Thank you & for Addon:GenealogyTree Can you check instructions please?==<br />
Thanks for removing the duplicate word GulliblePangolin :) If you are on ms-windows can you test the [https://gramps-project.org/wiki/index.php/Addon:GenealogyTree#Microsoft_Windows instructions] are clear for you please? [[User:Gioto|Gioto]] ([[User talk:Gioto|talk]]) 04:45, 15 May 2020 (UTC)<br />
:: All good. Checked and followed instructions and they very clear, only difference was when starting the Miktex console a popup appears asking to update I was unsure but ended up saying yes and all went well. Thanks for improving alot of the support pages. [[User:GulliblePangolin|GulliblePangolin]] ([[User talk:GulliblePangolin|talk]]) 13:48, 15 May 2020 (UTC)<br />
:::By the way thanks for pointing me to these great looking reports, I had seen them in the menu but had not made the effort to make them work. thanks [[User:GulliblePangolin|GulliblePangolin]] ([[User talk:GulliblePangolin|talk]]) 13:50, 15 May 2020 (UTC)<br />
==Inconsistent Terminology ==<br />
Is there a reason you want to add an interface term '[https://en.wikipedia.org/wiki/Disclosure_widget disclosure]' which is from another GUI system to Gramps vocabulary? The developers have directed us to use the GTK interface widgets nomenclature where possible.<br />
<br />
Google says the use in the [[Gramps_5.1_Wiki_Manual_-_Categories#Sources_Category|Sources section]] would be the ONLY incidence of 'disclosure' in the Gramps wiki.<br />
<br />
In the [[Gramps_5.1_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|visual Guide to the interface]], the term 'expander' is used. This matches the GTK names. Variations of expand & collapse are use to describe its use and the mirror action.<br />
<br />
And why do you want to change to rollover tooltip backdrop color to neon green? The black background with reversed text matches the rollover color scheme in the default GTK GUI and with the default '[[Addon:Themes|Adwaita]]' theme with the Themes addon.<br />
<br />
-brian<br />
[[User:Bamaustin|Bamaustin]] ([[User talk:Bamaustin|talk]]) 07:20, 29 May 2020 (UTC)<br />
::I gave my reason and black is not suitable it really does not convey it is a tooltip, yellow or green or another non black choice would be good that is why the typographical conventions page is for to provide a legend to what it means, I'm not going to get into [https://en.wikipedia.org/wiki/Wikipedia:Edit_warring edit warring] with you, but the example screenshot shown on the page you linked to on wikipedia is for the same GTK gui toolkit used by Gramps ??? so do what you want!! If this project wants helps why are you actively trying to discourage people, looking at your history you have issue(s) with others also!! I'll take a break for now as I'm upset at your inconsistently even in your reply to this! [[User:GulliblePangolin|GulliblePangolin]] ([[User talk:GulliblePangolin|talk]]) 01:46, 7 June 2020 (UTC)</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_Preface&diff=78729Gramps 5.1 Wiki Manual - Preface2020-05-29T06:02:49Z<p>GulliblePangolin: /* Typographical conventions in the Gramps Wiki Manual */</p>
<hr />
<div>{{man index|Gramps 5.1 Wiki Manual|Gramps 5.1 Wiki Manual - What's new?|5.1}}<br />
{{languages|Gramps_5.1_Wiki_Manual_-_Preface}}<br />
<br />
Gramps is a software package designed for genealogical research. Although similar to other genealogical programs, Gramps offers some unique and features which we'll discuss below.<br />
<br />
Gramps is an Open Source software package, which means you are free to make copies and distribute it to anyone you like. It's developed and maintained by a worldwide team of volunteers whose goal is to make Gramps powerful, yet easy to use.<br />
__FORCETOC__<br />
== Why use Gramps? ==<br />
<br />
Most genealogy programs allow you to enter information about your ancestors and descendants. Typically, they can display family relationships through charts, graphs, or reports. Some allow you to include pictures or other media. Most let you include information about people even if those people are not related to the primary family you happen to be researching. And they may include features that let you exchange data with other programs and print different types of reports.<br />
<br />
Gramps has all these capabilities and more. Notably, it allows you to integrate bits and pieces of data as they arise from your research and to put them in one place -- your computer. You can then use your computer to manipulate, correlate, and analyze your data, rather than messing with reams of paper.<br />
<span id="Typographical conventions"><br />
== Typographical conventions in the Gramps Wiki Manual ==<br />
</span><br />
<onlyinclude>In this book, some words are marked with special typography: <br />
*Applications<br />
<br />
*<pre>Commands you type at the command line</pre><br />
<br />
*''Filenames'' or <code>Filenames</code><br />
<br />
*<tt>''Replaceable text''</tt><br />
<br />
*{{man label|Labels}} for buttons and other portions of the graphical interface<br />
<br />
*{{man rollover|hint text}} for roll-over hints (AKA Tooltips) that identify elements of the graphical interface<br />
<br />
*Menu selections look like this: {{Man menu|Menu -> Submenu -> Menu Item}}<br />
<br />
*{{man button|Buttons}} you can click<br />
<br />
*[https://en.wikipedia.org/wiki/Disclosure_widget disclosure triangle] node {{man button|&#x25B6;}}expand or {{man button|&#x25BC;}}collapse disclosure triangular widget. All the nodes of the tree view mode can be simultaneously collapsed or expanded from the pop-up menu shown by right-clicking.<br />
<br />
*{{Man key press|CTRL|D}} [[Gramps_5.1_Wiki_Manual_-_Keybindings|Key combinations]] you can press on your Keyboard.<br />
<br />
*<tt>Anything you type in</tt><br />
<br />
*{{checkbox|1|Checked}} - Checkbox that is selected<br />
*{{checkbox|0|Unchecked}} - Checkbox that is unselected<br />
<br />
The manual also provides assorted bits of additional information in tips and notes as follows:<br />
<br />
{{man tip| 1=Example Tip |2=Tips and bits of extra information will look like this.}}<br />
<br />
{{man note| Example Note |Notes will look like this.}}<br />
<br />
Finally, there are [[Gramps_5.1_Wiki_Manual_-_Error_and_Warning_Reference|warnings]], notifying you where you should be careful:<br />
<br />
{{man warn| Example Warning |This is what a warning looks like. If there's a chance you'll run into trouble, you will be warned beforehand.}}</onlyinclude><br />
{{-}}<br />
{{man index|Gramps 5.1 Wiki Manual|Gramps 5.1 Wiki Manual - What's new?|5.1}}<br />
{{languages|Gramps_5.1_Wiki_Manual_-_Preface}}<br />
{{grampsmanualcopyright}}<br />
<br />
[[Category:Documentation]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Template:Man_tooltip&diff=78728Template:Man tooltip2020-05-29T06:02:03Z<p>GulliblePangolin: Gramps tooltips are light Green on my main system and light yellow on my laptop, so depends on theme etc... either way using black for the user manual is a terrible because it draws your eye too much!</p>
<hr />
<div><strong><kbd {{#if:{{{class|}}}|class="{{{class}}}"}} {{#if:{{{id|}}}|id="{{{id}}}"}} style="background:#7FFF00; color:#000000; font-family:Sans-Serif; {{#if:{{{spacing|}}}| padding-left:0.4em; padding-right:0.4em;| letter-spacing:0.1em; padding-left:0.5em; padding-right:0.4em;}}{{#if:{{{style|}}}|{{{style}}}}}" {{#if:{{{lang|}}}|lang="{{{lang}}}" xml:lang="{{{lang}}}"}} {{#if:{{{title|}}}|title="{{{title}}}"}}>{{{1}}}</kbd></strong><noinclude><br>[[Gramps_{{man version}}_Wiki_Manual_-_Preface|Typographical convention]] used in the Gramps User manual<br><br>To indicate roll-over hints (AKA: [https://en.wikipedia.org/wiki/Tooltip Tootips])on buttons and other portions of the graphical interface<br><br>Copy of [https://wikipedia.org/wiki/Template:Kbd Template:Kbd] From Wikipedia, the free encyclopedia.<br />
[[Category:Templates]]</noinclude></div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Template:Man_tooltip&diff=78727Template:Man tooltip2020-05-29T05:59:22Z<p>GulliblePangolin: </p>
<hr />
<div><strong><kbd {{#if:{{{class|}}}|class="{{{class}}}"}} {{#if:{{{id|}}}|id="{{{id}}}"}} style="background:#7FFF00; color:#000000; font-family:Sans-Serif; {{#if:{{{spacing|}}}| padding-left:0.4em; padding-right:0.4em;| letter-spacing:0.1em; padding-left:0.5em; padding-right:0.4em;}}{{#if:{{{style|}}}|{{{style}}}}}" {{#if:{{{lang|}}}|lang="{{{lang}}}" xml:lang="{{{lang}}}"}} {{#if:{{{title|}}}|title="{{{title}}}"}}>{{{1}}}</kbd></strong><noinclude><br>[[Gramps_{{man version}}_Wiki_Manual_-_Preface|Typographical convention]] used in the Gramps User manual<br>To indicate roll-over hints (AKA: [https://en.wikipedia.org/wiki/Tooltip Tootips])on buttons and other portions of the graphical interface<br><br>Copy of [https://wikipedia.org/wiki/Template:Kbd Template:Kbd] From Wikipedia, the free encyclopedia.<br />
[[Category:Templates]]</noinclude></div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Template:Man_tooltip&diff=78726Template:Man tooltip2020-05-29T05:58:07Z<p>GulliblePangolin: </p>
<hr />
<div><strong><kbd {{#if:{{{class|}}}|class="{{{class}}}"}} {{#if:{{{id|}}}|id="{{{id}}}"}} style="background:#7FFF00; color:#000000; font-family:Sans-Serif; {{#if:{{{spacing|}}}| padding-left:0.4em; padding-right:0.4em;| letter-spacing:0.1em; padding-left:0.5em; padding-right:0.4em;}}{{#if:{{{style|}}}|{{{style}}}}}" {{#if:{{{lang|}}}|lang="{{{lang}}}" xml:lang="{{{lang}}}"}} {{#if:{{{title|}}}|title="{{{title}}}"}}>{{{1}}}</kbd></strong><noinclude><br>[[Gramps_{{man version}}_Wiki_Manual_-_Preface|Typographical convention]] used in the Gramps User manual<br>To indicate roll-over hints (AKA: [https://en.wikipedia.org/wiki/Tooltip Tootips])on buttons and other portions of the graphical interface<br><br>Copy of [https://wikipedia.org/wiki/Template:Kbd Template:Kbd] From Wikipedia, the free encyclopedia; trying to use a dark color close to Gramps web site.<br />
[[Category:Templates]]</noinclude></div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Template:Man_tooltip&diff=78725Template:Man tooltip2020-05-29T05:57:54Z<p>GulliblePangolin: </p>
<hr />
<div><strong><kbd {{#if:{{{class|}}}|class="{{{class}}}"}} {{#if:{{{id|}}}|id="{{{id}}}"}} style="background:#7FFF00; color:#000000; font-family:Sans-Serif; {{#if:{{{spacing|}}}| padding-left:0.4em; padding-right:0.4em;| letter-spacing:0.1em; padding-left:0.5em; padding-right:0.4em;}}{{#if:{{{style|}}}|{{{style}}}}}" {{#if:{{{lang|}}}|lang="{{{lang}}}" xml:lang="{{{lang}}}"}} {{#if:{{{title|}}}|title="{{{title}}}"}}>{{{1}}}</kbd></strong><noinclude><br>[[Gramps_{{man version}}_Wiki_Manual_-_Preface|Typographical convention]] used in the Gramps User manual<br>To indicate roll-over hints (AKAL [https://en.wikipedia.org/wiki/Tooltip Tootips])on buttons and other portions of the graphical interface<br><br>Copy of [https://wikipedia.org/wiki/Template:Kbd Template:Kbd] From Wikipedia, the free encyclopedia; trying to use a dark color close to Gramps web site.<br />
[[Category:Templates]]</noinclude></div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Template:Man_tooltip&diff=78724Template:Man tooltip2020-05-29T05:57:45Z<p>GulliblePangolin: </p>
<hr />
<div><strong><kbd {{#if:{{{class|}}}|class="{{{class}}}"}} {{#if:{{{id|}}}|id="{{{id}}}"}} style="background:#7FFF00; color:#000000; font-family:Sans-Serif; {{#if:{{{spacing|}}}| padding-left:0.4em; padding-right:0.4em;| letter-spacing:0.1em; padding-left:0.5em; padding-right:0.4em;}}{{#if:{{{style|}}}|{{{style}}}}}" {{#if:{{{lang|}}}|lang="{{{lang}}}" xml:lang="{{{lang}}}"}} {{#if:{{{title|}}}|title="{{{title}}}"}}>{{{1}}}</kbd></strong><noinclude><br>[[Gramps_{{man version}}_Wiki_Manual_-_Preface|Typographical convention]] used in the Gramps User manual<br>To indicate roll-over hints (AKAL [https://en.wikipedia.org/wiki/Tooltip Tootips])on buttons and other portions of the graphical interface<br><br>Copy of [https://wikipedia.org/wiki/Template:Kbd Template:Kbd] From Wikipedia, the free encyclopedia; trying to use a dark color close to gramps web site.<br />
[[Category:Templates]]</noinclude></div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Template:Man_tooltip&diff=78723Template:Man tooltip2020-05-29T05:55:58Z<p>GulliblePangolin: </p>
<hr />
<div><strong><kbd {{#if:{{{class|}}}|class="{{{class}}}"}} {{#if:{{{id|}}}|id="{{{id}}}"}} style="background:#7FFF00; color:#000000; font-family:Sans-Serif; {{#if:{{{spacing|}}}| padding-left:0.4em; padding-right:0.4em;| letter-spacing:0.1em; padding-left:0.5em; padding-right:0.4em;}}{{#if:{{{style|}}}|{{{style}}}}}" {{#if:{{{lang|}}}|lang="{{{lang}}}" xml:lang="{{{lang}}}"}} {{#if:{{{title|}}}|title="{{{title}}}"}}>{{{1}}}</kbd></strong><noinclude><br>[[Gramps_{{man version}}_Wiki_Manual_-_Preface|Typographical convention]] used in the Gramps User manual<br>For indicating roll-over hints on buttons and other portions of the graphical interface<br><br>Copy of [https://wikipedia.org/wiki/Template:Kbd Template:Kbd] From Wikipedia, the free encyclopedia; trying to use a dark color close to gramps web site.<br />
[[Category:Templates]]</noinclude></div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_Preface&diff=78722Gramps 5.1 Wiki Manual - Preface2020-05-29T05:49:43Z<p>GulliblePangolin: /* Typographical conventions in the Gramps Wiki Manual */</p>
<hr />
<div>{{man index|Gramps 5.1 Wiki Manual|Gramps 5.1 Wiki Manual - What's new?|5.1}}<br />
{{languages|Gramps_5.1_Wiki_Manual_-_Preface}}<br />
<br />
Gramps is a software package designed for genealogical research. Although similar to other genealogical programs, Gramps offers some unique and features which we'll discuss below.<br />
<br />
Gramps is an Open Source software package, which means you are free to make copies and distribute it to anyone you like. It's developed and maintained by a worldwide team of volunteers whose goal is to make Gramps powerful, yet easy to use.<br />
__FORCETOC__<br />
== Why use Gramps? ==<br />
<br />
Most genealogy programs allow you to enter information about your ancestors and descendants. Typically, they can display family relationships through charts, graphs, or reports. Some allow you to include pictures or other media. Most let you include information about people even if those people are not related to the primary family you happen to be researching. And they may include features that let you exchange data with other programs and print different types of reports.<br />
<br />
Gramps has all these capabilities and more. Notably, it allows you to integrate bits and pieces of data as they arise from your research and to put them in one place -- your computer. You can then use your computer to manipulate, correlate, and analyze your data, rather than messing with reams of paper.<br />
<span id="Typographical conventions"><br />
== Typographical conventions in the Gramps Wiki Manual ==<br />
</span><br />
<onlyinclude>In this book, some words are marked with special typography: <br />
*Applications<br />
<br />
*<pre>Commands you type at the command line</pre><br />
<br />
*''Filenames'' or <code>Filenames</code><br />
<br />
*<tt>''Replaceable text''</tt><br />
<br />
*{{man label|Labels}} for buttons and other portions of the graphical interface<br />
<br />
*{{man rollover|hint text}} for roll-over hints that identify elements of the graphical interface<br />
<br />
*Menu selections look like this: {{Man menu|Menu -> Submenu -> Menu Item}}<br />
<br />
*{{man button|Buttons}} you can click<br />
<br />
*[https://en.wikipedia.org/wiki/Disclosure_widget disclosure triangle] node {{man button|&#x25B6;}}expand or {{man button|&#x25BC;}}collapse disclosure triangular widget. All the nodes of the tree view mode can be simultaneously collapsed or expanded from the pop-up menu shown by right-clicking.<br />
<br />
*{{Man key press|CTRL|D}} [[Gramps_5.1_Wiki_Manual_-_Keybindings|Key combinations]] you can press on your Keyboard.<br />
<br />
*<tt>Anything you type in</tt><br />
<br />
*{{checkbox|1|Checked}} - Checkbox that is selected<br />
*{{checkbox|0|Unchecked}} - Checkbox that is unselected<br />
<br />
The manual also provides assorted bits of additional information in tips and notes as follows:<br />
<br />
{{man tip| 1=Example Tip |2=Tips and bits of extra information will look like this.}}<br />
<br />
{{man note| Example Note |Notes will look like this.}}<br />
<br />
Finally, there are [[Gramps_5.1_Wiki_Manual_-_Error_and_Warning_Reference|warnings]], notifying you where you should be careful:<br />
<br />
{{man warn| Example Warning |This is what a warning looks like. If there's a chance you'll run into trouble, you will be warned beforehand.}}</onlyinclude><br />
{{-}}<br />
{{man index|Gramps 5.1 Wiki Manual|Gramps 5.1 Wiki Manual - What's new?|5.1}}<br />
{{languages|Gramps_5.1_Wiki_Manual_-_Preface}}<br />
{{grampsmanualcopyright}}<br />
<br />
[[Category:Documentation]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_Categories&diff=78721Gramps 5.1 Wiki Manual - Categories2020-05-29T05:47:13Z<p>GulliblePangolin: /* Citation Tree View */ https://en.wikipedia.org/wiki/Disclosure_widget</p>
<hr />
<div>{{man index|Gramps 5.1 Wiki Manual - Main Window|Gramps 5.1 Wiki Manual - Manage Family Trees|5.1}}<br />
{{languages|Gramps 5.1 Wiki Manual - Categories}}<br />
{{#vardefine:chapter|4}}<br />
{{#vardefine:figure|0}}<br />
[https://en.wikipedia.org/wiki/Genealogy#Types_of_information Genealogical information] is very broad and can be extremely detailed. Displaying it poses a challenge that Gramps takes on by dividing and organizing the information into a series of Categories, each with their own Views. Each View displays a portion of the total information, selected according to a particular category. This will become clearer as we explore the different Categories.<br />
<br />
== Categories of the Navigator ==<br />
The different Categories of the Navigator: The navigator is located at the left of the window and allows selection of the different categories.<br />
<br />
*{{icon|gram}} '''Dashboard''': Displays different general purpose Gramplets, small widgets that can help in your genealogical research.<br />
<br />
*{{icon|peop}} '''People''': Displays the people in the family tree without their connections. This Category contains the PeopleListView and the PeopleTreeView.<br />
<br />
*{{icon|rela}} '''Relationships''': Shows the relationships between the Active Person and other people in a textual way. This includes parents, spouses, and children.<br />
<br />
*{{icon|fami}} '''Families''': Shows the families in the family tree.<br />
<br />
*{{icon|ance}} '''Charts''': Displays graphical trees for the selected person.<br />
<br />
*{{icon|even}} '''Events''': Displays the events in the family tree.<br />
<br />
*{{icon|plac}} '''Places''': Displays the places in the family tree.<br />
<br />
*{{icon|geog}} '''Geography''': Displays data of your family tree on a map.<br />
<br />
*{{icon|sour34}} '''[[Gramps_5.1_Wiki_Manual_-_Categories#Sources_Category|Sources]]''': Displays the sources in the family tree.<br />
<br />
*{{icon|cite}} '''Citations''': Displays the citations in the family tree.<br />
<br />
*{{icon|repo}} '''Repositories''': Displays the repositories in the family tree.<br />
<br />
*{{icon|medi}} '''Media''': Displays the media objects in the family tree.<br />
<br />
*{{icon|note}} '''Notes''': Displays the notes in the family tree.<br />
<br />
The categories can contain several ways of presenting the data. Each specific way is called a View. <br />
For example:<br />
* Categories<br />
** View (1)<br />
** View (2)<br />
<br />
For each category you have a number of ways to switch between Views:<br />
# by selecting the relevant icon from the toolbar<br />
# from the menu {{man menu|View > ... }} <br />
# Via [[Gramps_5.1_Wiki_Manual_-_Keybindings#List_Views|keyboard shortcuts]] See the shortcuts for ''Changes the view to view number 0/1/2/../9 in this view category''<br />
<br />
The following sections provide a brief description of each category and the view's within.<br />
<br />
== Dashboard Category ==<br />
<br />
[[File:DashboardCategoryView-example-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Dashboard Category view]]<br />
<br />
This contains the {{icon|gram}} '''Dashboard''', which shows a number of widgets, called [[Gramps_5.1_Wiki_Manual_-_Gramplets#What_is_a_Gramplet|Gramplets]], that can help you in your research. Two Gramplets are shown by default on start-up (the [[Gramps_5.1_Wiki_Manual_-_Gramplets#Welcome|Welcome]] and [[Gramps_5.1_Wiki_Manual_-_Gramplets#Top_Surnames|Top Surname]] Gramplets). When you have an open Family Tree you can by using the context menu (right-clicking) on an empty area of the Dashboard View, to see a popup menu to "{{man menu|Add a gramplet}}" that shows a list of the possible Gramplets you may add and use.<br />
<br />
*{{man label|Age Stats}} Gramplet - list age span statistics in a number of graphs<br />
*{{man label|Age on Date}} Gramplet - list the people alive and their ages on a particular date<br />
*{{man label|Calendar}} Gramplet - see people's events on a particular date, or in a month in the past<br />
*{{man label|FAQ}}<br />
*{{man label|Given Name Cloud}} Gramplet - most popular given names<br />
*{{man label|Quick View}} - run a Quick View on the current person<br />
*{{man label|Records Gramplet}} - see world's records of your data<br />
*{{man label|Session Log}} Gramplet - keep track of what you have done, and what records you have visited<br />
*{{man label|SoundEx Generator}}<br />
*{{man label|Statistics}} Gramplet - see stats on the database<br />
*{{man label|Surname Cloud}} Gramplet - most popular surnames as a "text cloud"<br />
*{{man label|To Do}} Gramplet - a notepad to keep tabs on your research<br />
*{{man label|Top Surnames}} Gramplet - top 10 most popular surnames<br />
*{{man label|Welcome}} Gramplet - a Gramps welcome message<br />
*{{man label|What's Next}} Gramplet - what needs to be done next<br />
<br />
In addition, there are a number of Third party Gramplets that you can easily install and use. These include:<br />
<br />
*Headline News Gramplet - current, breaking news from Gramps<br />
*Data Entry Gramplet - edit active person's name, birth date and place, death date and place, and add people<br />
*Python Gramplet - a Python shell<br />
*FAQ Gramplet - frequently asked questions<br />
*Note Gramplet - see and edit active person's primary Person Note<br />
<br />
and many others. See [[Third-party Addons]] for more details.<br />
<br />
For more detailed information on using the installed Gramplets, see [[Gramps 5.1 Wiki Manual - Gramplets|Gramplets]].<br />
<br />
== People Category ==<br />
<br />
In the {{man label|People Category}} the {{man label|People List view}} or {{man label|Grouped People}}(default) views display a list of all people in the database. From this view, you may add, edit, remove, or merge people. Each view (List or Grouped) display several columns of information about each person.<br />
<br />
By default, the view displays the <code>Name</code>, <code>ID</code>, <code>Gender</code>, <code>Birth Date</code> and <code>Death Date</code> of the Person. Additional columns for <code>Birth Place</code>, <code>Death Place</code>, <code>Spouse</code>, <code>Number of Parents</code>, <code>Number of Marriages</code>, <code>Number of Children</code>, <code>Number of To Do Notes</code>, <code>Private</code>, <code>Tags</code> and <code>Last Changed</code> may be displayed.<br />
<br />
The {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Column_Editor|Column Editor]]}} dialog can be used to show, hide and change the order of the displayed columns. This editor can be accessed by selecting {{man menu|View &#x27a1; Configure...}} from the menu or by clicking the [[File:Gramps-config.png|34px]]{{man button|Configure View...}} button on the toolbar.<br />
<br />
See also<br />
* [[Gramps_5.1_Wiki_Manual_-_Navigation#Using_the_People_Category|Using the People Category]]<br />
* [[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_people|Editing information about people]]<br />
<br />
{{man note|For Information displayed in the columns|Some of the column selection types require that the event being shown has the ''Role'' type of ''Primary'' eg Birth and Death Dates. This is set via the [[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor dialog]]'s ''General'' tab.}}<br />
{{man note|Column counts for <code>Number of xxxxxx</code>|For <code>Number of Marriages</code> only relationships of type ''Married'' are counted. For <code>Number of Children</code> only children with a ''Birth'' relationship are counted. However, for <code>Number of Parents</code> any parent relationship (even those with a relationship of 'None') will be included in the parent count.}}<br />
{{-}}<br />
===Tree View - Grouped People===<br />
<br />
[[File:People-tree-view-grouped-people-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} People Category - Tree View - Grouped People]]<br />
<br />
People are grouped according to their family names. To the left of each family name is typically either an arrow or some other type of indicator (eg: ''+''). Clicking it once will reveal the entire list of people sharing that name. Clicking the indicator again will "roll up" the list and show only the family name.<br />
<br />
{{man note|Configure the view limitation|For the Group view the first column "<code>Name</code>" cannot be changed as the view is based on showing grouped surnames.}}<br />
<br />
{{-}}<br />
<br />
===Tree View - People List View===<br />
<br />
[[File:People-tree-view-people-list-view-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} People Category - Tree View - People List View]]<br />
<br />
List of all the people in the database, sorted by first column which by default is the <code>Name</code> column.<br />
<br />
{{-}}<br />
<br />
===People Category Bottombar tabs===<br />
Both Tree Views (Grouped People/People List View) share the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tabs.<br />
{{-}}<br />
====Details====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Details|Details]] Gramplet<br />
{{-}}<br />
====Gallery====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Gallery|Gallery]] Gramplet<br />
{{-}}<br />
====Events====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Events|Events]] Gramplet<br />
{{-}}<br />
====Children====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Children|Children]] Gramplet<br />
{{-}}<br />
====Citations====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Citations|Citations]] Gramplet<br />
{{-}}<br />
====Notes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Notes|Notes]] Gramplet<br />
{{-}}<br />
====Attributes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Attributes|Attributes]] Gramplet<br />
{{-}}<br />
====References====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#References|References]] Gramplet<br />
{{-}}<br />
===People Category Sidebar tabs===<br />
<br />
Both Tree Views (Grouped People/People List View) share the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tab by default.<br />
{{-}}<br />
====Filter====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
{{-}}<br />
<br />
== Relationships Category ==<br />
<br />
[[File:Relationships-category-view-51.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Relationships Category view]]<br />
<br />
The Relationships Category shows the default {{man label|Relationships Category view}} which displays all the relationships of the Active Person (the selected person). Specifically, it shows the parents, siblings, spouses, and children of that person.<br />
<br />
The Relationships Category is designed to allow for quick navigation. You can quickly change the Active Person simply by clicking the name of any person listed on the page. Each name is actually a [http://en.wikipedia.org/wiki/Hyperlink hypertext link], similar to a web page.<br />
<br />
The name of the Active Person is in '''bold''' style. Other names are shown either with or without '''''bold and italic''''' emphasis depending on whether certain relationships exist for the named person. For a person listed as a parent or spouse of the Active Person, the name is emphasized if that person has a parent family. For a person listed as a sibling or child of the Active Person, the name is emphasized if that person has children.<br />
<br />
Dates are normally in regular style, and in ''italic'' style if the displayed event is a fallback event, i.e., a substitute event for another missing event. That may be christening event for birth event, burial event for death event, etc.<br />
{{-}}<br />
===Relationships Category view===<br />
<br />
For the Relationships Category views via the menu or toolbar you may select:<br />
* {{man menu|Edit>Edit...}} or the {{man button|Edit the active person}} icon - opens the {{man label|Person Edit dialog}}<br />
* {{man menu|Edit>Add New Parents...}} or the {{man button|Add a new set of parents}} icon - to create a new family with the Active Person listed as a child.<br />
* {{man menu|Edit>Add Existing Parents...}} or the {{man button|Add person as child to and existing family}} icon - which opens the [[Gramps_5.1_Wiki_Manual_-_Categories#Select_Family_selector|Select Family selector]] allowing you to choose from a list of existing families, and then add the person as a child to that family.<br />
* {{man menu|Edit>Add Partner...}} or the {{man button|Add a new family with person as parent}} icon - <br />
* {{man menu|Edit>Reorder...}} or the {{man button|Change order of parents families}} icon - to open the [[Gramps_5.1_Wiki_Manual_-_Categories#Reorder_Relationships_dialog|Reorder Relationships dialog]] <br />
<br />
The following sections are available:<br />
{{-}}<br />
====Active Person====<br />
<br />
* At the top of the screen, name, {{man label|ID}}, {{man label|Birth}}, and {{man label|Death}} information, as well as the calculated age of the Active Person is displayed. You may highlight and copy the {{man label|Birth}} and {{man label|Death}} text fields.<br />
<br />
* On the right hand side a photo of the person if available, will be shown. This photo shows the first image available in the {{man label|[[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Gallery|Gallery]]}} tab of this person (if any exist). You can click on the photo to open it in the default picture viewer.<br />
<br />
* Next to the person's name is a symbol indicating gender, and an {{man button|[[Image:Gramps-notes.png|13px]]Edit}} button. Clicking the {{man button|[[Image:Gramps-notes.png|13px]]Edit}} button will allow you to edit all of the person's individual information in the {{man label|[[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Edit_Person_dialog|Edit Person]]}} dialog.<br />
<br />
* See also: [[Gramps_5.1_Wiki_Manual_-_Navigation#Setting_the_Active_Person|Setting the Active Person]]<br />
<br />
====Parents====<br />
<br />
The Parents section, displays the families in which the person is a child. Since it is possible for a person to have multiple sets of parents, it is possible to have several Parents sections.<br />
<br />
You may edit an existing parents by selecting the {{man button|[[Image:Gramps-notes.png|13px]]Edit}} button next to the parents. If you select the {{man button|-}} button next to a set of parents, then the Active Person will be removed as a child from the parents. This button does not delete the parents' relationship.<br />
<br />
See the {{man label|[[Gramps_5.1_Wiki_Manual_-_Categories#Configuration|Configure Relationships]]}} section to configure what details to show or hide etc...<br />
<br />
{{man warn|Warning|If you are not careful, it is possible to create multiple families with the same parents. This is rarely what the user wants to do. If you attempt to add a new family that has the same parents as an existing family, Gramps will issue a warning dialog. If you get this dialog, you should probably Cancel the edit, and then use the {{man button|Select}} button to select the existing family.}}<br />
=====Select Family selector=====<br />
[[File:SelectFamily-SelectorDialog-example-50.png|thumb|right|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Select Family - selector dialog example]]<br />
<br />
The {{man label|Select Family}} selector dialog allows you to link to an already existing Family.<br />
<br />
The following columns are shown: ID(default sort for list), Father, Mother, Last Change.<br />
<br />
You may use the {{man button|Find}} button to filter the list based on one of the options from the drop down list:<br />
* '''ID contains''' (default)<br />
* ''ID does not contain''<br />
* ''Father contains''<br />
* ''Father does not contain''<br />
* ''Mother contains''<br />
* ''Mother does not contain''<br />
* ''Last Change contains''<br />
* ''Last Change does not contain''<br />
<br />
{{stub}}<br />
{{-}}<br />
<br />
=====Siblings=====<br />
<br />
The Sibling section show the active persons brothers and sisters.<br />
<br />
<br />
{{-}}<br />
<br />
====Family====<br />
<br />
Similar to the Parents section is the Family section, which displays families where the Active Person is a parent. Because it is possible to have multiple families, it is possible to have multiple Family sections. Each family section displays the spouse and any children.<br />
<br />
{{man note | Spouse |We use the term spouse for sake of simplicity. However, please note that spouse may in fact be a domestic partner, a partner in a civil union, or various other similar relationships between two people. Spouse relationships are not required to be only between a male and female.}}<br />
<br />
You may add a family by selecting the {{man button|Add Spouse}} button in the toolbar. This will create a new family with the Active Person listed as a father or mother.<br />
<br />
Selecting the {{man button|[[Image:Gramps-notes.png|13px]]Edit}} button next to the spouse will allow you to edit the displayed family. Clicking the {{man button|-}} button will remove the person from the displayed family.<br />
<br />
{{-}}<br />
<br />
{{man warn| Removing a person from a family |Removing a person from a family does not delete the family. The person is removed as the father or mother, and any other relationships in the family continue to exist.}}<br />
<br />
{{man note | Note |We use the terms father and mother for the sake of simplicity. Even if there are no children in a family, the father and mother terminology is still used. In the case of male/male or female/female relationships, the father and mother labels should be considered to be convenience labels.}}<br />
<br />
{{-}}<br />
Select the {{man button|Change order of parents families}} button to display the {{man label|[[Gramps_5.1_Wiki_Manual_-_Categories#Reorder_Relationships_dialog|Reorder Relationships]]}} dialog that will allow you to reorder the families.<br />
<br />
======Reorder Relationships dialog====== <br />
{{man note|This option will only be enabled|if more than one set of parents or more than one set of spouses exists for the Active Person.}}<br />
<br />
[[File:ReorderRelationships-dialog-50.png|right|thumb|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Reorder Relationships - dialog - example]]<br />
<br />
When more than one set of parents or more than one set of spouses exists for the Active Person.<br />
<br />
Select one of the following:<br />
* the menu {{man menu|Edit > Reorder}}<br />
* or the {{man button|Change order of parents and families}} toolbar icon button<br />
* or the {{man button|Reorder Parents}} icon near the {{man label|Parents:}} label<br />
* or the {{man button|Reorder Families}} icon near the {{man label|Family:}} label<br />
to display the {{man label|Reorder Relationships}} dialog that will allow you to reorder:<br />
* the parents order in the top section {{man label|Parent relationships}} using the up/down arrow buttons.<br />
* or families order in the bottom section {{man label|Family relationships}} using the up/down arrow buttons.<br />
{{-}}<br />
<br />
=====Children=====<br />
<br />
The Active persons children.<br />
{{-}}<br />
<br />
====Configuration====<br />
<br />
[[File:ConfigureRelationshipsView-content-tab-50.png|right|thumb|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Configure Relationships Category - Content (tab)]]<br />
<br />
You can control how much information is displayed by using the {{man menu|View -> Configure...}} menu or click on the toolbar {{man button|Configure the active view...}} button.<br />
<br />
The following options are available:<br />
*On the {{man label|Content}} tab<br />
** {{checkbox|1}} {{man label|Show Details}} (checkbox checked by default) show or hide the birth and death information (All except the Active person)<br />
** {{checkbox|1}} {{man label|Show Siblings}} (checkbox checked by default) show or hide siblings.<br />
{{-}}<br />
[[File:ConfigureRelationshipsView-layout-tab-50.png|right|thumb|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Configure Relationships Category - Layout (tab)]]<br />
<br />
*On the {{man label|Layout}} tab<br />
** {{checkbox|1}} {{man label|Use shading}} (checkbox checked by default)<br />
** {{checkbox|1}} {{man label|Display edit buttons}} (checkbox checked by default) - show or hide the {{man button|[[Image:Gramps-notes.png|13px]]Edit}} button shown next to each person.<br />
** {{checkbox|0}} {{man label|View links as website links}} (checkbox unchecked by default)<br />
{{-}}<br />
<br />
===Relationships Category Bottombar tabs===<br />
The {{man label|Relationships Category view}} by default displays no Gramplets in the [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tab. You may add them as required.<br />
{{-}}<br />
===Relationships Category Sidebar tabs===<br />
The {{man label|Relationships Category view}} by default displays no Gramplets in the [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tab. You may add them as required.<br />
{{-}}<br />
<br />
== Families Category ==<br />
<br />
{{man warn| {{man button|Remove}} button |Unlike the Relationships Category, clicking the {{man button|Remove}} button in this view will remove the family from the database. All people will remain, but all relationships between the people in the family will be removed.}}<br />
<br />
[[File:Families-category-list-view-50.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Families Category - (List) View]]<br />
<br />
In the {{man label|Families Category}} the {{man label|Families List view}} displays a list of all families in the database(see Fig. {{#var:chapter}}.{{#var:figure}}). From this view, you may {{man button|[[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Family_Editor_dialog|Add a new Family]]}}, {{man button|[[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Family_Editor_dialog|Edit the selected family]]}}, {{man button|Delete the selected family}}, {{man button|[[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merge_Families|Merge the selected (2) families]]}} from the list, or {{man button|Tag the selected rows}}. The default display lists the <code>ID, Father, Mother, Relationship and Marriage Date</code>. If you configure the active view you can, hide existing columns, show additional columns like <code>Private, Tags, Last Changed</code>, or rearrange the column order. <br />
<br />
If you can also right-click on a family and from the context menu, select "Make Mother Active Person" or "Make Father Active Person"<br />
<br />
See also<br />
* [[Gramps_5.1_Wiki_Manual_-_Navigation#Using_the_Families_Category|Using the Families Category]]<br />
* [[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_relationships|Editing information about relationships]]<br />
<br />
{{man note|Children cannot be displayed on the screen in this list view.|The children can be viewed in the associated ''Children'' tab in the bottombar or sidebar and [[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Children|Family Editor's ''Children'']] tab.}}<br />
{{-}}<br />
===Families Category Bottombar tabs===<br />
The {{man label|Families Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tabs as default.<br />
{{-}}<br />
====Gallery====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Gallery|Gallery]] Gramplet<br />
{{-}}<br />
====Events====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Events|Events]] Gramplet<br />
{{-}}<br />
====Children====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Children|Children]] Gramplet<br />
{{-}}<br />
====Citations====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Citations|Citations]] Gramplet<br />
{{-}}<br />
====Notes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Notes|Notes]] Gramplet<br />
{{-}}<br />
====Attributes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Attributes|Attributes]] Gramplet<br />
{{-}}<br />
====References====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#References|References]] Gramplet<br />
{{-}}<br />
<br />
===Families Category Sidebar tabs===<br />
<br />
The {{man label|Families Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tabs as default.<br />
{{-}}<br />
====Filter====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
{{-}}<br />
<br />
== Charts Category ==<br />
{{stub}}<br />
{{man tip|Want more Chart Views?|Installation of additional downloadable addons contain extra views. See [[Third-party Addons]]}}<br />
<br />
The Charts Category shows several graphical representations of the ancestry or descendants of the active person. <br />
<br />
By default Gramps shows the {{man button|[[Gramps_5.1_Wiki_Manual_-_Categories#Pedigree_View|Pedigree]]}} View. With the {{man button|[[Gramps_5.1_Wiki_Manual_-_Categories#Fan_Chart_View|Fan Chart]]}} View and {{man button|[[Gramps_5.1_Wiki_Manual_-_Categories#Descendant_Fan_View|Descendant Fan]]}} chart View and {{man button|[[Gramps_5.1_Wiki_Manual_-_Categories#2-Way_Fan_View|2-Way Fan]]}} chart view being selectable from the toolbar or menu via {{man menu|View > '''Name of Chart View'''}}<br />
<br />
=== Pedigree View===<br />
<br />
[[File:ChartsCategory-pedigreeview1-horizontal-right-standard-5gen-default-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Pedigree view 1 (Default) Tree direction:horizontal to right]]<br />
<br />
The {{man label|Pedigree}} View shows up to nine generations in the form of a chart, depending on the size of the window you may need to use the scroll bars to see parts of the chart.<br />
<br />
Each person is indicated by a box labeled with his or her name, birth information (indicated by an asterisk * sign), death information (indicated by a plus + sign), a black stripe across the top left corner of the box is shown if the person is deceased (or determined by Gramps to be no longer alive) and optionally the primary image will be displayed if available.<br />
<br />
Two lines branch from each person box. The top line leads to the person's father and the bottom line leads to the mother. Solid lines represent the biological birth type relationship, while dashed lines represent non-birth relationships such as adoption, step-parenthood, guardianship, etc.<br />
<br />
The left arrow {{man button|Jump to child...}} button beside the Active Person is a only selectable if the Active Person has children, clicking this button expands to show a list of the Active Person's children. Selecting one of the children makes that child the Active Person for the chart.<br />
<br />
<!--??-->The appearance of the children's names in the menu differentiates the dead ends of the tree from the continuing branches.<br />
<br />
Children who have children themselves appear in the menu in the boldface and italic type, while children without children (dead ends) appear in a regular font. If the Active Person has only one child, no menu will be displayed (since there is only one choice) and the child will become the Active Person when the arrow button is clicked.<br />
<br />
The right-hand side of the window shows two right arrow buttons. When the top button {{man button|Jump to father}} is clicked, the Father of the Active Person becomes the Active Person. When the bottom button {{man button|Jump to mother}} is clicked, the Mother of the Active Person becomes the Active Person.<br />
<br />
{{-}}<br />
[[File:ChartsCategory-PedigreeView-PersonContextMenu-showing-Children-example-50.png|right|thumb|250px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Person context menu showing Children]]<br />
<br />
Right-clicking on any person's box in the Pedigree View will bring up the Person "context menu".<br />
<br />
Among other useful items, the context menu has sub-menus listing {{man label|Spouses}} , {{man label|Siblings}} , {{man label|Children}} , {{man label|Parents}} and {{man label|Related}} of that person.<br />
<br />
"Greyed-out" sub-menus indicate the absence of the data in the appropriate category. Similar to the children menu above, Childrens' and Parents' menus distinguish continuing lines from dead ends.<br />
<br />
{{-}}<br />
<br />
==== Configure the active view ====<br />
<br />
[[File:ChartsCategory-PedigreeView-ConfigureCharts-dialog-default-50.png|right|thumb|250px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Charts Category - Pedigree View - Configure the active view - dialog - showing Defaults on Layout tab]]<br />
<br />
The {{man label|Layout}} tab has the following option available:<br />
* {{checkbox|1}} {{man label|Show images}} (checked by default)<br />
* {{checkbox|1}} {{man label|Show marriage data}} (checked by default)<br />
* {{checkbox|1}} {{man label|Show unknown people}} (checked by default)<br />
* {{checkbox|0}} {{man label|Show tags}} (unchecked by default)<br />
* {{man label|Tree style:}}<br />
** '''Standard'''(default)<br />
** Compact<br />
** Expanded<br />
* {{man label|Tree direction:}}<br />
** Vertical (↑)<br />
** Vertical (↓)<br />
** '''Horizontal (→)'''(default)<br />
** Horizontal (←)<br />
* {{man label|Tree size:}} slider range 2 to 9. Set to <code>5</code>(by default)<br />
<br />
[[File:ChartsCategory-pedigreeview2-horizontal-left-standard-5gen-50.png|left|thumb|250px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Pedigree view 2 - Tree direction:horizontal to left]]<br />
[[File:ChartsCategory-pedigreeview2-vertical-up-standard-5gen-50.png|right|thumb|250px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Pedigree view 3 - Tree direction:vertical and up]]<br />
[[File:ChartsCategory-pedigreeview2-vertical-down-standard-5gen-50.png|left|thumb|250px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Pedigree view 4 - Tree direction:vertical and down]]<br />
<br />
{{-}}<br />
<br />
=== Fan Chart View ===<br />
<br />
[[File:ChartsCategory-fanchartview-fullcircle-9gen-default-50.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Fan Chart View - full circle]]<br />
<br />
The {{man label|Fan Chart}} view shows the active persons ancestry as a pie chart. Clicking on a name in the chart will double the section of the pie allocated to that person. A second click brings the chart back to the original form. Right click brings up a context menu like in the pedigree view, allowing to navigate to other people. <br />
<br />
This view enables to see large ancestries in a more compact manner, and to see very quickly which parts of an ancestry need further research. <br />
<br />
You can rotate the view by click and drag outside the fan chart. You can move the view by click and drag inside the inner (white) region.<br />
<br />
#The view can be a circle, a halfcircle or a quadrant of a circle. The latter are always attached to the bottom or side of the view<br />
#Children of the center person are shown within the ring at the center<br />
#Drag and drop people to the center to change the active person<br />
#Color options<br />
## Colors of the boxes based on the age of the people<br />
## Colors of the boxes depending on the time period the person lived in<br />
## White, classic, gender based, and user defined colors<br />
# Filtering: use the person filter in the sidebar to quickly obtain insight in the people shown. For example: which people have birth events, who has the attribute ''blue eyes'', ... . Filtered results have bold font, the ones that don’t satisfy the filter are shown transparent<br />
#Show up to 11 generations in the view.<br />
#Print the view from the toolbar. The view as you see it (after rotating, expanding, changing color) can via the print button be printed or saved as svg (to edit further in Inkscape and view in eg Firefox), pdf or ps.<br />
#The font used can be selected and automatically adjust to fit within the boxes. On a darker background, the font is white, and vice versa.<br />
<br />
To understand all, [https://plus.google.com/u/0/115195430424417504730/posts/QrXM4z9JxrG watch the screencast]<br />
<br />
See also: [[Gramps_5.1_Wiki_Manual_-_Gramplets#Fan_Chart|Fan Chart Gramplet]]<br />
{{-}}<br />
==== Configure the active view ====<br />
<br />
[[File:ChartsCategory-FanChartView-ConfigureCharts-dialog-default-50.png|right|thumb|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Charts Category - Fan Chart View - Configure the active view - dialog - showing Defaults Defaults on Layout tab]]<br />
<br />
* {{man label|Max generations:}} ''9'' (default)<br />
* {{man label|Text Font:}} ''Sans'' (default)<br />
* {{man label|Background:}}<br />
** Gender colours<br />
** '''Generation based gradient''' (default)<br />
** Age (0-100) based gradient<br />
** Single main (filter) colour<br />
** Time period based gradient<br />
** White<br />
** Colour scheme classic report<br />
** Colour scheme classic view<br />
* {{man label|Start gradient/Main colour:}} ''#ef2929'' (default)<br />
* {{man label|End gradient/2nd colour:}} ''#3d37e9'' (default)<br />
* {{man label|Fan chart type:}}<br />
** '''Full Circle''' (default)<br />
** Half Circle<br />
** Quadrant<br />
* {{checkbox|1}} {{man label|Show names on two lines}}<br />
* {{checkbox|1}} {{man label|Flip name on the left of the fan}}<br />
* {{checkbox|1}} {{man label|Show children ring}}<br />
* {{checkbox|0}} {{man label|Show gramps id}}<br />
<br />
{{-}}<br />
<br />
=== Descendant Fan View ===<br />
<br />
[[File:ChartsCategory-desendantfan-fullcircle-9gen-default-50.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Descendant Fan Chart View - full circle]]<br />
{{stub}}<br />
<br />
View showing the active person's direct descendants as a fan chart.<br />
<br />
* [https://gramps-project.org/2012/09/descendant-fanchart/ Descendant Fan View]<br />
<br />
* See also: [[Gramps_5.1_Wiki_Manual_-_Gramplets#Descendant_Fan_Chart|Descendant Fan Chart Gramplet]]<br />
<br />
{{-}}<br />
==== Configure the active view ====<br />
<br />
[[File:ChartsCategory-DescendantFanChartView-ConfigureCharts-dialog-default-50.png|right|thumb|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Charts Category - Descendant Fan Chart View - Configure the active view - dialog - showing Defaults on Layout tab]]<br />
{{stub}}<br />
{{-}}<br />
<br />
=== 2-Way Fan View ===<br />
<br />
[[File:ChartsCategory-2wayfan-fullcircle-ances4gen-descen4gen-default-50.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} 2-Way Fan Chart View - 4 Generations of Ancestors (Top) / 4 Generations of Descendants (bottom)]]<br />
{{stub}}<br />
<br />
<br />
* See also: [[Gramps_5.1_Wiki_Manual_-_Gramplets#2-Way_Fan_Chart|2-Way Fan Chart Gramplet]]<br />
<br />
* [https://github.com/gramps-project/gramps/pull/222 Feature: Gep-030 FanChart2Way]<br />
{{-}}<br />
==== Configure the active view ====<br />
<br />
[[File:ChartsCategory-2-WayFanChartView-ConfigureCharts-dialog-default-50.png|right|thumb|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Charts Category - 2-Way Fan Chart View - Configure the active view - dialog - showing Defaults on Layout tab]]<br />
{{stub}}<br />
{{-}}<br />
<br />
===Charts Category Bottombar tabs===<br />
<br />
The {{man label|Charts Category}} by default displays no Gramplets in the [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tab. You may add them as required.<br />
{{-}}<br />
===Charts Category Sidebar tabs===<br />
<br />
The {{man label|Charts Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tabs.<br />
{{-}}<br />
====Filter====<br />
Only the {{man label|Fan Chart View}} and {{man label|Descendant Fan View}} have a Filter shown by default.<br />
<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
{{-}}<br />
<br />
== Events Category ==<br />
The {{man label|Events Category}} shows the {{man label|Events View}} that lists the all the events recorded in the Family Tree. Events can be shared between multiple people and multiple families.<br />
<br />
See also:<br />
* [[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Editing information about events]]<br />
{{-}}<br />
===Events View===<br />
[[File:EventsCategory-EventsListView-example-50.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Events Category - Events (List) View - example]]<br />
<br />
From the {{man label|Events View}} list the following columns are available for display: {{man label|Description}} , {{man label|ID}} , {{man label|Type}} , {{man label|Main Participants}} , {{man label|Date}} , {{man label|Place}} and {{man label|Last Changed}}.<br />
<br />
The default view displays the {{man label|Description}} , {{man label|ID}} , {{man label|Type}} , {{man label|Date}} and {{man label|Place}} of the event. The {{man label|Column Editor}} dialog can be used to add, remove and rearrange the displayed columns. This can be accessed from the {{man button|Configure View...}} button on the toolbar.<br />
<br />
The list of Events can be sorted in the usual manner, by clicking on the column heading. Clicking once sorts in ascending order, clicking again sorts in descending order.<br />
<br />
{{man warn|Use meaningful event descriptions|Because events can be shared, you should take the extra time to give each event a unique and meaningful description. This will help you find the correct event when you share events.}}<br />
{{-}}<br />
===Events Category Bottombar tabs===<br />
<br />
The {{man label|Events Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tabs.<br />
{{-}}<br />
====Gallery====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Gallery|Gallery]] Gramplet<br />
{{-}}<br />
====Citations====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Citations|Citations]] Gramplet<br />
{{-}}<br />
====Notes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Notes|Notes]] Gramplet<br />
{{-}}<br />
====Attributes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Attributes|Attributes]] Gramplet<br />
{{-}}<br />
====References====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#References|References]] Gramplet<br />
{{-}}<br />
===Events Category Sidebar tabs===<br />
<br />
The {{man label|Events Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tabs.<br />
{{-}}<br />
====Filter====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
{{-}}<br />
<br />
== Places Category ==<br />
<br />
The {{man label|Places Category}} holds two views that show [[Gramps_Glossary#place|places]]: either as grouped (hierarchically in a tree) or ungrouped (in a simple flat list). Each view lists the geographical places in which the events of the database took place. These could be places of birth, death, and marriages of people, as well as their home, employment, education addresses, or any other conceivable reference to the geographical location. <br />
<br />
[[File:Toolbar-Place-Options_51.png|center|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Configure Relationships Category - Content (tab)]]<br />
The Places View lists the places' {{man label|Name}} , {{man label|Title}} , {{man label|ID}} , {{man label|Type}} , {{man label|Code}} , {{man label|Latitude}} , {{man label|Longitude}} , {{man label|Private}} , {{man label|Tags}} , and {{man label|Last Changed}}. All of these columns can be used for sorting by clicking on a column heading.<br />
<br />
====&#x2699; Configuration Options====<br />
[[File:Menubar-View-overview-example-50.png|right|thumb|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} View menu for the People category View]]<br />
You can control the layout (which columns will be displayed and their order of display) by clicking the [[File:Gramps-config.png|34px]]{{man button|Configure...}}&nbsp;button, choosing {{Man menu|View&nbsp;&#x27a1;&nbsp;Configure...}} from the View menu, or pressing the ''Configure active view'' [[Gramps_5.1_Wiki_Manual_-_Keybindings#Common_keybindings|keyboard keybinding]].<br />
{{-}}<br />
[[File:ConfigurePersonView-51.png|right|thumb|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Configure Person Category View]]The {{man label|Column Editor}} dialog may be used to add, remove and rearrange the displayed columns. Changes will only be enacted when the {{man button|Apply}} button is clicked.<br />
<br />
Once the View columns are shown, clicking once on the column header sorts in ascending order, clicking again sorts in descending order. <br />
<br />
These Configuration options and the current [[Gramps_5.1_Wiki_Manual_-_Filters|filters]] also constrain the data exported via the {{Man menu|Family Trees&nbsp;&#x27a1;&nbsp;[[Gramps_5.1_Wiki_Manual_-_Settings#Export_View|Export View...]]}}<br />
{{-}}<br />
<br />
===Places List View===<br />
[[File:PlacesCategory-PlaceListView-50.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Places Category - Place (List) View - example]]<br />
<br />
The Place List View shows all the places in one long list.<br />
{{-}}<br />
<br />
===Places Tree View===<br />
[[File:PlacesCategory-PlaceTreeView-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Places Tree View - example]]<br />
<br />
The Place Tree View groups the places in a hierarchy: country, county, ... etc<br />
<br />
{{-}}<br />
<br />
===Map Service===<br />
{{man note|This feature is limited|And may not always produce the results you desire.}}<br />
<br />
[[File:PlacesCategory-AttemptToSeeSelectedLocation-example-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Places Category - "Attempt to see selected locations with a Map Service (OpenstreetMap, Google Maps, ..." button - example]]<br />
<br />
If a place has been highlighted, you may display the place in a web browser by selecting the {{man button|Attempt to see selected locations with a Map Service (OpenstreetMap, Google Maps, ...}} button.<br />
<br />
Your default web browser should open, attempting to use either the recorded coordinates (longitude and latitude) or the place name to display the location using the Maps provider web site. Different map services might have different requirements for the location description.<br />
<br />
{{-}}<br />
[[File:PlacesCategory-MapServices-list-51.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Places Category - "Select a Map Service" button - showing list of options]]<br />
<br />
From the {{man button|Select a Map Service}} drop down list you can choose the map service you want to use from the following three options:<br />
* '''OpenStreetMap'''(default) - Uses longitude and latitude coordinates if present, otherwise uses city and country, or uses description of the place.<br />
* ''EniroMaps'' - Valid for places within Sweden and Denmark, only if longitude and latitude are available, otherwise uses city and country, or uses description of the place.<br />
* ''GoogleMaps'' - Uses longitude and latitude coordinates if present, otherwise uses city and country, or uses description of the place.<br />
<br />
{{-}}<br />
See also:<br />
* [[Map_Services|Map Services - Google Earth]] - addon allows you to use Google Earth.<br />
<br />
===Places Category Bottombar tabs===<br />
<br />
The {{man label|Places Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tabs.<br />
{{-}}<br />
====Details====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Details|Details]] Gramplet<br />
{{-}}<br />
====Location====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Locations|Locations]] Gramplet<br />
{{-}}<br />
<br />
====Gallery====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Gallery|Gallery]] Gramplet<br />
{{-}}<br />
====Events====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Events|Events]] Gramplet<br />
{{-}}<br />
====Citations====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Citations|Citations]] Gramplet<br />
{{-}}<br />
====Notes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Notes|Notes]] Gramplet<br />
{{-}}<br />
====References====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#References|References]] Gramplet<br />
{{-}}<br />
===Places Category Sidebar tabs===<br />
<br />
The {{man label|Places Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tabs.<br />
{{-}}<br />
====Filter====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
{{-}}<br />
<br />
== Geography Category ==<br />
<br />
{{man tip|Note|The Geography category is only present if the prerequisite program <code>[[Gramps_5.1_Wiki_Manual_-_Categories#Prerequisites_to_see_the_geography_view|OsmGpsMap]]</code> is present that Gramps can use.}}<br />
<br />
[[File:GeographyCategory-GeoPlacesView-AllKnownPlaces-openstreemap-example-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "All known Places" GeoPlaces View - Geography Category - example using Openstreetmap - sidebar and bottombar hidden]]<br />
<br />
The {{man label|Geography Category}} shows place event data visually on a map. It contains many Geographic Views, which allows you to see the people and their events placed on a map via an internet map provider (OpenStreetMap, Google maps ...).<br />
<br />
The following Geographic Views are available:<br />
* Show all places in your family tree<br />
* Show all places connected to the active person<br />
* Show all places connected to the active family<br />
* Show all places connected to all events<br />
* Show all places connected to a filtered selection of events<br />
* Show if two people have been able to meet<br />
* Show if two families have been able to meet<br />
* Show all displacements or moves for one person and their descendants<br />
<br />
These views are accessible via the buttons on the toolbar. To filter on places or events, activate the filter sidebar via the menu {{man menu|View->Filter Sidebar}}<br />
<br />
To have these Geographic views work correctly, you need:<br />
* To have events related to places.<br />
* These places must have coordinates : latitude and longitude.<br />
* If one place has no coordinates, it will never appear on the map.<br />
* If you have an active internet connection, for all moves on the map, all zoom ... all tile maps are saved.<br />
** When you are without an internet connection, all tile maps are cached from the previous session and can be used.<br />
** So, the map can be used without an internet connection and all already visited places can be shown again.<br />
** The only thing to do is for each place or area you want to use without an internet connection is to select them, zoom into these places. You'll be able to use them again without connection.<br />
<br />
{{man warn|BE CAREFUL|The {{man label|Geography Category}} views may use many [https://en.wikipedia.org/wiki/Gigabyte Gigabytes] of storage space on your computer. If you use several maps, you need to have this same gigabytes size multiply by the number of map used.}}<br />
<br />
==== The different views ====<br />
===== All known places =====<br />
<br />
[[File:GeographyCategory-GeoPlacesView-AllKnownPlaces-openstreemap-example-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "All known Places" GeoPlaces View - Geography Category - example using Openstreetmap - sidebar and bottombar hidden]]<br />
<br />
This view show all places with coordinates in the database.<br />
<br />
from Gramps 4.2.2, for performances reason, by default, the view show only the place related to the places history or the filtered places.<br />
If you really want to see all places, you need to select the popup menu from the context menu [[Gramps_5.1_Wiki_Manual_-_Categories#button_3_.28_right_button_.29|right button]] and select "show all places".<br />
{{-}}<br />
[[File:GeographyCategory-AllKnownPlaces-Configure-tab-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} {{man label|The places marker color}} tab for the "All known Places" GeoPlaces View - Configure the active view]]<br />
<br />
;Configure the active view: {{man label|The places marker color}} tab<br />
The configuration menu tab for has the following options:<br />
<br />
The {{man label|All known Places}} view is the only Geography view that allows you to change the color used for the place type markers.<br />
<br />
The colors are green for the following map renders:<br />
* Openstreetmap <br />
* Maps for free<br />
* Opencyclemap and Public transport.<br />
<br />
All other marker renders are red.<br />
<br />
Click on the {{man button|Configure the active view}} button on the toolbar.<br />
<br />
Then click on the {{man label|The places marker color}} tab.<br />
<br />
For each type of place, you can select and choose a color. The default color is green "#008b00"<br />
<br />
See also:<br />
* [[Gramps_5.1_Wiki_Manual_-_Categories#Can_we_change_the_marker.27s_color_.3F|Can we change the marker color?]]<br />
{{-}}<br />
<br />
===== All known places for one Family =====<br />
<br />
[[File:GeographyCategory-AllKnownPlacesForOneFamily-example-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "All known places for one Family" GeoFamily View - Geography Category - example using Openstreetmap - sidebar and bottombar hidden]]<br />
<br />
This view show all places visited by all family members during their lives.<br />
<br />
This view is not connected to filters. It only depend on the active family and the history.<br />
{{-}}<br />
;Configure the active view: {{man label|Specific parameters}} tab<br />
The configuration menu tab for this view has no additional options.<br />
{{-}}<br />
<br />
===== Have they been able to meet ? =====<br />
<br />
[[File:GeographyCategory-HaveTheyBeenAbleToMeet-default-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Have they been able to meet ?" GeoClose View - Geography Category - example using Openstreetmap - sidebar and bottombar hidden]]<br />
<br />
This view is used to show if two persons were able to meet during their life.<br />
<br />
You must select one reference person :<br />
#From the menu popup : Choose the reference person<br />
#From the toolbar<br />
<br />
When the reference person is active, you'll see its life way.<br />
For each known place with coordinates, you'll see a circle or an oval depending on the longitude.<br />
<br />
The circle radius can be tuned in the configuration view.<br />
This value is defined in tenth of degree.<br />
<br />
{{-}}<br />
[[File:GeographyCategory-HaveTheyBeenAbleToMeet-Configure-tab-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "The selection parameters" tab for the "Have they been able to meet ?" GeoClose View - Configure the active view]]<br />
<br />
;Configure the active view: {{man label|The selection parameters}} tab<br />
See the configuration menu tab for additional options.<br />
{{-}}<br />
<br />
===== All places related to Events =====<br />
<br />
[[File:GeographyCategory-AllPlacesRelatedToEvents-example-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "All places related to Events" GeoEvents View - Geography Category - example using Openstreetmap - sidebar and bottombar hidden]]<br />
<br />
This view is used to show all places related to events.<br />
It can take some time to show when we have many events.<br />
<br />
from Gramps 4.2.2, for performances reason, by default, the view show only the place related to the events history or the filtered events.<br />
If you really want to see all events, you need to select the popup menu from the context menu [[Gramps_5.1_Wiki_Manual_-_Categories#button_3_.28_right_button_.29|right button]] and select "show all events".<br />
{{-}}<br />
;Configure the active view: {{man label|Specific parameters}} tab<br />
The configuration menu tab for this view has no additional options.<br />
{{-}}<br />
<br />
===== All known places for one Person =====<br />
[[File:GeographyCategory-AllKnownPlacesForOnePerson-example-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "All known places for one Person" GeoPerson View - Geography Category - example using Openstreetmap - sidebar and bottombar hidden]]<br />
<br />
This view show all places visited by one person during that persons life.<br />
<br />
This view is not connected to filters. It only depend on the active person and the history.<br />
<br />
If you want to use the animate functionality, click on the [[Gramps_5.1_Wiki_Manual_-_Categories#button_3_.28_right_button_.29|right button]] of the mouse. You'll get a popup menu.<br />
From the menu popup, you can select 'animate' to see the life way of the current person:<br />
<br />
If the active person has several related events, you can see a virtual move between those markers. The move is related to years or distance and can be modified in the person map preferences. If the distance between to markers is greater than a value in tenth of degree, we show moves depending on distance instead of years. In these case, the number of steps between these two markers can be modified. You can modify the animation speed between steps. The moves start at the first event year until the last event year.<br />
{{-}}<br />
[[File:GeographyCategory-AllKnownPlacesForOnePerson-Configure-tab-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "The animation parameters" tab for the "All known places for one Person" GeoPerson View - Configure the active view]]<br />
<br />
;Configure the active view: {{man label|The animation parameters}} tab<br />
See the configuration menu tab for the following options you can change:<br />
*A slider to set the {{man label|Animation speed in milliseconds(big value means slower:)}} (default: ''100'')<br />
*A slider to set the {{man label|How many steps between two markers when we are on large move?:}} (default: ''20'')<br />
*A slider to set the {{man label|The minimum latitude/longitude to select large move. The value is in tenth of degree.}} (default: ''5'')<br />
{{-}}<br />
====== All known places for one person with graphical information (KML files) ======<br />
<br />
[[File:gramps-person-kml.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} One person with 3 KML files]]<br />
<br />
If KML files are added as Media objects in the Gallery tab for the various records, this Geography view will show one path or one surface for each KML file.<br />
<br />
In the following example, you see 3 layered KML files rendered from different Gallery tabs referenced by this Person:<br />
* a farm limits outline KML in the Birth Event.<br />
* a path KML used to go to school in the Education Event.<br />
* a parish (or municipality) limits outline KLM in the Place Gallery tab for the Baptism Event.<br />
<br />
In the case of the Farm limits outline, the KLM was added to the Gallery tab of the Birth Event (rather than being applied to that of the re-useable [[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Place_Editor_dialog|'Farm' type Place]]) because acreage was bought and sold over the years. This outline represented the Farm size at the date of birth.<br />
<br />
See [[Gramps_5.1_Wiki_Manual_-_Categories#Adding_places_from_KML_files|Adding places from KML files]]<br />
<br />
{{man tip|What is a KML file ?|See the article [https://en.wikipedia.org/wiki/Keyhole_Markup_Language Keyhole Markup Language] From Wikipedia, the free encyclopedia}}<br />
{{-}}<br />
<br />
===== Every residence or move for a person and any descendants =====<br />
<br />
[[File:GeographyCategory-EveryResidenceOrMoveForAPersonAndAnyDescendants-example-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Every residence or move for a person and any descendants" GeoMoves View - Geography Category - example using Openstreetmap - sidebar and bottombar hidden]]<br />
<br />
This view is used to show all descendant's life ways.<br />
<br />
They are displayed by generation.<br />
You can change the delay between the generation display in the view configuration.<br />
<br />
This view is not connected to filters. It only depend on the active person and the history.<br />
{{-}}<br />
[[File:GeographyCategory-EveryResidenceOrMoveForAPersonAndAnyDescendants-Configure-tab-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "The parameters for moves" tab for the "Every residence or move for a person and any descendants" GeoMoves View - Configure the active view]]<br />
<br />
;Configure the active view: {{man label|The parameters for moves}} tab<br />
See the configuration menu tab for the following options you can change:<br />
*A slider to set {{man label|The maximum number of generations.}} to show. (default: ''20'')<br />
*A slider to set the {{man label|Time in milliseconds between drawing two generations.}} (default: ''500'')<br />
{{-}}<br />
<br />
===== Have these two families been able to meet ? =====<br />
<br />
[[File:GeographyCategory-HaveTheseTwoFamiliesBeenAbleToMeet-example-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Have these two families been able to meet ?" GeoFamClose View - Geography Category - example using Openstreetmap - sidebar and bottombar hidden]]<br />
<br />
This view is used to show if two families were able to meet during their life.<br />
<br />
You must select one reference family :<br />
* From the menu popup : Choose the reference family<br />
* From the toolbar<br />
<br />
When the reference family is active, you'll see all its member's life way.<br />
For each known place with coordinates, you'll see a circle or an oval depending on the longitude.<br />
<br />
The circle radius can be tuned in the configuration view.<br />
This value is defined in tenth of degree.<br />
{{-}}<br />
[[File:GeographyCategory-HaveTheseTwoFamiliesBeenAbleToMeet-Configure-tab-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "The selection parameters" tab for the "Have these two families been able to meet ?" GeoFamClose View - Configure the active view]]<br />
<br />
;Configure the active view: {{man label|The selection parameters}} tab<br />
See the configuration menu tab for additional options.<br />
{{-}}<br />
<br />
===Usage===<br />
====The configuration====<br />
Via the toolbar {{man button|Configure View...}} button (or via the menu {{man menu|View}})<br />
<br />
=====All views=====<br />
[[File:ConfigureGeography-the-map-tab-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Configure Geography - "The map" tab]]<br />
<br />
{{man label|The map}} tab contains options common to all Geography views: <br />
* {{man label|Where to save the tiles of the tiles for offline mode.:}} (default is ''<code>$HOME/.gramps/maps</code>''). If required you can change the directory where map tile files are stored on your computer. {{man menu|Be careful, it can take several gigabytes, and if on a metered internet connection may result in a monetary cost to you.}}.<br />
** {{man button|Select tile cache directory for offline mode}} button<br />
* A slider for {{man label|Zoom used when centering:}} (default: ''12''). The zoom level for when we center the map or when we select one marker. Every time the Geographic View redraws the map, this zoomlevel will be used.<br />
* A slider for {{man label|The maximum number of places to show:}} (default: ''5000''). Reducing this number for faster map drawing but with less life ways.<br />
* {{checkbox|1}} {{man label|Use keypad for shortcuts: Either we choose the + and - from the keypad if we select this or we use the characters from the keyboard.}} - checkbox selected by default.<br />
<br />
{{-}}<br />
<br />
=====Specific views=====<br />
See the description of the view.<br />
<br />
====How to zoom and move around the map ?====<br />
=====Zoom in and Zoom out the map=====<br />
To zoom, you can use :<br />
* The +/- buttons on the top left of the map<br />
* The scroll mouse.<br />
* The "+" or "-" key on the keypad (default).<br />
<br />
You can replace the numeric keypad by the alpha numeric keyboard in the configuration view.<br />
<br />
=====Move around the map=====<br />
To move around the map, you can :<br />
* Click on the map, then drag it.<br />
* Use the arrows.<br />
<br />
====The mouse actions on the map====<br />
<br />
The right button below is for one right handed person.<br />
This will be the left button for one left handed person.<br />
<br />
=====button 1 ( left button )=====<br />
You have two usages for the button 1 :<br />
# The marker selection.<br />
# Valid the region selection<br />
<br />
=====button 2 ( middle button )=====<br />
The only usage for this button is to select an area on the map.<br />
# when pressed : start the region selection<br />
# when released, end the region selection.<br />
You must use the button 1 to validate the selected region when finished.<br />
<br />
=====button 3 ( right button )=====<br />
Only one usage for this button.<br />
* show the [https://en.wikipedia.org/wiki/Context_menu context menu popup].<br />
<br />
=====The mouse over a marker=====<br />
When the mouse is placed over one marker, we display the place name in the status bar.<br />
<br />
====The menu popup====<br />
From this context menu, you have the following functions available for views :<br />
*hide or show the crosshair<br />
*lock or unlock the zoom<br />
*change the default map (provider)<br />
*add a place and link a place at the mouse position<br />
*add a place from kml file<br />
*center the map at the mouse position.<br />
*center the map depending on a place from sub menu.<br />
*remove all tiles already uploaded for the current provider<br />
*"show all places" or "show all events" for the "all known places" view or "all places related to events" view.<br />
<br />
====Click on a marker====<br />
We have two cases :<br />
# events : For each event, we can edit this event or center the map on this place.<br />
# places : For each place, we can edit this place or center the map on this place.<br />
When centering the map, the zoom used is defined in the geography preferences.<br />
<br />
We may have several markers in the click area depending on the zoom.<br />
In this case, We show for each marker all related events and/or places.<br />
We obtain a mix between the two cases described above.<br />
<br />
====Adding or Linking to a place====<br />
For this, click on the [[Gramps_5.1_Wiki_Manual_-_Categories#button_3_.28_right_button_.29|right button]] of the mouse, you'll get a popup menu.<br />
In this menu, you can select {{man label|Add place}} or {{man label|Link place}}<br />
<br />
When you add a place or try to link a place to the position of the mouse, you'll get a place selection in a region.<br />
You'll see on the map a circle in which you may choose markers place names. You can adjust the circle size with the cursor. Depending on the diameter of this circle, a list is created. If the place has already some filled fields, you'll see these values in a green color row. If you agree, you double click on this row. if you don't agree, you can choose another row.<br />
<br />
Another way to set latitude and longitude :<br />
* Download the [[Place completion tool]] via the [[5.1_Addons#Installing_Addons_in_Gramps|Addons manager]]. If you download the data of your country, this tool can add latitude-longitude to all your places.<br />
<br />
====Adding places from KML files====<br />
<br />
For this, click on the [[Gramps_5.1_Wiki_Manual_-_Categories#button_3_.28_right_button_.29|right button]] of the mouse, you'll get a context popup menu.<br />
<br />
In this menu, you can select {{man label|Add place from KML}}<br />
<br />
You will get the {{man label|Select a kml file used to add places}} file chooser dialog. Select the file you want to add.<br />
<br />
If you have several places in the same KML file, you will get one place editor for each place. Be careful.<br />
<br />
====How to change the map provider ?====<br />
Several map providers are available in Gramps.<br />
<br />
Click on the [[Gramps_5.1_Wiki_Manual_-_Categories#button_3_.28_right_button_.29|right button]] of the mouse, you'll get a popup menu.<br />
<br />
In the bottom of this menu, you can select a new provider.<br />
<br />
The following providers are available :<br />
* '''OpenStreetMap''' (default) : The advantage of [http://www.openstreetmap.org/ OpenStreetMap] is that it is a free project, so you can update the maps yourself with missing information via their website.<br />
* Maps For Free<br />
* OpenCycleMap<br />
* Public Transport<br />
* Google street<br />
* Google sat<br />
* Google hybrid<br />
* Virtualearth street<br />
* Virtualearth sat<br />
* Virtualearth hybrid<br />
{{man tip|Some maps are not free, please read the map provider ''Terms of Service'' :|<br />
[https://www.google.com/intl/en_ALL/help/terms_maps.html Google street], <br />
[https://www.google.com/intl/en_ALL/help/terms_maps.html Google sat], <br />
[https://www.google.com/intl/en_ALL/help/terms_maps.html Google hybrid], <br />
[http://www.microsoft.com/maps/product/terms.html Virtualearth street], <br />
[http://www.microsoft.com/maps/product/terms.html Virtualearth sat], and <br />
[http://www.microsoft.com/maps/product/terms.html Virtualearth hybrid]<br />
<br />
Note that Virtualearth is now Bing maps}}<br />
<br />
====Can we change the marker's color ?====<br />
<br />
Only the {{man label|[[Gramps_5.1_Wiki_Manual_-_Categories#All_known_places|All known Places]]}} view supports changing the place type markers colors all the other views are hard coded in Gramps.<br />
{{-}}<br />
<br />
====How to get/remove the crosshair ?====<br />
It can be useful to have the crosshair visible to see the center of the map.<br />
This functionality is available with the [[Gramps_5.1_Wiki_Manual_-_Categories#button_3_.28_right_button_.29|right button]] of the mouse. you'll get a popup menu.<br />
Select Add or Remove cross hair.<br />
This is useful to add or link places to the correct latitude-longitude coordinates<br />
<br />
====How to lock/unlock the map ?====<br />
When we change the map ( person to family, ... ), the zoom is recalculated.<br />
It can be useful in some case to keep the same zoom and position when we change the map provider.<br />
For this, click on the [[Gramps_5.1_Wiki_Manual_-_Categories#button_3_.28_right_button_.29|right button]] of the mouse, you'll get a popup menu.<br />
In this menu, you can select lock or unlock zoom and position.<br />
<br />
===Prerequisites to see the geography view===<br />
For Gramps 5.x, you need to install [http://nzjrs.github.io/osm-gps-map/ osmgpsmap] version 1.0 and above and the associated gir package.<br />
<br />
For example on ubuntu, you must have:<br />
<code>gir1.2-osmgpsmap-1.0</code> and <code>libosmgpsmap-1.0-0</code><br />
<br />
===Possible problems===<br />
*No view : do you have <code>osmgpsmap</code> installed ? (''<code>gramps -v</code>'' from the command line may help you)<br />
*No tiles : do you have an internet connection active ?<br />
*No tiles for one provider : if other providers are OK, file a bug<br />
*Missing tiles : you have no internet connection and it's the first time you try to show the current place.<br />
*Missing tiles : this can be the same as no tiles for one provider if they modify the access rules (i.e user-agent)<br />
*Other : [[Using_the_bug_tracker|Report a bug]]<br />
<br />
===Geography Category Bottombar tabs===<br />
<br />
The {{man label|Geography Category}} by default displays no Gramplets in the [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tab. You may add them as required.<br />
<br />
{{-}}<br />
<br />
===Geography Category Sidebar tabs===<br />
<br />
The {{man label|Geography Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tabs.<br />
<br />
{{-}}<br />
====Filter====<br />
<br />
The filter type may change depending on the view selected.<br />
<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
{{-}}<br />
<br />
== Sources Category ==<br />
<br />
The {{man label|Sources Category}} offers two view modes ({{man label|Citation Tree}} View and {{man label|Sources List}} View) that list the sources of certain information stored in the family tree. The record selection, column configuration and Gramplet selections are independent for each view mode.<br />
<br />
Sources can include various documents: birth, death, and marriage certificates; books; films; journals; private diaries - nearly anything that can be described as genealogical evidence. Gramps gives you the option to provide citations of sources for each (Event, Person, Place, Media, Note, et cetera) object you create. <br />
<br />
By default, the Sources View mode lists the {{man label|Title}}, {{man label|ID}}, and {{man label|Author}} of the source, as well as any {{man label|Publication}} information that may be associated with it. The list of Sources can be re-sorted by clicking on a different column heading. Clicking the header the first time sorts the rows in ascending order based on that column. Clicking again reverses to descending order. <br />
<br />
The {{man label|Column Editor}} tab of the Configure Sources dialog can be used to add, remove and rearrange the displayed columns. Click the [[file:gramps-config.png|x32px]] {{man rollover|Configure the active view}} toolbar button or select Configure&hellip; from the {{man menu|Edit}} menu to open the dialog. <br />
<br />
You can select the {{man button| {{icon| stock_add}}}} {{man rollover|Add a new source}} toolbar button to create a new source or {{man button| {{icon| stock_edit}}}} {{man rollover|Edit the selected source}} button to edit the sources selected in the list. Either action will invoke the {{man label|[[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#New_Source_dialog|Source Editor]]}} dialog.<br />
<br />
* See [[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_sources|Editing information about sources]] <br />
{{-}}<br />
===Citation Tree View===<br />
[[File:SourcesCategory-CitationTreeView-example-50.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Sources Category - Citation Tree - View]]<br />
<br />
The default (Citation Tree View mode) list will also show all the sources. In addition, it allows the user to see the Citations associated with each source by clicking on the [https://en.wikipedia.org/wiki/Disclosure_widget disclosure triangle] node {{man button|&#x25B6;}}expand or {{man button|&#x25BC;}}collapse disclosure triangular widget. All the nodes of the tree view mode can be simultaneously collapsed or expanded from the pop-up menu shown by right-clicking:<br />
*{{man menu|Back}}<br />
*{{man menu|Forward}}<br />
*{{man menu|Expand all Nodes}}<br />
*{{man menu|Collapse all Nodes}}<br />
*{{man menu|Add&hellip;}}<br />
*{{man menu|Add citation&hellip;}}<br />
*{{man menu|Edit&hellip;}}<br />
*{{man menu|Delete}}<br />
*{{man menu|Merge&hellip;}}<br />
*{{man menu|Quick View &#x25B6; Source or Citation References}}<br />
{{-}}<br />
<br />
===Sources List View===<br />
{{stub}}<br />
[[File:SourcesCategory-SourcesListView-example-50.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Sources Category - (List) View]]<br />
<br />
The alternative view only shows the Sources as a list.<br />
{{-}}<br />
===Sources Category Bottombar tabs===<br />
<br />
The {{man label|Sources Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tabs.<br />
{{-}}<br />
====Gallery====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Gallery|Gallery]] Gramplet<br />
{{-}}<br />
====Notes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Notes|Notes]] Gramplet<br />
{{-}}<br />
====References====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#References|References]] Gramplet<br />
{{-}}<br />
===Sources Category Sidebar tabs===<br />
<br />
The {{man label|Sources Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tabs.<br />
{{-}}<br />
====Filter====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
{{-}}<br />
<br />
== Citations Category ==<br />
<br />
The {{man label|Citations Category}} shows the Citation list View that show the citations for certain information stored in the family tree.<br />
<br />
Citations specify which parts of a source are relevant to the information in the database. For example, a Source may be a book, and the citation may be a particular page in the book. Gramps gives you the option to provide a citation for each event you record (births, deaths, marriages, etc.). <br />
<br />
{{-}}<br />
===Citations List View===<br />
<br />
[[File:CitationsCategory-CitationsListView-example-50.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Citations Category - Citations (List) View - example]]<br />
<br />
The Citations List View shows the {{man label|Volume/Page}} , {{man label|ID}} , and {{man label|Date}} of the citation, as well as any {{man label|Confidence}} in the evidence.<br />
<br />
The list of Citations can be sorted by clicking on a column heading.<br />
<br />
Clicking once sorts in ascending order, clicking again sorts in descending order. The {{man label|Column Editor}} dialog can be used to add, remove and rearrange the displayed columns.<br />
<br />
{{-}}<br />
<br />
===Citations Category Bottombar tabs===<br />
<br />
The {{man label|Citations Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tabs.<br />
{{-}}<br />
====Gallery====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Gallery|Gallery]] Gramplet<br />
{{-}}<br />
====Notes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Notes|Notes]] Gramplet<br />
{{-}}<br />
====References====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#References|References]] Gramplet<br />
{{-}}<br />
===Citations Category Sidebar tabs===<br />
<br />
The {{man label|Citations Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tabs.<br />
{{-}}<br />
====Filter====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
{{-}}<br />
<br />
== Repositories Category ==<br />
<br />
The {{man label|Repositories Category}} shows the Repository List View. A repository can be thought of as a collection of sources. Each source in the family tree may be a reference to a repository (such as a library) in which it belongs.<br />
<br />
{{-}}<br />
===Repository List View===<br />
<br />
[[File:RepositoriesCategory-RepositoriesListView-example-50.png|450px|right|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Repositories (list) view - example]]<br />
<br />
This view shows a list of all recorded repositories.<br />
{{-}}<br />
<br />
===Repository Category Bottombar tabs===<br />
<br />
The {{man label|Repository Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tabs.<br />
{{-}}<br />
====Details====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Details|Details]] Gramplet<br />
{{-}}<br />
====Notes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Notes|Notes]] Gramplet<br />
{{-}}<br />
====References====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#References|References]] Gramplet<br />
{{-}}<br />
===Repository Category Sidebar tabs===<br />
<br />
The {{man label|Repository Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tabs.<br />
{{-}}<br />
====Filter====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
{{-}}<br />
<br />
== Media Category ==<br />
<br />
The {{man label|Media Category}} shows the Media List View, which list the Media Objects stored in the family tree.<br />
<br />
Media Objects are technically any files that relate somehow to the stored genealogical data.<br />
<br />
Most frequently, these are images, audio files, animation files, etc. <br />
{{-}}<br />
===Media List View===<br />
<br />
[[File:MediaCategory-MediaListView-example-50.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Media Category - Media (List) View - example]]<br />
<br />
The Media List View shows the following columns for the list {{man label|Name}} , {{man label|ID}} , {{man label|Type}}, {{man label|Path}} and {{man label|Date}} of the Media Object.<br />
<br />
The {{man label|Column Editor}} dialog may be used to rearrange the displayed columns, which obey usual sorting rules. <br />
{{-}}<br />
<br />
===Media Category Bottombar tabs===<br />
<br />
The {{man label|Media Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tabs.<br />
{{-}}<br />
====Preview====<br />
In the "Preview" tab you can double click on the media/photo to open it in the default picture viewer.<br />
<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Media_Preview|Media Preview]] Gramplet<br />
{{-}}<br />
====Citations====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Citations|Citations]] Gramplet<br />
{{-}}<br />
====Notes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Notes|Notes]] Gramplet<br />
{{-}}<br />
====Attributes====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Attributes|Attributes]] Gramplet<br />
{{-}}<br />
====Image Metadata====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Image Metadata|Image Metadata]] Gramplet<br />
{{-}}<br />
====References====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#References|References]] Gramplet<br />
{{-}}<br />
===Media Category Sidebar tabs===<br />
<br />
The {{man label|Media Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tabs.<br />
{{-}}<br />
====Filter====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
{{-}}<br />
<br />
== Notes Category ==<br />
<br />
The {{man label|Notes Category}} shows the Notes List View, which list text note (either pure text or preformated), as stored in the other objects.<br />
<br />
See also:<br />
* [[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Editing information about notes]]<br />
{{-}}<br />
===Notes List View===<br />
<br />
[[File:NotesCategory-NotesListView-example-50.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Notes Category - Notes (List) view]]<br />
<br />
The Notes List View shows a list of text notes.<br />
<br />
The functionality of the notes View is similar to the other views. The view lists all {{man label|Notes}} stored in the Family Tree. <br />
<br />
Using the menu {{man menu|View ->Configure View...}} you open the {{man label|Column Editor}} and you can change the displayed columns. The possibilities are {{man label|Preview}}, {{man label|ID}}, {{man label|Type}}, {{man label|Private}}, {{man label|Tags}} and {{man label|Last Changed}}.<br />
<br />
The {{man label|Type}} can be ([[Gramps_5.1_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#note_type|amongst others]]): ''Event Note'', ''Address Note'', ''Source text'', ''Place Note''. (In version 5.1, the built-in {{man label|Type}} list includes: ''Citation'', ''General'', ''HTML code'', ''Link'', ''Report'', ''Research'', ''Source text'', ''To Do'', ''Transcript'', ''Unknown'')<br />
<br />
Double-clicking on a Note in the list will bring up a window where you can edit the Note. You can change fonts, font color and background color. A spellchecker is available for ''English'' and your local language.<br />
{{-}}<br />
<br />
===Notes Category Bottombar tabs===<br />
<br />
The {{man label|Notes Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] tabs.<br />
{{-}}<br />
====References====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#References|References]] Gramplet<br />
{{-}}<br />
===Notes Category Sidebar tabs===<br />
<br />
The {{man label|Notes Category}} shows the following [[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] tabs.<br />
{{-}}<br />
====Filter====<br />
See [[Gramps_5.1_Wiki_Manual_-_Gramplets#Filter|Filter]] Gramplet<br />
<br />
{{-}}<br />
{{man index|Gramps 5.1 Wiki Manual - Main Window|Gramps 5.1 Wiki Manual - Manage Family Trees|5.1}}<br />
{{languages|Gramps 5.1 Wiki Manual - Categories}}<br />
{{grampsmanualcopyright}}<br />
<br />
[[Category:Documentation]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Gramps_Glossary&diff=78639Gramps Glossary2020-05-28T09:07:39Z<p>GulliblePangolin: /* G */</p>
<hr />
<div>{{languages|Gramps_Glossary}}<br />
__NOTOC__<br />
This Glossary gives an overview of terms that appear in [https://gramps-project.org/blog/features/ Gramps], with a short description, and a link to relevant articles. <br />
<br />
For a glossary of genealogical terms, see [[Genealogy Glossary]].<br />For a list of pages dedicated to terms in this Glossary, see [[:Category:Gramps_terminology| Category:Terminology]]<br />
<br />
[[#A|A]] [[#B|B]] [[#C|C]] [[#D|D]] [[#E|E]] [[#F|F]] [[#G|G]] [[#H|H]] [[#I|I]] [[#J|J]] [[#K|K]] [[#L|L]] [[#M|M]] [[#N|N]] [[#O|O]] [[#P|P]] [[#Q|Q]] [[#R|R]] [[#S|S]] [[#T|T]] [[#U|U]] [[#V|V]] [[#W|W]] [[#X|X]] [[#Y|Y]] [[#Z|Z]]<br />
<br />
<!-- <br />
inserting a "Glossary Term" into the Glossary list<br />
;<span id="glossary_term">Glossary Term</span>: Definition of the term.<br />
<br />
inserting the term into the Gramps wiki manual<br />
[[Gramps_Glossary#glossary_term|Glossary Term]] <br />
<br />
for more information about WikiMedia sections, see:<br />
https://meta.wikimedia.org/w/index.php?title=Help:Section#id_with_space<br />
--><br />
==A==<br />
<br />
;<span id="active_person">Active Person</span>: (''core concept'') - The person designated as the momentary center of focus in the open Gramps database. The perspective of this person defines the context for actions and for displaying all the surrounding information. Changing this focus is done by [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Setting_the_Active_Person|navigating the Active Person]] selection to another person. <br />
<br />
;<span id="address">address</span>: (''[[#secondary_object|sec. obj.]]'') - The Gramps concept of an Address is a particular location with an associated time frame. Think of it as a mailing address. It is intended to represent where a person lived and when the person lived there. The Address consists:<br />
:* Date<br />
:* Street Address<br />
:* Locality<br />
:* City<br />
:* County<br />
:* State/Province<br />
:* Postal/Zip code<br />
:* Country<br />
:* Phone<br />
:Not to be confused with a [[Gramps_Glossary#place|Place]] which has a fixed position (its location). [[Why_residence_event_and_not_Address%3F|Use this with care.]] For genealogical research you can also use the residence event coupled with a [[Gramps_Glossary#place|Place]]. For mailing (email, postal), add an address to a [[Gramps_Glossary#person|Person]] or [[Gramps_Glossary#repository|Repository]].<br />
<br />
;<span id="aide">Aide</span>: (''[[#event_role|event role]]'') A term to refer to the role of an assistant.<br />
<br />
;<span id="anglicisation">anglicisation</span>:<br />
: process of making something English. If an immigrant (or their descendant) adopts a naturalized variation of their birth name, that [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Preferred_name_section|preferred alias]] can be added with an ''Also Known As'' [[Names_in_Gramps#Name_Types|name type]] in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Names|Names]] tab. All aliases can be categorized by type and surname variants may be [[Grouping_Surnames|grouped]] with the in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Name_Editor|Name Editor]]. <br />
<br />
;<span id="attribute">attribute</span>: (''[[#secondary_object|sec. obj.]]'') - Attributes are for something permanent, or at least somewhat permanent: eye color, blood type, etc. Usually you would have not more than one of each attribute type for a [[Gramps_Glossary#person|Person]]/[[Gramps_Glossary#family|Family]]/etc.<br />
<br />
==B==<br />
;<span id="books report">Books Report</span>:<br />
A [[Gramps_{{Version manual}}_Wiki_Manual_-_Reports|Reports menu]] feature of Gramps that allows the [[Gramps_{{Version manual}}_Wiki_Manual_-_Reports_-_part_3|design or generation of a repeatable custom genealogy ''Book'']]. A Book consists of an ordered collation of Gramps textual and graphical reports in a single document.<br />
<br />
;<span id="bride">Bride</span>: (''[[#event_role|event role]]'') A term to refer to the woman a marriage ceremony who will have the role of ''wife'' in the marriage. See also: ''mother''.<br />
<br />
==C==<br />
;<span id="celebrant">Celebrant</span>: (''[[#event_role|event role]]'') A term describing a role of the person who performs a rite, especially referring to a priest at the Eucharist. <br />
<br />
;[[File:Gramps-citation.png|right]]<span id="citation">Citation</span>: ({{icon|cite}} ''[[#primary_object|prim. obj.]]'') - Contains the information that enables you or others to locate your source document. An isolated [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_source_citations|Citation can be created]] without first creating separate [[#source|Source]] object. But, should the same source be referenced repeatedly in a Tree, a separate Source simplifies the Citation and eliminates redundant information that must be harmonized.<br />
<br />
;<span id="clergy">Clergy</span>: (''[[#event_role|event role]]'') A term applied to a religious person regardless of religion. For example, a monk or priest. See also: ''[[#celebrant|celebrant]]''.<br /><small>Religious terminology is often subject to dispute, see the [https://www.merriam-webster.com/dictionary/clergy Merriam-Webster] for an independent definition.</small><br />
<br />
;<span id="custom">''custom'' Types</span>: This indicates a user defined type, as opposed to types that came pre-defined in Gramps. When none of the pre-defined Types are suitable, add a new ''[[Gramps_Glossary#custom|custom]]'' Type by typewriting directly into the selector combo box. If the value doesn't precisely match any of the existing menu items, a new ''custom'' Type will be created when the {{man button|OK}} button is clicked. <br />Any added ''custom'' Type will remain available in that expanded menu... unless the Tree is exported & re-imported or via a [[Third-party_Addons|3rd party addon]] Utility like [[Types_Cleanup_Tool|Type Cleanup]].<br /><small>'''''custom'' Types''' can be defined for: Event Attributes, Family Attributes, media Attributes, Person Attributes, [[#event_role|Event Roles]], Event types, Family Relation types, Child Reference Types, Name Origin Types, Names Types, Note Types, Place Types, Repository Types, Source Attributes, source Media Types, URL Types.</small><br />
<br />
==D==<br />
;<span id="date">date</span>: (''[[#secondary_object|sec. obj.]]'') - Dates in Gramps are much more complex than just a month, day, and year. Dates are always in a [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Calendars|particular calendar]], can span a time frame, the [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_Quality|Date Quality]] can be approximate, and have support for many other subtleties specific to genealogy data. <br />
<br />
;<span id="dna">DNA</span>:<br />
# acronym: '''d'''eoxyribo'''n'''ucleic '''a'''cid<br />
# a [https://wikipedia.org/wiki/Nucleic_acid nucleic acid] that carries genetic information.<br />
<br />
;<span id="dtd">DTD</span>: <br />
:acronym: '''D'''ocument '''T'''ype '''D'''efinition. A document that defines the tagging structure which identifies the individual components of an [https://wikipedia.org/wiki/Standard_Generalized_Markup_Language SGML] or [[#xml|XML]] document.<br />
<br />
==E==<br />
;[[File:Gramps-event.png|right]]<span id="event">Event</span>: ({{icon|even}} ''[[#primary_object|prim. obj.]]'') - Contains the information related to an happening. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Adding an Event record]] provides the context of an interaction of the roles of People/Families, dates & places in activities.<br />An Event is a defining moment in a person's life. See [[events in Gramps|events]] for the use in genealogy, for predefined events in Gramps and suggested naming for common events.<br />
<br />
;<span id="event_role">event role</span>: The [[Gramps_Glossary#role|role]] a [[Gramps_Glossary#person|Person]] plays in an [[Gramps_Glossary#Event|Event]]. In Gramps, an Event can be linked to as many participants as desired. Each [[Gramps_Glossary#person|Person]] may participate in different roles but more than one Person might play the same role. The Event Role captures this. Some common Roles are pre-defined but the user can add other [[Gramps_Glossary#custom|custom]] Roles by just typing in an appropriate new Role Type in the [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]].<br />
:<small>Pre-defined Types of Event Role: [[Gramps_Glossary#aide|Aide]], [[Gramps_Glossary#bride|Bride]], [[Gramps_Glossary#celebrant|Celebrant]], [[Gramps_Glossary#clergy|Clergy]], [[Gramps_Glossary#family_role|Family]], [[Gramps_Glossary#groom|Groom]], [[Gramps_Glossary#informant|Informant]], [[Gramps_Glossary#primary|Primary]], [[Gramps_Glossary#witness|Witness]], [[Gramps_Glossary#unknown|Unknown]], ''[[Gramps_Glossary#custom|custom]]''</small><br />
<br />
;<span id="event_type">event type</span>: The general denominator to which an event belongs, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, a christian, civil, tibetan, ... marriage, are all denoted by the event type ''marriage''. See [[events in Gramps]] for an overview.<br />
<br />
==F==<br />
;<span id="family">Family</span>: <br />
#[[File:Gramps-family.png|right]]'''Family''' ({{icon|fami}} ''[[#primary_object|prim. obj.]]'') - Contains the information specific to relationships between people. This typically contains one or two parents and zero or more children.<br />The Family relationship is a core concept in Gramps. It depicts the basic relations between people. Commonly this will contain a father, a mother and some children, however, it can also contain only parts of this (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, two brothers, a mother and child). People can be part of several families (adoption, remarried, ...) <br />
#'''<span id="family_role">Family</span>''' (''[[#event_role|event role]]'') An event can be coupled to a family, denoting that the entire family was involved in the event. Typically the Marriage event will be coupled to a family with event role ''family''<br />
;<span id="filter">Filter</span>: <br />
:A [[Gramps_{{Version manual}}_Wiki_Manual_-_Filters|filter]] in a database hides (filters out) records, displaying only those records that match a specified criteria. In Gramps, the criteria can be simple or complex, with multiple levels. The basic Search is a simple filter that compares only a single attribute of a record. The Filter Gramplet compares several attributes simultaneously. The Custom Filter allows highly complex [[#rule|Rules]]-based compares with [[Example_filters|layers of intersection]] options for those rules. (Additional Rules are are available as addons.) Each increased capability slows performance of the interface.<br />
<br />
==G==<br />
;<span id="gedcom">[https://en.wikipedia.org/wiki/GEDCOM GEDCOM]</span>: <br />
# acronym: '''Ge'''nealogy '''D'''ata '''Com'''munication<br />
# a format for exchanging genealogical data. The <abbr title="an open standard is a standard that is publicly available and has various rights to use associated with it, and may also have various properties of how it was designed such as 'open process.' There is no single definition and interpretations vary with usage.">open</abbr> specification for the GEDCOM format was developed by The Church of Jesus Christ of Latter-day Saints (LDS Church) as an aid to genealogical research. The last standard release was version 5.5.1 in 2019. As an Open Standard, there are extensive and constantly changing incompatibilities between implementations and data loss when transferring GEDCOM formatted data between competing software tools is common. <br />
<br />
;<span id="gramps">Gramps</span>: [https://gramps-project.org/blog/features/ Gramps] is an open-source genealogy program, a free software project and community. <br />''The [https://gramps-project.org/introduction-WP/2006/04/looking-back-over-5-years/ reverse engineered] '''GRAMPS''' ('''G'''enealogical '''R'''esearch and '''A'''nalysis '''M'''anagement '''P'''rogramming '''S'''ystem) acronym was phased out in favor of '''Gramps''' as the official name of the software. All upper-case software names have become unfashionable.''<br />
<br />
;<span id="gramplet">Gramplet</span>: a [[Gramps_{{Version manual}}_Wiki_Manual_-_Gramplets#definition|Gramplet]] is a plug-in or addon widget that extends the functionality of Gramps by providing a dynamic view and interface to the Family Tree data. 3rd party Gramplets, reports, quick views, and tools are managed with the [[Gramps_{{Version manual}}_Wiki_Manual_-_Plugin_Manager|Plug-in Manager]]. <br />
:''See the [[Gramplets|Gramplets for Python Developers]] for independent development information.''<br />
<br />
;<span id="GUI"><span id="graphical user interface">Graphical User Interface (GUI)</span></span>: a visual way of indicating interactive features of a computer operating system or application/program. Gramps uses a "windows, icons, menus, pointer" ([https://wikipedia.org/wiki/WIMP_(computing) WIMP]) based GUI with [https://wikipedia.org/wiki/Post-WIMP post-WIMP] elements like hyperlinked redirection and custom interface objects.<br />
:The appearance and interaction may vary by conventions dictated by the [[Download|Operating System (OS)]], installation option (such as [[Portal:Translators|language localization support]] or [[{{man version}}_Addons|add-on/plug-in]]), [https://wikipedia.org/wiki/Theme_(computing) theme] (at the OS or [[Addon:Themes|internal]] levels), and/or [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Preferences|user preferences customization]].<br />
:The specific interface elements are identified by customary name, general appearance & behavior in the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|Visual Guide to Gramps]]. Expansion interface elements are described in the user documention for [[{{man version}}_Addons|each specific add-on]].<br />
<br />
;<span id="groom">Groom</span>: (''[[#event_role|event role]]'') A term to refer to the man at a marriage who will be referred to as ''husband'' after the marriage. See also: ''father''.<br />
<br />
;GUI: An acronym. ''see [[#graphical user interface|Graphical User Interface]]''.<br />
<br />
==H==<br />
[[File:Gramps Go-Home48x48 win.png|right]]<br />
;<span id="home_person">Home Person</span>: (''core concept'') - The persistently designated '''Home Person''' is the foundational [[#person|Person]] in the Tree (the currently open Gramps database). This Person is the central target of genealogical research and family references extend from this center. Ideally, every person, event and source in the Tree will (however directly or indirectly) relate back to the '''Home Person'''.<br />By default, the database reports describe everything else in contextual relation to this person. The [[Gramps_{{Version manual}}_Wiki_Manual_-_Main_Window#Status_Bar_and_Progress_Bar|Status Bar]], the [[Gramps_{{Version manual}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View]] called "[[Gramps_{{Version manual}}_Wiki_Manual_-_Reports_-_part_8#Relation_to_Home_Person|Relation to Home Person]]", and the Third party addon [[#gramplet|Gramplet]] called "[[Deep_Connections_Gramplet|Deep Connections]]" all describe different aspects of the relationship of the [[#active_person|Active Person]] to the '''Home Person'''.<br />You (or your client) are customarily designated ([[Gramps_{{Version manual}}_Wiki_Manual_-_Settings#Setting_Home_person|set]]) as the Home Person. And this ''Home'' designation serves as a persistent point of reference for the rest of the the Tree in Reports generally and for the Active Person in detail. But a different '''Home Person''' might be temporarily [[Gramps_{{Version manual}}_Wiki_Manual_-_Settings#Setting_Home_person|set]] when generating reports or when researching a complex biography or obituary. <Br />Fascinating tidbits often lure Gramps researchers into wandering off-course. When the [[#active_person|Active Person]] has become lost, the bearings can be instantly regained by navigating the [[#active_person|Active Person]] selection back to the '''Home Person'''.<br /><small>Navigate to '''Home Person''' - ''keyboard shortcut''</small> {{man key press|Alt|Home}} or press the toolbar <!-- broken icon {{icon|thom}}-->[[File:Gramps_Go-Home48x48 win.png|text-bottom|20px]]{{man button|Home}} button. <br />The custom filter rule for finding the '''Home Person''' is in a People category filter under the General filters and is named 'Default person.'<br />
<br />
==I==<br />
;<span id="informant">Informant</span>: (''[[#event_role|event role]]'') A term to refer to the [[#role|Role]] of Person who reports an [[#event|Event]].<br />
<br />
==J==<br />
==K==<br />
==L==<br />
==M==<br />
;<span id="matronymic">matronym</span>:<br />
:(''[[#name_origin|origin]] Name attrib.'') - personal name based on the name of one's mother<br />
<br />
;[[File:Gramps-media.png|right]]<span id="media">Media</span>: ({{icon|medi}} ''[[#primary_object|prim. obj.]]'') - Contains the information related to a media object. This includes images, documents, or any other type of related files.<br />
<br />
==N==<br />
;<span id="name origin">Name Origin</span>:<br />
:An optional attribute (characteristic) identifying how a name was derived for a [[#person|Person]]. Pre-defined items of the [[Names_in_Gramps#Origin_Attributes|origin selection menu]] include: inherited, patrilineal, matrilineal, given, taken, [[#patronymic|patronymic]], [[#matronymic|matronymic]], feudal, pseudonym, occupation.<br />''Available as a standard attribute of [[Names_in_Gramps|Names in Gramps]].'' <br />
<br />
;[[File:Gramps-notes.png|right]]<span id="note">Note</span>: ({{icon|note}} ''[[#primary_object|prim. obj.]]'') - Contains the information representing a textual brief record of facts and how it [[#reference|references]] other objects in the Tree. Notes can be added to any object at any any level of the Tree and are often used to detail the context of that record in the Tree.<br />
:Records in the [[Gramps_{{Version manual}}_Wiki_Manual_-_Categories#Notes_Category|Note Category]] contain free-form text with [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Note_markup_and_preformat_in_reports|basic formatting]] and [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Link_Editor|linking]] features. That text is created and modified using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Notes Editor]].<br />
<br />
==O==<br />
==P==<br />
;<span id="patronymic">patronym</span>:<br />
:(''[[#name_origin|origin]] Name attrib.'') - personal name based on the name of one's father.<br />
<br />
;[[File:Gramps-person.png|right]]<span id="person">Person</span>: ({{icon|peop}} ''[[#primary_object|prim. obj.]]'') - Contains the information specific to an individual person in the People category.<br />
<br />
;[[File:Gramps-place.png|right]]<span id="place">Place</span>: ({{icon|plac}} ''[[#primary_object|prim. obj.]]'') - The Gramps concept of a Place is a particular location independent of time. Over time, the same Place may have different address information due to changing borders and political situation. For example, Leningrad and St. Petersburg represent the same place, but with different names. Places in Gramps are stored in a hierarchy and are direct accessed via the [[Gramps_5.1_Wiki_Manual_-_Categories#Places_Category|Places category view]]. A Place consists of:<br />
:* Descriptive Title<br />
:* Name<br />
:* Type (such as country, state, county ...)<br />
:* Longitude/Latitude<br />
:* Code (such as a country code or postal code)<br />
:* A list of alternative names for the place<br />
:* A list of regions which enclose the place<br />
<br />
;<span id="posix">POSIX</span>: [https://wikipedia.org/wiki/Posix Portable Operating System Interface]: a family of OS standards specified by the [https://wikipedia.org/wiki/IEEE_Computer_Society IEEE] Computer Society for maintaining compatibility with variants of Unix (such as Linux) and other operating systems. Although the MacOS is "POSIX-certified", the term is used in this manual to generically refer to just the "Mostly POSIX-compliant" Linux and BSD distributions [[Download#Linux_and_BSD_distributions|with verified Gramps downloads]] and which use the POSIX-style [https://wikipedia.org/wiki/Filesystem_Hierarchy_Standard environment]. <br />
<br />
;<span id="primary_object">primary object</span>: Primary objects are the [[Using_database_API|data structures]] at the top level of a [[Gramps_Data_Model|hierarchical collection of records]]. Beside the main structure of data, they can contain a hierarchy of [[#secondary_object|secondary objects]], and can be referenced by other primary or secondary objects. In the Gramps database, primary objects and the secondary objects that they contain are stored as separate records. Each primary object type is stored in a separate table. See [[Using_database_API#Primary_Objects|Using database API, Primary Objects]] (see also ''[[#secondary_object|secondary object]]'')<br />
<br />
: The [[Using_database_API#Primary_Objects|primary objects]] are: <br />{{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]], {{icon|sour34}} [[#source|Source]], [[File:16x16-gramps-tag.png]] [[#tag|Tag]].<br />
<!--<br />
:{{icon|cite}} [[#citation|Citation]] - Contains the information related to a citation into a source.<br />
:{{icon|even}} [[#event|Event]] - Contains the information related to an event.<br />
:{{icon|fami}} [[#family|Family]] - Contains the information specific to relationships between people. This typically contains one or two parents and zero or more children.<br />
:{{icon|medi}} [[#media|Media]] - Contains the information related to a media object. This includes images, documents, or any other type of related files.<br />
:{{icon|note}} [[#note|Note]] - Contains the information related to a note.<br />
:{{icon|peop}} [[#person|Person]] - Contains the information specific to an individual person in the People category.<br />
:{{icon|plac}} [[#place|Place]] - Contains the information related to a specific place.<br />
:{{icon|repo}} [[#repository|Repository]] - Contains the information related to a repository.<br />
:{{icon|sour34}} [[#source|Source]] - Contains the information related to a source of information.<br />
:* [[#tag|Tag]] - Contains the information related to a Tags.<br />
<br />
--><br />
;<span id="primary">Primary role</span>: (''[[#event_role|event role]]'') A term to refer to the [[#role|role]] of the focal participant of an [[#event|Event]].<br />
<br />
;[[File:gramps-unlock.png|right]]<span id="private_tag">Private tag</span>: <br />
: The Private option tags information that should be redacted when sharing data or printing reports. Records are shown with: a locked padlock when private; and, an unlocked padlock when public. Clicking the padlock icon toggles between Public &amp; Private flags. This manual override supplements the automated [[Gramps_{{Version manual}}_Wiki_Manual_-_Probably_Alive|Probably Alive]] and custom [[Filter|Filter]] features which help Gramps to respect Personal Privacy. <br />
:Gramps is a single user database and omits the typical security features of a multi-user system. So even Private data will be accessible from within Gramps. However, generating reports and exporting data default to redacting information flagged as Private.<br />
<br />
==Q==<br />
==R==<br />
;<span id="reference">Reference</span>: the basic a system of linking relationships between objects in Gramps. When when an object is added in the Editor for record, a [[References#definition|Reference]] (link) is created in the object that was added. <br />
<br />
;[[File:Gramps-relation.png|right]]<span id="references_tab">References tab</span>: a system of linking between objects in Gramps. When objects of Gramps are linked, the [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#References|References tab]] lists the objects to link toward it.<br />
<br />
;[[File:Gramps-repository.png|right]]<span id="repository">Repository</span>: ({{icon|repo}} ''[[#primary_object|prim. obj.]]'') - Contains the information related to a physical or virtual structure where genealogical and family history sources are stored. Once a [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_repositories|Repository is added]] to a Gramps Tree, it can used to organize [[#source|Sources]].<br />
<br />
;<span id="role">role</span>: function performed or part played by a person (or other Gramps object) in a particular situation. When objects of Gramps are linked, a Reference is created where the Role disambiguates the relative nature of the reference. ''see [[#event_role|event role]]''<br />
<br />
;<span id="romanization">romanization</span>:<br />
: linguistic representation of a word in the Roman (Latin) alphabet<br />
<br />
==S==<br />
;<span id="secondary_object">secondary object</span>: Secondary objects are contained within other objects, and cannot be referenced directly. They can contain other secondary objects. Examples include: Name, Date and Address. See [[Using_database_API#Secondary_Objects|Using database API, Secondary Objects]] (see also ''[[#primary_object|primary object]]'')<br />
<br />
;[[File:Gramps-source.png|right]]<span id="source">Source</span>: ({{icon|sour34}} ''[[#primary_object|prim. obj.]]'') - A person ''(family, friend, another researcher)'', thing ''(book, magazine newspaper, census)'', or place ''(courthouse, church, library, genealogical/historical society)'' from which information comes, arises, or is obtained. After [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#New_Source_dialog|adding a Source]] to a Gramps Tree, the [[Sources#Definition|Source]] can be referenced in [[#citation|Citations]] and organized with [[#repository|Repositories]].<br />
<br />
==T==<br />
;[[File:gramps-tag.png|right]]<span id="tag">Tag</span>: ([[File:16x16-gramps-tag.png]] ''[[#primary_object|prim. obj.]]'') - A label that can be attached to a {{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]] or {{icon|sour34}} [[#source|Source]] for the purpose of easy identification and filtering.<br />A keyword or phrase used to group the collection to produce a report.<br />
<br />
;<span id="Typographical conventions">Typographical conventions</span>: The [[Gramps_{{man version}}_Wiki_Manual_-_Preface#Typographical_conventions|customary formatting]] having special (and possibly peculiar) meaning when used throughout the MediaWiki driven [[Gramps_{{man version}}_Wiki_Manual|Gramps manual]] and documentation. The different typeface accents, highlighting and enclosures indicate specific parts of the Gramps [[#graphical user interface|Graphical User Interface]] ([[#GUI|GUI]]) or prompt a User activity.<br />
<br />
==U==<br />
;<span id="unknown">Unknown</span>: (''[[#event_role|event role]]'') A placeholder for when the [[#role|role]] of a participant in an [[#event|Event]] has not yet been defined. Gramps sets an appropriate default Role as each new Event type is created. But when a new participant is associated with an existing Event via Share or drag'n'drop, the Role isn't as predictable. In such a case, an Unknown placeholder is inserted. <br />
:Any Unknown [[#event_role|Event Role]] type causes a variety of reporting problems. [[Rule_expansions#People_with_events_with_a_selected_role|Persons and Families with Unknown Roles]] should be found and the Roles manually replaced as soon as is practical.<br />
<br />
==V==<br />
;<span id="view">View</span>: ''([[Gramps_{{version manual}}_Wiki_Manual_-_Main_Window|graphical user interface terminology]])'' - a '''[[Gramps_{{Version manual}}_Wiki_Manual_-_Main_Window|View]]''' is a Gramps-specific name for the display layouts presenting information in a structured and predictable manner. Layouts are in table, outline or graphical formats; depending on the preferred way to represent how the data elements relate to on another. <br />Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of Categories, each with their own View. Each of the Category Views displays a smaller, more digestible portion of the total information that comprises a Genealogical Tree. <br />A Category View may have alternate modes (subcategories) of display layout. (e.g. Views with Table layouts might have flat listed or hierarchically grouped modes.) Each mode of a category can be independently configured.<br />View data may be further subdivided with tabbed pages of layouts.<br />
<br />
==W==<br />
;<span id="witness">Witness</span>:(''[[#event_role|event role]]'') The term that applies to the people asked to be present at an event so as to be able to testify to its having taken place<br />
<br />
==X==<br />
;<span id="xml">XML</span>: acronym: E'''x'''tensible '''M'''arkup '''L'''anguage. A schema used to define the expected structure of data in a text format. The system annotates a document in a way that data elements are syntactically distinguishable from identifying tags. A markup language defines a set of rules for encoding documents in a fault tolerant format that is both (marginally) human-readable and machine-readable.<br />
<br />
==Y==<br />
==Z==<br />
<br />
{{man tip|1=Wiki manual|2=Please enhance the {{man label|Wiki}} - create new glossary terms and add them to the wiki manual. Glossary term IDs are more memorable &amp; predictable if kept to all lower-case and use underscores (_) for spaces.<br />
<br />
inserting a "Glossary Term" into the Glossary list<br /><br />
<code><nowiki>;<span id="glossary_term">Glossary Term</span>: Definition of the term.</nowiki></code><br />
<br />
inserting the term into the Gramps wiki manual<br /><br />
<code><nowiki>[[Gramps_Glossary#glossary_term|Glossary Term]]</nowiki></code> <br />
<br />
for more information about WikiMedia sections, see:<br /><br />
<code>https://meta.wikimedia.org/w/index.php?title=Help:Section#id_with_space</code><br />
<br />
}}<br />
<br />
[[Category:Gramps terminology|*]]<br />
[[Category:Translators/Categories]]<br />
[[Category:Documentation]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Gramps_Glossary&diff=78638Gramps Glossary2020-05-28T09:07:08Z<p>GulliblePangolin: /* G */</p>
<hr />
<div>{{languages|Gramps_Glossary}}<br />
__NOTOC__<br />
This Glossary gives an overview of terms that appear in [https://gramps-project.org/blog/features/ Gramps], with a short description, and a link to relevant articles. <br />
<br />
For a glossary of genealogical terms, see [[Genealogy Glossary]].<br />For a list of pages dedicated to terms in this Glossary, see [[:Category:Gramps_terminology| Category:Terminology]]<br />
<br />
[[#A|A]] [[#B|B]] [[#C|C]] [[#D|D]] [[#E|E]] [[#F|F]] [[#G|G]] [[#H|H]] [[#I|I]] [[#J|J]] [[#K|K]] [[#L|L]] [[#M|M]] [[#N|N]] [[#O|O]] [[#P|P]] [[#Q|Q]] [[#R|R]] [[#S|S]] [[#T|T]] [[#U|U]] [[#V|V]] [[#W|W]] [[#X|X]] [[#Y|Y]] [[#Z|Z]]<br />
<br />
<!-- <br />
inserting a "Glossary Term" into the Glossary list<br />
;<span id="glossary_term">Glossary Term</span>: Definition of the term.<br />
<br />
inserting the term into the Gramps wiki manual<br />
[[Gramps_Glossary#glossary_term|Glossary Term]] <br />
<br />
for more information about WikiMedia sections, see:<br />
https://meta.wikimedia.org/w/index.php?title=Help:Section#id_with_space<br />
--><br />
==A==<br />
<br />
;<span id="active_person">Active Person</span>: (''core concept'') - The person designated as the momentary center of focus in the open Gramps database. The perspective of this person defines the context for actions and for displaying all the surrounding information. Changing this focus is done by [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Setting_the_Active_Person|navigating the Active Person]] selection to another person. <br />
<br />
;<span id="address">address</span>: (''[[#secondary_object|sec. obj.]]'') - The Gramps concept of an Address is a particular location with an associated time frame. Think of it as a mailing address. It is intended to represent where a person lived and when the person lived there. The Address consists:<br />
:* Date<br />
:* Street Address<br />
:* Locality<br />
:* City<br />
:* County<br />
:* State/Province<br />
:* Postal/Zip code<br />
:* Country<br />
:* Phone<br />
:Not to be confused with a [[Gramps_Glossary#place|Place]] which has a fixed position (its location). [[Why_residence_event_and_not_Address%3F|Use this with care.]] For genealogical research you can also use the residence event coupled with a [[Gramps_Glossary#place|Place]]. For mailing (email, postal), add an address to a [[Gramps_Glossary#person|Person]] or [[Gramps_Glossary#repository|Repository]].<br />
<br />
;<span id="aide">Aide</span>: (''[[#event_role|event role]]'') A term to refer to the role of an assistant.<br />
<br />
;<span id="anglicisation">anglicisation</span>:<br />
: process of making something English. If an immigrant (or their descendant) adopts a naturalized variation of their birth name, that [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Preferred_name_section|preferred alias]] can be added with an ''Also Known As'' [[Names_in_Gramps#Name_Types|name type]] in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Names|Names]] tab. All aliases can be categorized by type and surname variants may be [[Grouping_Surnames|grouped]] with the in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Name_Editor|Name Editor]]. <br />
<br />
;<span id="attribute">attribute</span>: (''[[#secondary_object|sec. obj.]]'') - Attributes are for something permanent, or at least somewhat permanent: eye color, blood type, etc. Usually you would have not more than one of each attribute type for a [[Gramps_Glossary#person|Person]]/[[Gramps_Glossary#family|Family]]/etc.<br />
<br />
==B==<br />
;<span id="books report">Books Report</span>:<br />
A [[Gramps_{{Version manual}}_Wiki_Manual_-_Reports|Reports menu]] feature of Gramps that allows the [[Gramps_{{Version manual}}_Wiki_Manual_-_Reports_-_part_3|design or generation of a repeatable custom genealogy ''Book'']]. A Book consists of an ordered collation of Gramps textual and graphical reports in a single document.<br />
<br />
;<span id="bride">Bride</span>: (''[[#event_role|event role]]'') A term to refer to the woman a marriage ceremony who will have the role of ''wife'' in the marriage. See also: ''mother''.<br />
<br />
==C==<br />
;<span id="celebrant">Celebrant</span>: (''[[#event_role|event role]]'') A term describing a role of the person who performs a rite, especially referring to a priest at the Eucharist. <br />
<br />
;[[File:Gramps-citation.png|right]]<span id="citation">Citation</span>: ({{icon|cite}} ''[[#primary_object|prim. obj.]]'') - Contains the information that enables you or others to locate your source document. An isolated [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_source_citations|Citation can be created]] without first creating separate [[#source|Source]] object. But, should the same source be referenced repeatedly in a Tree, a separate Source simplifies the Citation and eliminates redundant information that must be harmonized.<br />
<br />
;<span id="clergy">Clergy</span>: (''[[#event_role|event role]]'') A term applied to a religious person regardless of religion. For example, a monk or priest. See also: ''[[#celebrant|celebrant]]''.<br /><small>Religious terminology is often subject to dispute, see the [https://www.merriam-webster.com/dictionary/clergy Merriam-Webster] for an independent definition.</small><br />
<br />
;<span id="custom">''custom'' Types</span>: This indicates a user defined type, as opposed to types that came pre-defined in Gramps. When none of the pre-defined Types are suitable, add a new ''[[Gramps_Glossary#custom|custom]]'' Type by typewriting directly into the selector combo box. If the value doesn't precisely match any of the existing menu items, a new ''custom'' Type will be created when the {{man button|OK}} button is clicked. <br />Any added ''custom'' Type will remain available in that expanded menu... unless the Tree is exported & re-imported or via a [[Third-party_Addons|3rd party addon]] Utility like [[Types_Cleanup_Tool|Type Cleanup]].<br /><small>'''''custom'' Types''' can be defined for: Event Attributes, Family Attributes, media Attributes, Person Attributes, [[#event_role|Event Roles]], Event types, Family Relation types, Child Reference Types, Name Origin Types, Names Types, Note Types, Place Types, Repository Types, Source Attributes, source Media Types, URL Types.</small><br />
<br />
==D==<br />
;<span id="date">date</span>: (''[[#secondary_object|sec. obj.]]'') - Dates in Gramps are much more complex than just a month, day, and year. Dates are always in a [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Calendars|particular calendar]], can span a time frame, the [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_Quality|Date Quality]] can be approximate, and have support for many other subtleties specific to genealogy data. <br />
<br />
;<span id="dna">DNA</span>:<br />
# acronym: '''d'''eoxyribo'''n'''ucleic '''a'''cid<br />
# a [https://wikipedia.org/wiki/Nucleic_acid nucleic acid] that carries genetic information.<br />
<br />
;<span id="dtd">DTD</span>: <br />
:acronym: '''D'''ocument '''T'''ype '''D'''efinition. A document that defines the tagging structure which identifies the individual components of an [https://wikipedia.org/wiki/Standard_Generalized_Markup_Language SGML] or [[#xml|XML]] document.<br />
<br />
==E==<br />
;[[File:Gramps-event.png|right]]<span id="event">Event</span>: ({{icon|even}} ''[[#primary_object|prim. obj.]]'') - Contains the information related to an happening. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Adding an Event record]] provides the context of an interaction of the roles of People/Families, dates & places in activities.<br />An Event is a defining moment in a person's life. See [[events in Gramps|events]] for the use in genealogy, for predefined events in Gramps and suggested naming for common events.<br />
<br />
;<span id="event_role">event role</span>: The [[Gramps_Glossary#role|role]] a [[Gramps_Glossary#person|Person]] plays in an [[Gramps_Glossary#Event|Event]]. In Gramps, an Event can be linked to as many participants as desired. Each [[Gramps_Glossary#person|Person]] may participate in different roles but more than one Person might play the same role. The Event Role captures this. Some common Roles are pre-defined but the user can add other [[Gramps_Glossary#custom|custom]] Roles by just typing in an appropriate new Role Type in the [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]].<br />
:<small>Pre-defined Types of Event Role: [[Gramps_Glossary#aide|Aide]], [[Gramps_Glossary#bride|Bride]], [[Gramps_Glossary#celebrant|Celebrant]], [[Gramps_Glossary#clergy|Clergy]], [[Gramps_Glossary#family_role|Family]], [[Gramps_Glossary#groom|Groom]], [[Gramps_Glossary#informant|Informant]], [[Gramps_Glossary#primary|Primary]], [[Gramps_Glossary#witness|Witness]], [[Gramps_Glossary#unknown|Unknown]], ''[[Gramps_Glossary#custom|custom]]''</small><br />
<br />
;<span id="event_type">event type</span>: The general denominator to which an event belongs, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, a christian, civil, tibetan, ... marriage, are all denoted by the event type ''marriage''. See [[events in Gramps]] for an overview.<br />
<br />
==F==<br />
;<span id="family">Family</span>: <br />
#[[File:Gramps-family.png|right]]'''Family''' ({{icon|fami}} ''[[#primary_object|prim. obj.]]'') - Contains the information specific to relationships between people. This typically contains one or two parents and zero or more children.<br />The Family relationship is a core concept in Gramps. It depicts the basic relations between people. Commonly this will contain a father, a mother and some children, however, it can also contain only parts of this (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, two brothers, a mother and child). People can be part of several families (adoption, remarried, ...) <br />
#'''<span id="family_role">Family</span>''' (''[[#event_role|event role]]'') An event can be coupled to a family, denoting that the entire family was involved in the event. Typically the Marriage event will be coupled to a family with event role ''family''<br />
;<span id="filter">Filter</span>: <br />
:A [[Gramps_{{Version manual}}_Wiki_Manual_-_Filters|filter]] in a database hides (filters out) records, displaying only those records that match a specified criteria. In Gramps, the criteria can be simple or complex, with multiple levels. The basic Search is a simple filter that compares only a single attribute of a record. The Filter Gramplet compares several attributes simultaneously. The Custom Filter allows highly complex [[#rule|Rules]]-based compares with [[Example_filters|layers of intersection]] options for those rules. (Additional Rules are are available as addons.) Each increased capability slows performance of the interface.<br />
<br />
==G==<br />
;<span id="gedcom">[https://en.wikipedia.org/wiki/GEDCOM GEDCOM]</span>: <br />
# acronym: '''Ge'''nealogy '''D'''ata '''Com'''munication<br />
# a format for exchanging genealogical data. The <abbr title="an open standard is a standard that is publicly available and has various rights to use associated with it, and may also have various properties of how it was designed such as 'open process.' There is no single definition and interpretations vary with usage.">open</abbr> specification for the GEDCOM format was developed by The Church of Jesus Christ of Latter-day Saints (LDS Church) as an aid to genealogical research. The last standard release was version 5.5.1 in 2019. As an Open Standard, there are extensive and constantly changing incompatibilities between implementations and data loss when transferring GEDCOM formatted data between competing software tools is common. <br />
<br />
;<span id="gramps">Gramps</span>: [https://gramps-project.org/blog/features/ Gramps] is an open-source genealogy program, a free software project and community. <br />''The [https://gramps-project.org/introduction-WP/2006/04/looking-back-over-5-years/ reverse engineered] '''GRAMPS''' ('''G'''enealogical '''R'''esearch and '''A'''nalysis '''M'''anagement '''P'''rogramming '''S'''ystem) acronym is being phased out in favor of '''Gramps''' as the official name of the software. All upper-case software names have become unfashionable.''<br />
<br />
;<span id="gramplet">Gramplet</span>: a [[Gramps_{{Version manual}}_Wiki_Manual_-_Gramplets#definition|Gramplet]] is a plug-in or addon widget that extends the functionality of Gramps by providing a dynamic view and interface to the Family Tree data. 3rd party Gramplets, reports, quick views, and tools are managed with the [[Gramps_{{Version manual}}_Wiki_Manual_-_Plugin_Manager|Plug-in Manager]]. <br />
:''See the [[Gramplets|Gramplets for Python Developers]] for independent development information.''<br />
<br />
;<span id="GUI"><span id="graphical user interface">Graphical User Interface (GUI)</span></span>: a visual way of indicating interactive features of a computer operating system or application/program. Gramps uses a "windows, icons, menus, pointer" ([https://wikipedia.org/wiki/WIMP_(computing) WIMP]) based GUI with [https://wikipedia.org/wiki/Post-WIMP post-WIMP] elements like hyperlinked redirection and custom interface objects.<br />
:The appearance and interaction may vary by conventions dictated by the [[Download|Operating System (OS)]], installation option (such as [[Portal:Translators|language localization support]] or [[{{man version}}_Addons|add-on/plug-in]]), [https://wikipedia.org/wiki/Theme_(computing) theme] (at the OS or [[Addon:Themes|internal]] levels), and/or [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Preferences|user preferences customization]].<br />
:The specific interface elements are identified by customary name, general appearance & behavior in the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|Visual Guide to Gramps]]. Expansion interface elements are described in the user documention for [[{{man version}}_Addons|each specific add-on]].<br />
<br />
;<span id="groom">Groom</span>: (''[[#event_role|event role]]'') A term to refer to the man at a marriage who will be referred to as ''husband'' after the marriage. See also: ''father''.<br />
<br />
;GUI: An acronym. ''see [[#graphical user interface|Graphical User Interface]]''.<br />
<br />
==H==<br />
[[File:Gramps Go-Home48x48 win.png|right]]<br />
;<span id="home_person">Home Person</span>: (''core concept'') - The persistently designated '''Home Person''' is the foundational [[#person|Person]] in the Tree (the currently open Gramps database). This Person is the central target of genealogical research and family references extend from this center. Ideally, every person, event and source in the Tree will (however directly or indirectly) relate back to the '''Home Person'''.<br />By default, the database reports describe everything else in contextual relation to this person. The [[Gramps_{{Version manual}}_Wiki_Manual_-_Main_Window#Status_Bar_and_Progress_Bar|Status Bar]], the [[Gramps_{{Version manual}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View]] called "[[Gramps_{{Version manual}}_Wiki_Manual_-_Reports_-_part_8#Relation_to_Home_Person|Relation to Home Person]]", and the Third party addon [[#gramplet|Gramplet]] called "[[Deep_Connections_Gramplet|Deep Connections]]" all describe different aspects of the relationship of the [[#active_person|Active Person]] to the '''Home Person'''.<br />You (or your client) are customarily designated ([[Gramps_{{Version manual}}_Wiki_Manual_-_Settings#Setting_Home_person|set]]) as the Home Person. And this ''Home'' designation serves as a persistent point of reference for the rest of the the Tree in Reports generally and for the Active Person in detail. But a different '''Home Person''' might be temporarily [[Gramps_{{Version manual}}_Wiki_Manual_-_Settings#Setting_Home_person|set]] when generating reports or when researching a complex biography or obituary. <Br />Fascinating tidbits often lure Gramps researchers into wandering off-course. When the [[#active_person|Active Person]] has become lost, the bearings can be instantly regained by navigating the [[#active_person|Active Person]] selection back to the '''Home Person'''.<br /><small>Navigate to '''Home Person''' - ''keyboard shortcut''</small> {{man key press|Alt|Home}} or press the toolbar <!-- broken icon {{icon|thom}}-->[[File:Gramps_Go-Home48x48 win.png|text-bottom|20px]]{{man button|Home}} button. <br />The custom filter rule for finding the '''Home Person''' is in a People category filter under the General filters and is named 'Default person.'<br />
<br />
==I==<br />
;<span id="informant">Informant</span>: (''[[#event_role|event role]]'') A term to refer to the [[#role|Role]] of Person who reports an [[#event|Event]].<br />
<br />
==J==<br />
==K==<br />
==L==<br />
==M==<br />
;<span id="matronymic">matronym</span>:<br />
:(''[[#name_origin|origin]] Name attrib.'') - personal name based on the name of one's mother<br />
<br />
;[[File:Gramps-media.png|right]]<span id="media">Media</span>: ({{icon|medi}} ''[[#primary_object|prim. obj.]]'') - Contains the information related to a media object. This includes images, documents, or any other type of related files.<br />
<br />
==N==<br />
;<span id="name origin">Name Origin</span>:<br />
:An optional attribute (characteristic) identifying how a name was derived for a [[#person|Person]]. Pre-defined items of the [[Names_in_Gramps#Origin_Attributes|origin selection menu]] include: inherited, patrilineal, matrilineal, given, taken, [[#patronymic|patronymic]], [[#matronymic|matronymic]], feudal, pseudonym, occupation.<br />''Available as a standard attribute of [[Names_in_Gramps|Names in Gramps]].'' <br />
<br />
;[[File:Gramps-notes.png|right]]<span id="note">Note</span>: ({{icon|note}} ''[[#primary_object|prim. obj.]]'') - Contains the information representing a textual brief record of facts and how it [[#reference|references]] other objects in the Tree. Notes can be added to any object at any any level of the Tree and are often used to detail the context of that record in the Tree.<br />
:Records in the [[Gramps_{{Version manual}}_Wiki_Manual_-_Categories#Notes_Category|Note Category]] contain free-form text with [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Note_markup_and_preformat_in_reports|basic formatting]] and [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Link_Editor|linking]] features. That text is created and modified using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Notes Editor]].<br />
<br />
==O==<br />
==P==<br />
;<span id="patronymic">patronym</span>:<br />
:(''[[#name_origin|origin]] Name attrib.'') - personal name based on the name of one's father.<br />
<br />
;[[File:Gramps-person.png|right]]<span id="person">Person</span>: ({{icon|peop}} ''[[#primary_object|prim. obj.]]'') - Contains the information specific to an individual person in the People category.<br />
<br />
;[[File:Gramps-place.png|right]]<span id="place">Place</span>: ({{icon|plac}} ''[[#primary_object|prim. obj.]]'') - The Gramps concept of a Place is a particular location independent of time. Over time, the same Place may have different address information due to changing borders and political situation. For example, Leningrad and St. Petersburg represent the same place, but with different names. Places in Gramps are stored in a hierarchy and are direct accessed via the [[Gramps_5.1_Wiki_Manual_-_Categories#Places_Category|Places category view]]. A Place consists of:<br />
:* Descriptive Title<br />
:* Name<br />
:* Type (such as country, state, county ...)<br />
:* Longitude/Latitude<br />
:* Code (such as a country code or postal code)<br />
:* A list of alternative names for the place<br />
:* A list of regions which enclose the place<br />
<br />
;<span id="posix">POSIX</span>: [https://wikipedia.org/wiki/Posix Portable Operating System Interface]: a family of OS standards specified by the [https://wikipedia.org/wiki/IEEE_Computer_Society IEEE] Computer Society for maintaining compatibility with variants of Unix (such as Linux) and other operating systems. Although the MacOS is "POSIX-certified", the term is used in this manual to generically refer to just the "Mostly POSIX-compliant" Linux and BSD distributions [[Download#Linux_and_BSD_distributions|with verified Gramps downloads]] and which use the POSIX-style [https://wikipedia.org/wiki/Filesystem_Hierarchy_Standard environment]. <br />
<br />
;<span id="primary_object">primary object</span>: Primary objects are the [[Using_database_API|data structures]] at the top level of a [[Gramps_Data_Model|hierarchical collection of records]]. Beside the main structure of data, they can contain a hierarchy of [[#secondary_object|secondary objects]], and can be referenced by other primary or secondary objects. In the Gramps database, primary objects and the secondary objects that they contain are stored as separate records. Each primary object type is stored in a separate table. See [[Using_database_API#Primary_Objects|Using database API, Primary Objects]] (see also ''[[#secondary_object|secondary object]]'')<br />
<br />
: The [[Using_database_API#Primary_Objects|primary objects]] are: <br />{{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]], {{icon|sour34}} [[#source|Source]], [[File:16x16-gramps-tag.png]] [[#tag|Tag]].<br />
<!--<br />
:{{icon|cite}} [[#citation|Citation]] - Contains the information related to a citation into a source.<br />
:{{icon|even}} [[#event|Event]] - Contains the information related to an event.<br />
:{{icon|fami}} [[#family|Family]] - Contains the information specific to relationships between people. This typically contains one or two parents and zero or more children.<br />
:{{icon|medi}} [[#media|Media]] - Contains the information related to a media object. This includes images, documents, or any other type of related files.<br />
:{{icon|note}} [[#note|Note]] - Contains the information related to a note.<br />
:{{icon|peop}} [[#person|Person]] - Contains the information specific to an individual person in the People category.<br />
:{{icon|plac}} [[#place|Place]] - Contains the information related to a specific place.<br />
:{{icon|repo}} [[#repository|Repository]] - Contains the information related to a repository.<br />
:{{icon|sour34}} [[#source|Source]] - Contains the information related to a source of information.<br />
:* [[#tag|Tag]] - Contains the information related to a Tags.<br />
<br />
--><br />
;<span id="primary">Primary role</span>: (''[[#event_role|event role]]'') A term to refer to the [[#role|role]] of the focal participant of an [[#event|Event]].<br />
<br />
;[[File:gramps-unlock.png|right]]<span id="private_tag">Private tag</span>: <br />
: The Private option tags information that should be redacted when sharing data or printing reports. Records are shown with: a locked padlock when private; and, an unlocked padlock when public. Clicking the padlock icon toggles between Public &amp; Private flags. This manual override supplements the automated [[Gramps_{{Version manual}}_Wiki_Manual_-_Probably_Alive|Probably Alive]] and custom [[Filter|Filter]] features which help Gramps to respect Personal Privacy. <br />
:Gramps is a single user database and omits the typical security features of a multi-user system. So even Private data will be accessible from within Gramps. However, generating reports and exporting data default to redacting information flagged as Private.<br />
<br />
==Q==<br />
==R==<br />
;<span id="reference">Reference</span>: the basic a system of linking relationships between objects in Gramps. When when an object is added in the Editor for record, a [[References#definition|Reference]] (link) is created in the object that was added. <br />
<br />
;[[File:Gramps-relation.png|right]]<span id="references_tab">References tab</span>: a system of linking between objects in Gramps. When objects of Gramps are linked, the [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#References|References tab]] lists the objects to link toward it.<br />
<br />
;[[File:Gramps-repository.png|right]]<span id="repository">Repository</span>: ({{icon|repo}} ''[[#primary_object|prim. obj.]]'') - Contains the information related to a physical or virtual structure where genealogical and family history sources are stored. Once a [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_repositories|Repository is added]] to a Gramps Tree, it can used to organize [[#source|Sources]].<br />
<br />
;<span id="role">role</span>: function performed or part played by a person (or other Gramps object) in a particular situation. When objects of Gramps are linked, a Reference is created where the Role disambiguates the relative nature of the reference. ''see [[#event_role|event role]]''<br />
<br />
;<span id="romanization">romanization</span>:<br />
: linguistic representation of a word in the Roman (Latin) alphabet<br />
<br />
==S==<br />
;<span id="secondary_object">secondary object</span>: Secondary objects are contained within other objects, and cannot be referenced directly. They can contain other secondary objects. Examples include: Name, Date and Address. See [[Using_database_API#Secondary_Objects|Using database API, Secondary Objects]] (see also ''[[#primary_object|primary object]]'')<br />
<br />
;[[File:Gramps-source.png|right]]<span id="source">Source</span>: ({{icon|sour34}} ''[[#primary_object|prim. obj.]]'') - A person ''(family, friend, another researcher)'', thing ''(book, magazine newspaper, census)'', or place ''(courthouse, church, library, genealogical/historical society)'' from which information comes, arises, or is obtained. After [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#New_Source_dialog|adding a Source]] to a Gramps Tree, the [[Sources#Definition|Source]] can be referenced in [[#citation|Citations]] and organized with [[#repository|Repositories]].<br />
<br />
==T==<br />
;[[File:gramps-tag.png|right]]<span id="tag">Tag</span>: ([[File:16x16-gramps-tag.png]] ''[[#primary_object|prim. obj.]]'') - A label that can be attached to a {{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]] or {{icon|sour34}} [[#source|Source]] for the purpose of easy identification and filtering.<br />A keyword or phrase used to group the collection to produce a report.<br />
<br />
;<span id="Typographical conventions">Typographical conventions</span>: The [[Gramps_{{man version}}_Wiki_Manual_-_Preface#Typographical_conventions|customary formatting]] having special (and possibly peculiar) meaning when used throughout the MediaWiki driven [[Gramps_{{man version}}_Wiki_Manual|Gramps manual]] and documentation. The different typeface accents, highlighting and enclosures indicate specific parts of the Gramps [[#graphical user interface|Graphical User Interface]] ([[#GUI|GUI]]) or prompt a User activity.<br />
<br />
==U==<br />
;<span id="unknown">Unknown</span>: (''[[#event_role|event role]]'') A placeholder for when the [[#role|role]] of a participant in an [[#event|Event]] has not yet been defined. Gramps sets an appropriate default Role as each new Event type is created. But when a new participant is associated with an existing Event via Share or drag'n'drop, the Role isn't as predictable. In such a case, an Unknown placeholder is inserted. <br />
:Any Unknown [[#event_role|Event Role]] type causes a variety of reporting problems. [[Rule_expansions#People_with_events_with_a_selected_role|Persons and Families with Unknown Roles]] should be found and the Roles manually replaced as soon as is practical.<br />
<br />
==V==<br />
;<span id="view">View</span>: ''([[Gramps_{{version manual}}_Wiki_Manual_-_Main_Window|graphical user interface terminology]])'' - a '''[[Gramps_{{Version manual}}_Wiki_Manual_-_Main_Window|View]]''' is a Gramps-specific name for the display layouts presenting information in a structured and predictable manner. Layouts are in table, outline or graphical formats; depending on the preferred way to represent how the data elements relate to on another. <br />Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of Categories, each with their own View. Each of the Category Views displays a smaller, more digestible portion of the total information that comprises a Genealogical Tree. <br />A Category View may have alternate modes (subcategories) of display layout. (e.g. Views with Table layouts might have flat listed or hierarchically grouped modes.) Each mode of a category can be independently configured.<br />View data may be further subdivided with tabbed pages of layouts.<br />
<br />
==W==<br />
;<span id="witness">Witness</span>:(''[[#event_role|event role]]'') The term that applies to the people asked to be present at an event so as to be able to testify to its having taken place<br />
<br />
==X==<br />
;<span id="xml">XML</span>: acronym: E'''x'''tensible '''M'''arkup '''L'''anguage. A schema used to define the expected structure of data in a text format. The system annotates a document in a way that data elements are syntactically distinguishable from identifying tags. A markup language defines a set of rules for encoding documents in a fault tolerant format that is both (marginally) human-readable and machine-readable.<br />
<br />
==Y==<br />
==Z==<br />
<br />
{{man tip|1=Wiki manual|2=Please enhance the {{man label|Wiki}} - create new glossary terms and add them to the wiki manual. Glossary term IDs are more memorable &amp; predictable if kept to all lower-case and use underscores (_) for spaces.<br />
<br />
inserting a "Glossary Term" into the Glossary list<br /><br />
<code><nowiki>;<span id="glossary_term">Glossary Term</span>: Definition of the term.</nowiki></code><br />
<br />
inserting the term into the Gramps wiki manual<br /><br />
<code><nowiki>[[Gramps_Glossary#glossary_term|Glossary Term]]</nowiki></code> <br />
<br />
for more information about WikiMedia sections, see:<br /><br />
<code>https://meta.wikimedia.org/w/index.php?title=Help:Section#id_with_space</code><br />
<br />
}}<br />
<br />
[[Category:Gramps terminology|*]]<br />
[[Category:Translators/Categories]]<br />
[[Category:Documentation]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Custom_Event_Types&diff=78637Custom Event Types2020-05-28T09:04:03Z<p>GulliblePangolin: </p>
<hr />
<div>{{man note|This page lists custom event types.|See also [[Events in Gramps]]}}<br />
<br />
These are example event types that are currently used by some users. They are not necessarily recommended, but may be a useful starting point.<br />
<br />
== Life Events ==<br />
<br />
* Origin<br />
* Stillbirth<br />
* Circumcision<br />
* Separation<br />
* Name Change<br />
* Transition (Sex change)<br />
<br />
== Legal ==<br />
<br />
* Bankruptcy<br />
* Liquidation<br />
* Civil Lawsuit<br />
* Civil Appeal<br />
* Criminal<br />
* Indictment<br />
* Court Case<br />
* Conviction<br />
* Criminal Appeal<br />
* Declaration of Intention (First Papers in the naturalization process in the US)<br />
* Trial<br />
* Inquest<br />
<br />
== Medical ==<br />
<br />
* Injury<br />
* Illness<br />
<br />
== Military ==<br />
<br />
* Battle<br />
* [[Draft_lottery|Draft Registration]] (US only?)<br />
* Partisan service<br />
* Commendation<br />
* Disciplinary Action<br />
* Desertion<br />
* Escape<br />
* Evacuation<br />
* Internment<br />
<br />
== Political ==<br />
<br />
* Appointed<br />
<br />
== Travel ==<br />
<br />
Travel other than Immigration and Emigration.<br />
<br />
* Arrival<br />
* Departure<br />
* Travel<br />
* Port of Call<br />
* Expedition<br />
<br />
== Other ==<br />
<br />
* Apprenticeship<br />
* Voluntary Work<br />
* Award (Prize, honour, decoration etc...)<br />
* Publication (Publication of a book, article, academic paper etc...)<br />
* Yahrzeit (Hebrew calendar anniversary of death)<br />
* Family Gathering<br />
* Wedding Dinner<br />
* Membership (of a club, society, organisation etc...)<br />
<br />
=See also=<br />
* [[Events in Gramps]]<br />
* [[Types_Cleanup_Tool|Types Cleanup Tool]] (third party add-on)<br />
<br />
[[Category:Events]]<br />
[[Category:Gramps terminology]]<br />
[[Category:Translators/Categories]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Custom_Event_Types&diff=78636Custom Event Types2020-05-28T09:03:42Z<p>GulliblePangolin: </p>
<hr />
<div>{{man note|This page lists custom event types.}}<br />
<br />
These are example event types that are currently used by some users. They are not necessarily recommended, but may be a useful starting point.<br />
<br />
== Life Events ==<br />
<br />
* Origin<br />
* Stillbirth<br />
* Circumcision<br />
* Separation<br />
* Name Change<br />
* Transition (Sex change)<br />
<br />
== Legal ==<br />
<br />
* Bankruptcy<br />
* Liquidation<br />
* Civil Lawsuit<br />
* Civil Appeal<br />
* Criminal<br />
* Indictment<br />
* Court Case<br />
* Conviction<br />
* Criminal Appeal<br />
* Declaration of Intention (First Papers in the naturalization process in the US)<br />
* Trial<br />
* Inquest<br />
<br />
== Medical ==<br />
<br />
* Injury<br />
* Illness<br />
<br />
== Military ==<br />
<br />
* Battle<br />
* [[Draft_lottery|Draft Registration]] (US only?)<br />
* Partisan service<br />
* Commendation<br />
* Disciplinary Action<br />
* Desertion<br />
* Escape<br />
* Evacuation<br />
* Internment<br />
<br />
== Political ==<br />
<br />
* Appointed<br />
<br />
== Travel ==<br />
<br />
Travel other than Immigration and Emigration.<br />
<br />
* Arrival<br />
* Departure<br />
* Travel<br />
* Port of Call<br />
* Expedition<br />
<br />
== Other ==<br />
<br />
* Apprenticeship<br />
* Voluntary Work<br />
* Award (Prize, honour, decoration etc...)<br />
* Publication (Publication of a book, article, academic paper etc...)<br />
* Yahrzeit (Hebrew calendar anniversary of death)<br />
* Family Gathering<br />
* Wedding Dinner<br />
* Membership (of a club, society, organisation etc...)<br />
<br />
=See also=<br />
* [[Events in Gramps]]<br />
* [[Types_Cleanup_Tool|Types Cleanup Tool]] (third party add-on)<br />
<br />
[[Category:Events]]<br />
[[Category:Gramps terminology]]<br />
[[Category:Translators/Categories]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Custom_Event_Types&diff=78635Custom Event Types2020-05-28T09:03:02Z<p>GulliblePangolin: /* See also */</p>
<hr />
<div>{{man note|This page lists custom event types.}}<br />
<br />
These are example event types that are currently used by some users. They are not necessarily recommended, but may be a useful starting point.<br />
<br />
== Life Events ==<br />
<br />
* Origin<br />
* Stillbirth<br />
* Circumcision<br />
* Separation<br />
* Name Change<br />
* Transition (Sex change)<br />
<br />
== Legal ==<br />
<br />
* Bankruptcy<br />
* Liquidation<br />
* Civil Lawsuit<br />
* Civil Appeal<br />
* Criminal<br />
* Indictment<br />
* Court Case<br />
* Conviction<br />
* Criminal Appeal<br />
* Declaration of Intention (First Papers in the naturalization process in the US)<br />
* Trial<br />
* Inquest<br />
<br />
== Medical ==<br />
<br />
* Injury<br />
* Illness<br />
<br />
== Military ==<br />
<br />
* Battle<br />
* [[Draft_lottery|Draft Registration]] (US only?)<br />
* Partisan service<br />
* Commendation<br />
* Disciplinary Action<br />
* Desertion<br />
* Escape<br />
* Evacuation<br />
* Internment<br />
<br />
== Political ==<br />
<br />
* Appointed<br />
<br />
== Travel ==<br />
<br />
Travel other than Immigration and Emigration.<br />
<br />
* Arrival<br />
* Departure<br />
* Travel<br />
* Port of Call<br />
* Expedition<br />
<br />
== Other ==<br />
<br />
* Apprenticeship<br />
* Voluntary Work<br />
* Award (Prize, honour, decoration etc...)<br />
* Publication (Publication of a book, article, academic paper etc...)<br />
* Yahrzeit (Hebrew calendar anniversary of death)<br />
* Family Gathering<br />
* Wedding Dinner<br />
* Membership (of a club, society, organisation etc...)<br />
<br />
=See also=<br />
* [[Types_Cleanup_Tool|Types Cleanup Tool]] (third party add-on)<br />
<br />
[[Category:Events]]<br />
[[Category:Gramps terminology]]<br />
[[Category:Translators/Categories]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Events_in_Gramps&diff=78634Events in Gramps2020-05-28T09:02:09Z<p>GulliblePangolin: </p>
<hr />
<div>{{languages|Events in Gramps}}<br />
<br />
An overview of the predefined events in Gramps are given, with their meaning. <br />
<br />
;Events and event types<br />
<br />
'''Events''' form a core concept in genealogical research. It is important therefore that the terminology and usage is consistent and well defined, so as to allow for optimal communication, translation and portability.<br />
<br />
An "event" is an umbrella term, and is used loosely to denote a fact about an individual, an event proper that occurs in his or her life, or an attribute. As examples, every individual has a birth event, and eventually a death event. Children being born to the individual would also be events. Being childless however is an attribute or fact about that individual.<br />
<br />
Generally setting an event for an individual allows you to to enter a data set, including the date, description, associated place, etc, in a structured way. <br />
<br />
In Gramps you define an event as belonging to a [[Gramps_Glossary#E|event type]]. This is useful as it allows the grouping of events under a common denominator, the event type. When creating an event, you must first select the event type. This can be any of the predefined events, or you can create a [[Custom_Event_Types|custom event]] just by typing a name. <br />
<br />
The pre-defined events provide most of what you need. For the sake of frivolity however, let us imagine that great uncle George was a lothario, and proud of it, and insisted that you recorded details of his numerous conquests in exchange for some vital genealogy documents that you need. You could then define an event type "affairs", and then in his individual record enter one such event for each affair, entering the date, place, details, etc for each. You then end up with a list of all his affairs listed chronologically. <br />
<br />
Frivolity apart however, defining too many event types can be problematic, and in many cases it might be better practice to group events under the same event type, and instead use the description field to add an extra nuance.<br />
<br />
Let us first provide an overview of the predefined events types available in Gramps, and then later mention event types that are not in that list.<br />
<br />
== Event types available in Gramps==<br />
The use of most event types is self explanatory, and the best way to familiarise yourself with them is simply to set to and dabble! However some events need more careful use, and introduce concepts that are not at first obvious.<br />
<br />
==Life Events==<br />
<br />
===Adopted===<br />
This type is for events related to childhood adoption. Typically the event is added to the individual being adopted, with this person playing the primary role. Administrators, civil servants and parents can be added to the event with different [[Gramps_Glossary#E|event roles]] <br />
<br />
The adoption event can be added for the process of adoption (which can take several months), but also as a placeholder for an adoption certificate that you have as a source. <br />
<br />
On adding the person to the family he is adopted into, one should also set his relationship with his adoptive parents to ''adopted''. This doubles the event information somewhat, but is used in some reports.<br />
<br />
===[[Baptise_record|Baptism]]===<br />
The event of baptism (not LDS), performed in infancy or later<br />
<br />
===[[Birth_certificate|Birth]]===<br />
The event of entering into life<br />
<br />
===Burial===<br />
The event of the proper disposing of the mortal remains of a deceased person<br />
<br />
===Cremation===<br />
Disposal of the remains of a person's body by fire<br />
<br />
===[[Death_certificate|Death]]===<br />
The event when mortal life terminates<br />
<br />
==Family==<br />
<br />
===Alternate Marriage===<br />
A relationship such as Cohabitation, Common Law Marriages, Civil Unions, Domestic Partnerships.<br />
<br />
===[[Indicate_a_divorce|Divorce]]===<br />
An event of dissolving a marriage through civil action<br />
<br />
===Divorce Filing===<br />
An event of filing for a divorce by a spouse<br />
<br />
===Engagement===<br />
An event of recording or announcing an agreement between two people to become married<br />
<br />
===Marriage===<br />
The marriage event is a bounding ceremony between two people before an official body. In other words, it is the state of being united to another person in a consensual and contractual relationship recognized (normally) by law. <br />
<br />
You should hence use this event typically as the 'official' starting event of the family unit in Gramps, that is, use it as a family event, with event role ''family''. Note that the family could be missing a ''father'', ''mother'' or both. Sharing an event with roles ''bride'' and ''groom'' is not the recommended approach in Gramps.<br />
<br />
Note further that the marriage event is wider than what is used in day-to-day language. It indicates civil marriage, church marriage, and all other types of union between adults that is official. <br />
<br />
To indicate an official end of a ''marriage event'', one should use the '''Divorce''' event.<br />
<br />
===Marriage Settlement===<br />
An event of creating an agreement between two people contemplating marriage, at which time they agree to release or modify property rights that would otherwise arise from the marriage<br />
<br />
===Marriage License===<br />
An event of obtaining a legal license to marry<br />
<br />
===Marriage Contract===<br />
An event of recording a formal agreement of marriage, including the prenuptial agreement in which marriage partners reach agreement about the property rights of one or both, securing property to their children<br />
<br />
===Marriage Banns===<br />
An event of an official public notice given that two people intend to marry<br />
<br />
===Annulment===<br />
Declaring a marriage void from the beginning (never existed)<br />
<br />
==Academic==<br />
<br />
===Degree===<br />
<br />
===Education===<br />
Indicator of a level of education attained<br />
<br />
===Graduation===<br />
An event of awarding educational diplomas or degrees to individuals<br />
<br />
==Legal==<br />
<br />
===Probate===<br />
An event of judicial determination of the validity of a will. May indicate several related court activities over several dates<br />
<br />
===Will===<br />
A legal document treated as an event, by which a person disposes of his or her estate, to take effect after death. The event date is the date the will was signed while the person was alive<br />
<br />
==Religious==<br />
<br />
===Adult Christening===<br />
The religious event (not LDS) of baptizing and/or naming an adult person<br />
<br />
===Bas Mitzvah===<br />
The ceremonial 'coming of age' event held when a Jewish girl reaches age 13, also known as "Bat Mitzvah"<br />
<br />
===Bar Mitzvah===<br />
The ceremonial 'coming of age' event held when a Jewish boy reaches age 13<br />
<br />
===Blessing===<br />
A religious event of bestowing divine care or intercession. Sometimes given in connection with a naming ceremony<br />
<br />
===[[Baptise_record|Christening]]===<br />
The act of baptizing and/or naming a child<br />
<br />
===Confirmation===<br />
Confirmation is a religious sacrament, ritual or rite of passage practiced by several Christian denominations and Reform Judaism. The term is intended to reflect a strengthening or deepening of one's relationship with God and church.<br />
<br />
===First Communion===<br />
A religious rite, the first act of sharing in the Lord's supper as part of church worship<br />
<br />
===Religion===<br />
A religious denomination to which a person is affiliated or for which a record applies<br />
<br />
==Residence==<br />
<br />
===[[Census]]===<br />
The event of the periodic count of the population for a designated locality, such as a national or state Census<br />
<br />
===Property===<br />
Pertaining to possessions such as real estate or other property of interest<br />
<br />
===[[Why_residence_event_and_not_Address%3F|Residence]]===<br />
The act of dwelling at an address for a period of time<br />
<br />
==Travel==<br />
<br />
===Naturalization===<br />
The event of obtaining citizenship<br />
<br />
===Emigration===<br />
An event of leaving one's homeland with the intent of residing elsewhere<br />
<br />
===Immigration===<br />
An event of entering into a new locality with the intent of residing there<br />
<br />
==Other==<br />
<br />
===Nobility Title===<br />
<br />
===Number of Marriages===<br />
The number of times this person has participated in a family as a spouse or parent<br />
<br />
===Cause Of Death===<br />
A description of the cause of death<br />
<br />
===Medical Information===<br />
<br />
==Vocational==<br />
<br />
===Elected===<br />
<br />
===Military Service===<br />
<br />
===Occupation===<br />
The type of work or profession of an individual<br />
<br />
===Ordination===<br />
Pertaining to a religious ordinance in general<br />
<br />
===Retirement===<br />
An event of exiting an occupational relationship with an employer after a qualifying time period<br />
<br />
==Custom==<br />
<br />
See [[Custom Event Types]] for some event types that are currently used by some users.<br />
<br />
<br />
== Event types not available in Gramps ==<br />
===[[Draft_lottery|Draft lottery]]===<br />
The Draft Lottery was a practice in general use, used to select who should have to undertake military service. Before the advent of a permanent professional army, it was not feasible to train all young boys, so some selection process was needed to determine who would or would not be drafted. So as to make this a fair process, it was common practice to organise a lottery, into which all boys of certain age had to be entered.<br />
<br />
The documents pertaining to these lotteries form an useful source of genealogical information, as all boys of a certain age were required to participate. <br />
<br />
This event type should be used for all the events/attributes relating to a Draft Lottery, for example:<br />
<br />
a) the lottery itself. This is associated with a place, and a specific date.<br />
<br />
b) legal documents relating to the lottery. Boys from rich families who were selected to join the army by the lottery process frequently paid commoners to take their place. Legal contracts were drafted for this. <br />
<br />
c) desertion documents concerning the lottery. Many selected individuals emigrated abroad so as to avoid their draft, with the consequence that they were recorded as deserters in their home country. In genealogical research this event can prove very difficult to trace, as deserters often changed their name to evade detection.<br />
<br />
== Events and Facts == <br />
<br />
[https://wiki.phpgedview.net/en/index.php?title=Facts_and_Events PhpGedView] lists the naming conventions in GEDCOM standard between : '''Events''' and '''Facts'''.<br />
<br />
=See also=<br />
* [[Gramps Glossary]] - overview of terms that appear in Gramps<br />
<br />
[[Category:Gramps terminology]]<br />
[[Category:Translators/Categories]]<br />
[[Category:Events]]<br />
[[Category:Tutorials]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Other_genealogy_tools&diff=78633Other genealogy tools2020-05-28T08:58:26Z<p>GulliblePangolin: /* Cranefoot */</p>
<hr />
<div>{{languages|Other genealogy tools}}<br />
In addition to the tools in Gramps, there are other [http://www.fsf.org/ Free Software] or [http://www.opensource.org/ Open Source] genealogy tools to make websites, trees, parse gedcom, .... If Gramps tools do not meet your needs, you may wish to consider one of the following tools.<br />
<br />
==ADAN==<br />
[http://fabrice.bouffanet.free.fr/Adan.shtml ADAN (Archivage D'Actes Notariés)] is a set of PHP modules in [[France|french]] with a search engine for managing Notarial certificates. It needs SHTML, PHP and MYSQL support. Released under GPL2.<br />
<br />
==Blossoc==<br />
[http://daimi.au.dk/~mailund/Blossoc/ Blossoc] is a GPL linkage disequilibrium association mapping tool that attempts to build (perfect) genealogies for each site in the input and score these according to non-random clustering of affected individuals, and judge high-scoring areas as likely candidates for containing disease affecting variation.<br />
<br />
==CollectiveAccess==<br />
[https://www.collectiveaccess.org/ CollectiveAccess] is a highly configurable cataloguing tool and web-based application for museums, archives and digital collections. Available free of charge under the GPL open-source license, it requires little to no custom programming to support a variety of metadata standards, external data sources and repositories, as well as most popular media formats. In addition to multilingual cataloguing facilities, it allows publication of this data in the languages of your choice.<br />
<br />
==Cranefoot==<br />
[http://www.finndiane.fi/software/cranefoot/ Cranefoot] is a lightweight program designed primarily for geneticists but you can use it for other pedigree visualization as well. Processes hundreds of families and thousands of individuals at once and wraps the results into a single document. Under GPL license.<br />
<br />
==eSciDoc==<br />
<br />
With [https://www.escidoc.org/ eSciDoc], scientists, librarians, and software developers can work with research data, create novel forms of publications, and establish new ways of scientific and scholarly communication. It is under Common Development and Distribution License (CDDL), an OSI-certified license.<br />
<br />
==Esp2ged==<br />
[http://notendur.hi.is/bjr2/esp2ged/ Esp2ged] is a program to move data from Espólín to the GEDCOM file format supported by (almost) all genealogy programs. Esp2ged is released under the GNU GPL License, version 3 or higher.<br />
<br />
==ExpoActes==<br />
[http://expocartes.monrezo.be/ ExpoActes] is a [[Belgium|belgian (french)]] PHP/MySQL module for easily displaying, editing and modifing certificates on '''your''' web server host. <br />
Released under GPL, you need at least Apache 1.3, PHP 4.3 and MySQL 4.0.<br />
Levels for access:<br><br />
*1 = Access to city, parish<br />
*2 = Access to patronymic<br />
*3 = Access to tables (names and dates)<br />
*4 = Access to more informations on certificates <br />
*5 = Allowed to load data with Nimègue (Windows program)<br />
*6 = Allowed to load data with CSV ([http://www.documentfoundation.org/download/ LibreOffice] or text) <br />
*7 = ** not used<br />
*8 = Allowed to manage all data<br />
*9 = Admin<br />
<blockquote>Seems Linux users need [http://expocartes.monrezo.be/download/actes.zip main module] and [http://expocartes.monrezo.be/download/_config.zip config]. This module is powerful but in French-only.<br />
[http://expocartes.monrezo.be/actes/admin/aide/chargecsv2.html help (in french)] for importing CSV on your server.<br />
</blockquote><br />
<br />
==Familier/Familiar==<br />
[http://familier.sourceforge.net/ Familier/Familiar] is a GPL cross-platform Family Tree management software using QT4. It supports viewing/editing file tree using drag-drop in multiple ways. Events allow you to define events in any number.<br />
It is available for both UNIX and Windows.<br />
<br />
==FASTLINK==<br />
[http://www.ncbi.nlm.nih.gov/CBBResearch/Schaffer/fastlink.html FASTLINK] is a significantly modified and improved version of the main programs of LINKAGE. It has been used in over 1000 published genetic linkage studies. See also [http://www.ncbi.nlm.nih.gov/CBBresearch/Schaffer/pedhunter.html PedHunter] and [[#Cranefoot|Cranefoot]].<br />
<br />
==Gedail==<br />
[http://jfbaquet.free.fr/outils/fonc_en.html Gedail] generates a Web genealogical site from a Gedcom file based on the gedcom 5.5 standard. It doesn't handle all gedcom elements. It is released under GPL.<br />
<br />
==GED2WWW-Genatoile==<br />
GED2WWW was an open source software originally written by Leslie Howard. Jean-Baptiste Fahy maintained the [http://home.nordnet.fr/~jbfahy/ged2wwwe.htm program] under [http://home.nordnet.fr/%7Ejbfahy/readme.txt GPL] but the developments are now on a new program: [http://home.nordnet.fr/~jbfahy/Genatoile/ GénàToile], which not display yet non-ASCII characters under UTF-8.<br />
<br />
==Gedcom one-to-one to XML==<br />
[http://www.unterstein.net/su/nn2x/ged1212xml.html ged1212xml] are scripts (awk|wsh ~ Javascript for Windows Script Host) to convert [[Gedcom]] data – one-to-one to wellformatted XML.<br />
<br />
==Généapro==<br />
[http://briot.github.com/geneapro/ Généapro] is GPL3 web genealogical software based on the [http://www.ngsgenealogy.org/cs/GenTech_Projects GenTech data model].<br />
<br />
==GenXchange==<br />
[http://mrgibson.com/gedcom/ GenXchange] is an experimental collection of free GPL genealogy tools to work with GEDCOM 5.5 and GSF 2.0 files. This software allows export of data to GEDML and HTML files. GEDXchange runs on Linux, Windows 95 through Vista, and OSX operating systems. Written in C, these tool are a set of fast binaries (not scripts) of both graphical interface and command line interface applications to meet most genealogy viewing and recording needs.<br />
<br />
==Gramps-php-exporter==<br />
[https://github.com/steelwil/gramps-php-exporter gramps-php-exporter] exports your [[Gramps XML]] database to a SQLite database, using python 2 or 3.<br />
<br />
Additionally there are some PHP scripts to display your database on the web.<br />
<br />
All privacy settings are honoured.<br />
<br />
==hrlib==<br />
[http://sourceforge.net/projects/hrlib/ hrlib] is a python library to read Heredis (a genealogy program) file. It allow you to read-only everything in a Heredis file with extension .hrX. Plus [http://sourceforge.net/projects/hrreportmaker/ hrreportmaker] create some reports with hrlib. It is able to use LifeLine report and also create new one in Python. There is no packages but files are on CVS. It is released under GPL. <br />
<br />
==hr2ged==<br />
[http://sourceforge.net/projects/hr2ged/ hr2ged] is a python program that transcribe Heredis file in Gedcom. It is available both with a GUI and on command-line. Also [http://loic.fejoz.free.fr/hr2db/ hr2db] may transcribe to MYSQL, ACCESS (via ODBC), Gadfly. It is released under GPL.<br />
<br />
==JcArbGen==<br />
[http://perso.orange.fr/noroc/jcarbgen.htm JcArbGen] is a KDE (qt) pedigree tree manager in '''french'''. It is released under GPL.<br />
<br />
==Karto==<br />
[http://sourceforge.net/projects/karto karto] needs java and is released under GPL.<br />
<blockquote>Karto allows to calibrate a scanned map with some known geo-points (Lambert, UTM, ...). After that, you can add any points (GPS points) in the map to build your own map. You can also add a transparent GIF image in the map after calibration (cave or mine). It doesn't work with common genealogical formats but with most images and textual masks. Useful if you want to display ancestors on your old map.</blockquote><br />
<br />
==Omeka==<br />
[http://omeka.org Omeka] is a GPL flexible web-publishing platform for the display of library, museum, archives, and scholarly collections and exhibitions.<br />
<br />
==openBMD==<br />
[http://openbmd.sourceforge.net/Home.html openBMD] is a free and cross-platform desktop application under GPL2 for the transcription of Birth, Marriage and Death (BMD) index records.<br />
<br />
==Phpmyfamily==<br />
[http://www.phpmyfamily.net/ phpmyfamily] is a dynamic genealogy website builder which allows geographically dispersed family members to maintain a central database of research which is readily accessable and editable. By having a central repository, family members can contribute as and when information becomes available without requiring them to send it to a central 'custodian', or disseminate via email, and allows anecdotal information and possible leads to be shared.<br />
<br />
==PyPedal==<br />
[http://pypedal.sourceforge.net/ PyPedal] - Python Pedigree Analysis is a Python module that provides tools for the manipulation of pedigrees, simple visualization of pedigrees, and the calculation of measures of genetic diversity from pedigrees.<br />
<br />
==Rodovid==<br />
[http://rodovid.sourceforge.net/ Rodovid] is a GPL2 drag-n-drop genealogic program for Linux or Windows based on Tk, Perl. You can edit info (name, sex, dates of birth, death, marriage, etc...) for individuals, add/remove photos, import and export GEDCOM data, creating sites like [http://www.mishchenko.tk this one].<br />
<br />
== SimplePyGed ==<br />
[http://github.com/dijxtra/simplepyged SimplePyGed - A simple Python GEDCOM parser], provides Python [http://en.wikipedia.org/wiki/Application_programming_interface API] to most commonly used GEDCOM records, tags and events. Released under GPL.<br />
<br />
== Web Family Tree ==<br />
[http://www.simonward.com/cgi-bin/page.pl?family/tree Web Family Tree] draws a tree of ancestors and descendants for any person, showing any number of generations (where the information exists). Published with a GNU General Public License. Also, Gramps allows to export into this format. You may download the last version on [http://freshmeat.net/projects/familytree_cgi/ freshmeat].<br />
<br />
== XGenealogy ==<br />
[http://www.bhagooa.com/XGenealogy/index.html XGenealogy] is a open-source genealogy program using GEDCOM 6.0 and written in java.<br />
<br />
==Xurano==<br />
[http://www.xurano.org/ Xurano] is a GNU Public License graphical editor to create and edit mid-size family trees (some hundred persons).<br />
<br />
==Yggdrasil==<br />
[http://code.google.com/p/yggdrasil-genealogy/ Yggdrasil] is a PostgreSQL database and a PHP front-end for large genealogy or prosopography research projects, with focus on documentation of the entire population of a particular area. New BSD License.<br />
<br />
== Projects hosted on Sourceforge code ==<br />
[http://sourceforge.net/directory/home-education/genealogy Sourceforge] is hosting some free and open source projects.<br />
<br />
== Projects hosted on Google code ==<br />
[http://code.google.com/hosting/search?q=label:Genealogy Google code (archive)] hosted many free and open source projects.<br />
<br />
== Projects hosted on Github ==<br />
[https://github.com/topics/genealogy Github] hosting many free and open source genealogy projects.<br />
<br />
== Non-Free Software ==<br />
In addition to [http://en.wikipedia.org/wiki/Free_Software Free Software] and [http://en.wikipedia.org/wiki/Open_source_software Open Source Software] programs, there are no cost, shareware and commercial genealogy tools. It is not the goal of the Gramps project to promote such products, since they do not preserve the user's freedom and can lock the user's data out of his/her control.<br />
<br />
For more information on no cost, shareware and commercial, see [http://www.cyndislist.com/software.htm Cyndi's List] or [http://genealogyblog.geneanet.org/ Geneasoft].<br />
<br />
== Other Tools ==<br />
One can also exchange information with family web applications, but these are not directly genealogy related. They can be interesting to host data generated from genealogy applications (anniversaries, ...). Some free tools (you need the skill to set up a web service, most web projects have companies connected to them that for a fixed fee host and maintain the application for you):<br />
<br />
* '''Family Connection''': [http://familyconnect.rubyforge.org/ Family Connection] is a GPL Web application based on [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails], which restricts access only to family members by requiring a family password. It offers Family News, Address Book, Photo Album.<br />
<br />
== Handset ==<br />
<br />
* Experimental [http://gramps-project.org/2011/01/gramps-mobile-interface-%E2%80%93-part-ii/ Gramps mobile interface] for devices with Meego and maybe devices with [https://www.tizen.org/devices Tizen].<br />
<br />
See also [[DenominoViso]]<br />
<br />
* Experimental [http://code.google.com/p/maegen/ Maegen] for Maemo5/N900.<br />
<br />
<br />
[[Category:Genealogy|All articles]]<br />
[[Category:Developers/Design]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Other_genealogy_tools&diff=78632Other genealogy tools2020-05-28T08:55:02Z<p>GulliblePangolin: /* CollectiveAccess */</p>
<hr />
<div>{{languages|Other genealogy tools}}<br />
In addition to the tools in Gramps, there are other [http://www.fsf.org/ Free Software] or [http://www.opensource.org/ Open Source] genealogy tools to make websites, trees, parse gedcom, .... If Gramps tools do not meet your needs, you may wish to consider one of the following tools.<br />
<br />
==ADAN==<br />
[http://fabrice.bouffanet.free.fr/Adan.shtml ADAN (Archivage D'Actes Notariés)] is a set of PHP modules in [[France|french]] with a search engine for managing Notarial certificates. It needs SHTML, PHP and MYSQL support. Released under GPL2.<br />
<br />
==Blossoc==<br />
[http://daimi.au.dk/~mailund/Blossoc/ Blossoc] is a GPL linkage disequilibrium association mapping tool that attempts to build (perfect) genealogies for each site in the input and score these according to non-random clustering of affected individuals, and judge high-scoring areas as likely candidates for containing disease affecting variation.<br />
<br />
==CollectiveAccess==<br />
[https://www.collectiveaccess.org/ CollectiveAccess] is a highly configurable cataloguing tool and web-based application for museums, archives and digital collections. Available free of charge under the GPL open-source license, it requires little to no custom programming to support a variety of metadata standards, external data sources and repositories, as well as most popular media formats. In addition to multilingual cataloguing facilities, it allows publication of this data in the languages of your choice.<br />
<br />
==Cranefoot==<br />
[http://www.finndiane.fi/software/cranefoot/ Cranefoot] processes hundreds of families and thousands of individuals at once and wraps the results into a single document. Under GPL license.<br />
<br />
==eSciDoc==<br />
<br />
With [https://www.escidoc.org/ eSciDoc], scientists, librarians, and software developers can work with research data, create novel forms of publications, and establish new ways of scientific and scholarly communication. It is under Common Development and Distribution License (CDDL), an OSI-certified license.<br />
<br />
==Esp2ged==<br />
[http://notendur.hi.is/bjr2/esp2ged/ Esp2ged] is a program to move data from Espólín to the GEDCOM file format supported by (almost) all genealogy programs. Esp2ged is released under the GNU GPL License, version 3 or higher.<br />
<br />
==ExpoActes==<br />
[http://expocartes.monrezo.be/ ExpoActes] is a [[Belgium|belgian (french)]] PHP/MySQL module for easily displaying, editing and modifing certificates on '''your''' web server host. <br />
Released under GPL, you need at least Apache 1.3, PHP 4.3 and MySQL 4.0.<br />
Levels for access:<br><br />
*1 = Access to city, parish<br />
*2 = Access to patronymic<br />
*3 = Access to tables (names and dates)<br />
*4 = Access to more informations on certificates <br />
*5 = Allowed to load data with Nimègue (Windows program)<br />
*6 = Allowed to load data with CSV ([http://www.documentfoundation.org/download/ LibreOffice] or text) <br />
*7 = ** not used<br />
*8 = Allowed to manage all data<br />
*9 = Admin<br />
<blockquote>Seems Linux users need [http://expocartes.monrezo.be/download/actes.zip main module] and [http://expocartes.monrezo.be/download/_config.zip config]. This module is powerful but in French-only.<br />
[http://expocartes.monrezo.be/actes/admin/aide/chargecsv2.html help (in french)] for importing CSV on your server.<br />
</blockquote><br />
<br />
==Familier/Familiar==<br />
[http://familier.sourceforge.net/ Familier/Familiar] is a GPL cross-platform Family Tree management software using QT4. It supports viewing/editing file tree using drag-drop in multiple ways. Events allow you to define events in any number.<br />
It is available for both UNIX and Windows.<br />
<br />
==FASTLINK==<br />
[http://www.ncbi.nlm.nih.gov/CBBResearch/Schaffer/fastlink.html FASTLINK] is a significantly modified and improved version of the main programs of LINKAGE. It has been used in over 1000 published genetic linkage studies. See also [http://www.ncbi.nlm.nih.gov/CBBresearch/Schaffer/pedhunter.html PedHunter] and [[#Cranefoot|Cranefoot]].<br />
<br />
==Gedail==<br />
[http://jfbaquet.free.fr/outils/fonc_en.html Gedail] generates a Web genealogical site from a Gedcom file based on the gedcom 5.5 standard. It doesn't handle all gedcom elements. It is released under GPL.<br />
<br />
==GED2WWW-Genatoile==<br />
GED2WWW was an open source software originally written by Leslie Howard. Jean-Baptiste Fahy maintained the [http://home.nordnet.fr/~jbfahy/ged2wwwe.htm program] under [http://home.nordnet.fr/%7Ejbfahy/readme.txt GPL] but the developments are now on a new program: [http://home.nordnet.fr/~jbfahy/Genatoile/ GénàToile], which not display yet non-ASCII characters under UTF-8.<br />
<br />
==Gedcom one-to-one to XML==<br />
[http://www.unterstein.net/su/nn2x/ged1212xml.html ged1212xml] are scripts (awk|wsh ~ Javascript for Windows Script Host) to convert [[Gedcom]] data – one-to-one to wellformatted XML.<br />
<br />
==Généapro==<br />
[http://briot.github.com/geneapro/ Généapro] is GPL3 web genealogical software based on the [http://www.ngsgenealogy.org/cs/GenTech_Projects GenTech data model].<br />
<br />
==GenXchange==<br />
[http://mrgibson.com/gedcom/ GenXchange] is an experimental collection of free GPL genealogy tools to work with GEDCOM 5.5 and GSF 2.0 files. This software allows export of data to GEDML and HTML files. GEDXchange runs on Linux, Windows 95 through Vista, and OSX operating systems. Written in C, these tool are a set of fast binaries (not scripts) of both graphical interface and command line interface applications to meet most genealogy viewing and recording needs.<br />
<br />
==Gramps-php-exporter==<br />
[https://github.com/steelwil/gramps-php-exporter gramps-php-exporter] exports your [[Gramps XML]] database to a SQLite database, using python 2 or 3.<br />
<br />
Additionally there are some PHP scripts to display your database on the web.<br />
<br />
All privacy settings are honoured.<br />
<br />
==hrlib==<br />
[http://sourceforge.net/projects/hrlib/ hrlib] is a python library to read Heredis (a genealogy program) file. It allow you to read-only everything in a Heredis file with extension .hrX. Plus [http://sourceforge.net/projects/hrreportmaker/ hrreportmaker] create some reports with hrlib. It is able to use LifeLine report and also create new one in Python. There is no packages but files are on CVS. It is released under GPL. <br />
<br />
==hr2ged==<br />
[http://sourceforge.net/projects/hr2ged/ hr2ged] is a python program that transcribe Heredis file in Gedcom. It is available both with a GUI and on command-line. Also [http://loic.fejoz.free.fr/hr2db/ hr2db] may transcribe to MYSQL, ACCESS (via ODBC), Gadfly. It is released under GPL.<br />
<br />
==JcArbGen==<br />
[http://perso.orange.fr/noroc/jcarbgen.htm JcArbGen] is a KDE (qt) pedigree tree manager in '''french'''. It is released under GPL.<br />
<br />
==Karto==<br />
[http://sourceforge.net/projects/karto karto] needs java and is released under GPL.<br />
<blockquote>Karto allows to calibrate a scanned map with some known geo-points (Lambert, UTM, ...). After that, you can add any points (GPS points) in the map to build your own map. You can also add a transparent GIF image in the map after calibration (cave or mine). It doesn't work with common genealogical formats but with most images and textual masks. Useful if you want to display ancestors on your old map.</blockquote><br />
<br />
==Omeka==<br />
[http://omeka.org Omeka] is a GPL flexible web-publishing platform for the display of library, museum, archives, and scholarly collections and exhibitions.<br />
<br />
==openBMD==<br />
[http://openbmd.sourceforge.net/Home.html openBMD] is a free and cross-platform desktop application under GPL2 for the transcription of Birth, Marriage and Death (BMD) index records.<br />
<br />
==Phpmyfamily==<br />
[http://www.phpmyfamily.net/ phpmyfamily] is a dynamic genealogy website builder which allows geographically dispersed family members to maintain a central database of research which is readily accessable and editable. By having a central repository, family members can contribute as and when information becomes available without requiring them to send it to a central 'custodian', or disseminate via email, and allows anecdotal information and possible leads to be shared.<br />
<br />
==PyPedal==<br />
[http://pypedal.sourceforge.net/ PyPedal] - Python Pedigree Analysis is a Python module that provides tools for the manipulation of pedigrees, simple visualization of pedigrees, and the calculation of measures of genetic diversity from pedigrees.<br />
<br />
==Rodovid==<br />
[http://rodovid.sourceforge.net/ Rodovid] is a GPL2 drag-n-drop genealogic program for Linux or Windows based on Tk, Perl. You can edit info (name, sex, dates of birth, death, marriage, etc...) for individuals, add/remove photos, import and export GEDCOM data, creating sites like [http://www.mishchenko.tk this one].<br />
<br />
== SimplePyGed ==<br />
[http://github.com/dijxtra/simplepyged SimplePyGed - A simple Python GEDCOM parser], provides Python [http://en.wikipedia.org/wiki/Application_programming_interface API] to most commonly used GEDCOM records, tags and events. Released under GPL.<br />
<br />
== Web Family Tree ==<br />
[http://www.simonward.com/cgi-bin/page.pl?family/tree Web Family Tree] draws a tree of ancestors and descendants for any person, showing any number of generations (where the information exists). Published with a GNU General Public License. Also, Gramps allows to export into this format. You may download the last version on [http://freshmeat.net/projects/familytree_cgi/ freshmeat].<br />
<br />
== XGenealogy ==<br />
[http://www.bhagooa.com/XGenealogy/index.html XGenealogy] is a open-source genealogy program using GEDCOM 6.0 and written in java.<br />
<br />
==Xurano==<br />
[http://www.xurano.org/ Xurano] is a GNU Public License graphical editor to create and edit mid-size family trees (some hundred persons).<br />
<br />
==Yggdrasil==<br />
[http://code.google.com/p/yggdrasil-genealogy/ Yggdrasil] is a PostgreSQL database and a PHP front-end for large genealogy or prosopography research projects, with focus on documentation of the entire population of a particular area. New BSD License.<br />
<br />
== Projects hosted on Sourceforge code ==<br />
[http://sourceforge.net/directory/home-education/genealogy Sourceforge] is hosting some free and open source projects.<br />
<br />
== Projects hosted on Google code ==<br />
[http://code.google.com/hosting/search?q=label:Genealogy Google code (archive)] hosted many free and open source projects.<br />
<br />
== Projects hosted on Github ==<br />
[https://github.com/topics/genealogy Github] hosting many free and open source genealogy projects.<br />
<br />
== Non-Free Software ==<br />
In addition to [http://en.wikipedia.org/wiki/Free_Software Free Software] and [http://en.wikipedia.org/wiki/Open_source_software Open Source Software] programs, there are no cost, shareware and commercial genealogy tools. It is not the goal of the Gramps project to promote such products, since they do not preserve the user's freedom and can lock the user's data out of his/her control.<br />
<br />
For more information on no cost, shareware and commercial, see [http://www.cyndislist.com/software.htm Cyndi's List] or [http://genealogyblog.geneanet.org/ Geneasoft].<br />
<br />
== Other Tools ==<br />
One can also exchange information with family web applications, but these are not directly genealogy related. They can be interesting to host data generated from genealogy applications (anniversaries, ...). Some free tools (you need the skill to set up a web service, most web projects have companies connected to them that for a fixed fee host and maintain the application for you):<br />
<br />
* '''Family Connection''': [http://familyconnect.rubyforge.org/ Family Connection] is a GPL Web application based on [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails], which restricts access only to family members by requiring a family password. It offers Family News, Address Book, Photo Album.<br />
<br />
== Handset ==<br />
<br />
* Experimental [http://gramps-project.org/2011/01/gramps-mobile-interface-%E2%80%93-part-ii/ Gramps mobile interface] for devices with Meego and maybe devices with [https://www.tizen.org/devices Tizen].<br />
<br />
See also [[DenominoViso]]<br />
<br />
* Experimental [http://code.google.com/p/maegen/ Maegen] for Maemo5/N900.<br />
<br />
<br />
[[Category:Genealogy|All articles]]<br />
[[Category:Developers/Design]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Resources_and_related_sites&diff=78631Resources and related sites2020-05-28T08:50:57Z<p>GulliblePangolin: </p>
<hr />
<div>{{languages|Resources and related sites}}<br />
Resources and internet sites that may be of interest to genealogy enthusiasts.<br />
<br />
{{man tip|If you have a site you would like to add, please do so.}}<br />
<br />
==Genealogy organizations==<br />
<br />
* [https://www.cdfhs.org.au/ Campbelltown District Family History Society Inc (NSW, Australia)]. We are a community organisation born out of the need to help others in our area learn how to do their genealogical research. We also raise money to help provide more resources in the local library's Family History Room.<br />
* [http://www.cornwall-opc.org/ Cornwall Online Parish Clerks]. This is an informal group of Genealogists who voluntarily assist others by doing look ups of U.K. records we have collected over the years. They call themselves "online parish clerks" because the major resources they use are the (ecclesiastical) parish records of births, deaths and marriages. The group concentrates on Cornwall.<br />
* The [http://www.worldgenweb.org/ WorldGenWeb] Project is a non-profit, volunteer based organization dedicated to providing genealogical and historical records and resources for world-wide access.<br />
<br />
==Family information sites==<br />
<br />
* [http://www.annforbes.org/ Ann Forbes (First Fleet Convict) and Descendants]. This site is for Ann Forbes' descendants. Ann was a First Fleet Convict who arrived in Australia on the 'Prince of Wales' in 1788. There are now many thousands of descendants and quite a lot of us are very interested in her life, times and family.<br />
<br />
==General information sites==<br />
* [http://www.familysearch.org FamilySearch.org] is one of the main international sites for genealogy. It is a resource of the [https://www.familysearch.org/home/about CJCLDS], a religious organization. (Gramps includes an [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#LDS|LDS tab]] for their unique ordinances information.)<br />
* [http://www.genuki.org.uk/ GENUKI] presents a large collection of genealogical information pages for England, Ireland, Scotland, Wales, the Channel Islands, and the Isle of Man.<br />
* [http://rootsweb.com/ RootsWeb] is the Internet's oldest and largest FREE genealogical community.<br />
* [http://en.wikipedia.org/wiki/Main_Page Wikipedia] is a useful resource for sourcing place names and their histories. Text, maps and related images are available under the GNU Free Documentation License or a similar, freely distributable licence.<br />
* [http://www.cyndislist.com/ Cyndi's List] Over a quarter of a million genealogy related links.<br />
* [http://www.rodovid.org Rodovid.org] is a MediaWiki-based genealogy site.<br />
* [http://werelate.org WeRelate.org] is a free wiki-based genealogy site covering people, families, places, sources, etc.<br />
* [http://genealogy.wikia.com Genealogy Wikia or "Familypedia"] is a free wiki-based genealogy site covering individuals, families, places, sources, etc; includes substantial copying of Wikipedia material about genealogy and places and people, then enhancing it.<br />
* [http://www.archive.org/ Internet Archive] purposes include offering permanent access for researchers, historians, scholars, people with disabilities, and the general public to historical collections that exist in digital format.<br />
* [http://hathitrust.org/ Hathi Trust Digital Library] is a very large-scale collaborative repository of digital content from research libraries including content digitized via the Google Books project and Internet Archive digitization initiatives, as well as content digitized locally by libraries.<br />
* [http://en.wikisource.org/wiki/Main_Page WikiSource] is an online library of free content publications, collected and maintained by a community. [http://en.wikisource.org/wiki/Special:IndexPages Collaborative transcriptions] are welcome.<br />
* [http://www.familytreeforum.com Family Tree Forum] is a free genealogy forum; also contains extensive Reference Library with research guides & external links, as well as Surname Database, Timeline, online magazine, Costume Gallery, plus much more!<br />
<br />
==US resources==<br />
* The [http://www.archives.gov/ National US Archives] and [http://aad.archives.gov/aad/ Archival databases].<br />
* [http://oedb.org/library/features/250-plus-killer-digital-libraries-and-archives Online libraries and archives] that focus mainly on localized, regional, and U.S. history, but it also includes larger collections, eText and eBook repositories, and a short list of directories to help you continue your research efforts.<br />
* The [http://international.loc.gov/intldl/intldlhome.html Global Gateway] - part of the [http://www.loc.gov/ Library of US Congress] - is a multimedia digital library, built with partners from around the world.<br />
* [http://www.loc.gov/rr/genealogy/ The Library of US Congress] has one of the world's premier collections of U.S. and foreign genealogical and local historical publications. The Library's genealogy collection began as early as 1815 with the purchase of Thomas Jefferson's library. See also the [http://www.loc.gov/coll/nucmc/index.html National Union Catalog of Manuscript Collections (NUCMC)]<br />
* [http://www.castlegarden.org/index.php CastleGarden] is a free site offers access to an extraordinary database of information on 11 million immigrants from 1820 through 1892, the year [http://www.libertyellisfoundation.org/ Ellis Island] opened.<br />
* [http://www.libertyellisfoundation.org/ Ellis Island]: more than 22 million passengers and members of ships' crews entered the United States through Ellis Island and the Port of New York between 1892 and 1924. See also this [http://stevenmorse.com/ellis2/ellis.html form] and the [http://stevenmorse.com/ellis2/ellisgold.html advanced one].<br />
* [http://www.mocavo.com/ Mocavo] aims to index the above resources and provides a search form.<br />
* [http://stevenmorse.com/ Stephen Morse] provides an index of good links to accessible resources.<br />
<br />
==Australian sources==<br />
* [http://prov.vic.gov.au/ Public Record Office Victoria]: this site provides a wide range of services to enable researchers to access the public records of Victoria. Links to immigration and emmigration records such as the ''Index to Registers of Assisted British Immigrants 1839-1871'' and ''Index of Inward Passenger Lists for British, Foreign and New Zealand Ports 1852-1923''<br />
* [http://www.clan-cameron.org.au/ Cameron genealogies]: this website celebrates those who descend from the Clan of the name of Cameron, in Australia.<br />
* [http://www.ianmarr.net.au/CEMINDEX.HTML Cemeteries of S.W. Victoria]: a useful collection of cemetery records. Keep in mind that before 1851, Victoria did not exist and the area was known as New South Wales.<br />
* [http://www.cwgc.org/ Commonwealth War Graves Commission]: the Debt of Honour Register is the Commission's database listing the 1.7 million men and women of the Commonwealth forces who died during the two world wars... The register can also be searched for details of the 67,000 Commonwealth civilians who died as a result of enemy action in the Second World War.<br />
* [http://firstfleet.uow.edu.au/ First Fleet] is a searchable database from the University of Wollongong. A text listing of the first three fleets is also [http://www.pcug.org.au/~pdownes/ available].<br />
* [http://members.pcug.org.au/~pblair/auscem/ Australian Cemetery Geolocations] A list of more than 3000 Australian cemeteries, with co-ordinates and a map to help locate each one.<br />
<br />
==French resources==<br />
===Online search===<br />
* [http://www.bigenet.org/index_us.php Bigenet] lists available certificates provided by some genealogical societies/associations.<br />
* [http://www.archivesnationales.culture.gouv.fr/ French Nationales Archives].<br />
* [http://www.archivesdefrance.culture.gouv.fr/ressources/en-ligne/ French Public Online] archives and ressources. Also access by [http://www.archivesdefrance.culture.gouv.fr/ressources/en-ligne/acces-par-type-de-documents type of search] and [http://www.archivesdefrance.culture.gouv.fr/ressources/en-ligne/service/ Provinces/Counties or cities].<br />
* The [http://www.fichierorigine.com/ Fichier Origine] and [http://www.bms2000.org/ BMS2000] databases for search in Quebec.<br />
* [http://www.geneabank.org/ GeneaBank] is a data sharing system between genealogical societies: in addition to a secured access to data records, GeneaBank offers an exchange system of points that allows any member of any participating society to browse anyone of the records that are provided by any society. This exchange system is only dedicated to manage possible discreapancies between ''consummating societies'' and ''providing societies''.<br />
* [http://www.collectionscanada.gc.ca/genealogy/index-e.html Library and Archives Canada] facilitates the discovery of our roots and family histories as a basic part of our Canadian heritage.<br />
<br />
===Others databases===<br />
====Collaborative====<br />
* [http://www.archives-aube.com/arkotheque/wiki_archives/ressource.php Aube's Archives (10)] provides collaborative indexes.<br />
* [http://ott.fr/wp/?page_id=870 Didier OTT] database with more than ''200 000 individuals'' on East France.<br />
* [http://gw2.geneanet.org/index.php3?b=favrejhas Favrejhas] is a genealogical database with more than ''600 000 individuals'' on North France.<br />
* [http://roglo.eu/roglo Roglo] is a database with around ''4 000 000 individuals''.<br />
* [http://www.francegenweb.org/~wiki/index.php/Portail:Listes_d%27%C3%A9changes Exchange Lists]<br />
<br />
====Association/Societies====<br />
* '''A'''ssociation des '''R'''eleveurs '''B'''énévoles pour la '''R'''echerche et l''''E'''ntraide (A.R.B.R.E):<br />
[http://www.marne-archive.com/ Marne County (51)] and related [http://www.meuse-archive.com/ Meuse (55)], [http://hautemarne-archive.com/ Haute-Marne (52)], [http://iledelareunion-archive.com/ Réunion (974)], [http://aisne-archive.com/ Aisne (02)], [http://ardennes-archive.com/ Ardennes (08)], [http://meurthemoselle-archive.com/ Meurthe-et-Moselle (54)], [http://jurarchive.com/ Jura (39)].<br />
* [http://baseaveyron.free.fr/ Aveyron County (12)]<br />
* [http://www.cousain.fr/recherche-ligne.php CousAin] is an index for Ain's Archives (01).<br />
* '''L'''ecture et '''I'''nformatisation des '''S'''ources '''A'''rchivistiques: [http://www.lisa90.org/ Lisa (90)].<br />
* [http://registres18.free.fr/ Registres18] with records on Cher (18).<br />
* [http://nomsdevendee.fr/ Noms de Vendée] provides a surnames index for Vendée (85).<br />
<br />
===General repositories===<br />
* [http://www.arbre-genealogique.eu/ Arbre généalogique] is a directory for web sites related to genealogy.<br />
* The [http://www.alfg.fr/ Centre d'Entraide Généalogique de France (C.E.G.F)] is a Portail which provides some [http://www.alfg.fr/numeric/index.htm genealogical resources].<br />
* The [http://www.cdhf.net/fr/ Departmental Center of History of the Families] has a vast genealogical library dealing with the families of France. It holds important funds of files concerning the whole of the French territory. (See the [http://www.cdhf.net/fr/index.php?t=bases&d=bases/moteurpat&c=moteurpat&f=selection databases])<br />
* [http://www.cyndislist.com/france.htm France Cyndi's List] of genealogy sites on internet.<br />
* [http://www.francegenweb.org/ FranceGenWeb] is a portal for genealogy.<br />
* Some [http://www.france-genealogie.fr/sections/rechercherbases/base%20de%20donnees locales and nationales bases].<br />
* [http://www.genealogylinks.net/europe/france/index.html France Genealogy Links] lists sites that have online genealogy resources, many of them free.<br />
* Portal from the [http://www.culture.fr/eng/Genealogie French Ministry of Culture and Communication] with some information and 9 databases.<br />
* [http://www.genealogie.org/ Genealogie.org] provides some resources for french related searches in America.<br />
* [http://www.geneawiki.com/index.php/Accueil Geneawiki] is a wiki related to genealogy.<br />
* [http://genealogyblog.geneanet.org/ Geneasoft] lists most up-to-date genealogical information and programs.<br />
* [http://www.francegenweb.org/~wiki/index.php/Accueil WikiGenWeb] the wiki of [http://www.francegenweb.org/ FranceGenWeb].<br />
<br />
===History===<br />
* [http://elsasserwurtzle.wordpress.com/boite-a-outils-du-genealogiste/telechargement/ Alsace/USA] with [https://elsasserwurtzle.files.wordpress.com/2012/06/emigrants-du-68-aux-usa-entre-1837-1870.pdf list of emigration from Alsace to USA] or [https://elsasserwurtzle.files.wordpress.com/2012/06/demandes-de-passeport-1793-1818.pdf passports from 1793 to 1818]. <br />
See also the [http://aad.archives.gov/aad/series-list.jsp?cat=GP44 US National Archives].<br />
* [http://gallica.bnf.fr/dossiers/html/dossiers/FranceAmerique/en/D1/Fr1.htm America/France] is a bilingual digital library made available by the ''Bibliothèque nationale de France'' in partnership with the Library of Congress ''the great library of Washington''. It explores the history of the French presence in North America from the first decades of the 16th Century to the end of the 19th Century.<br />
* [http://www.ancestramil.fr/ Ancestramil] provides useful informations about ancestors who were soldiers during their lifetime.<br />
* [http://www.apenet.eu/index.php?lang=en APEnet (Archives Portal Europe)] aims to build an Internet Gateway for Documents and Archives in Europe where fourteen European National Archives in close cooperation with the [http://www.europeana.eu/ Europeana] initiative will create a common access point to European archival descriptions and digital collections.<br />
* [http://www.archivesnationales.culture.gouv.fr/anom/fr/index.html Archives d'outre-mer] is a repository with most documents related to olds colonies. Every country where French government was present (all continent) are listed. You may find some maps, images, data for your genealogical search.<br />
* [http://www.banq.qc.ca/accueil/index.html Archives of Québec (BAnQ)] offers its services throughout Québec via a network of nine regional centres. This regional presence enables researchers from everywhere in Québec, or from beyond its borders, to discover and, in turn, present to others, the manifold pieces of our historical tapestry. The archival fonds and collections at the centres are accessible to the public, except for certain confidential documents.<br />
* [http://www.archivesportaleurope.eu Archives Portal Europe] provides access to information on archival material from different European countries as well as information on archival institutions throughout the continent. Related to [http://www.apenet.eu APEnet (Archives Portal Europe)]<br />
* [http://www.archivescanadafrance.org/english/accueil_en.html Canada/France] is a collaboration between Canada and France Archives.<br />
* [http://en.wikipedia.org/wiki/Europeana Europeana] is more what could be an european library using [[OCR]] and open source engine [http://en.wikipedia.org/wiki/Lucene Lucene]. Hungary, Portugal and France were active. Curently, seems to be a real European project. See also [https://github.com/europeana europeana's open projects].<br />
* [http://frda.stanford.edu/en/ap French Revolution Digital Archive] is a chronologically-ordered edited collection of sources on the French Revolution.<br />
* [http://gallica.bnf.fr/ Gallica] is the French numerical librarie with open specifications. Sounds, pictures, text are free of charges. Like [http://www.europeana.eu/ Europeana], Gallica use [[OCR]] (optical character recognition) for search.<br />
* [http://www.louisiane.culture.fr/en/som.html Louisiana/France].<br />
* [http://www.memoiredeshommes.sga.defense.gouv.fr/ Mémoire des hommes] gives the public access to databases created from the digitalization and indexation of biographical records preserved in the services of the ministry of defence. It also aims to honour the memory of those who took part in contemporary wars and sometimes gave their lives for their country.<br />
* For Russian and Armenian migrations, you can contact the [http://www.ofpra.gouv.fr/ <b>O</b>ffice <b>F</b>rançais de <b>P</b>rotection des <b>R</b>éfugiés et <b>A</b>patrides].<br />
* [http://www.genealogie.umontreal.ca/ PRDH ('''P'''rogramme de '''R'''echerche en '''D'''émographie '''H'''istorique : The Research Program in Historical Demography)] at the Université de Montréal undertook the exhaustive reconstruction of the population of Quebec from the beginnings of French colonization in the seventeenth century.<br />
* [http://www.stehelene.org/php/accueil.php?lang=en Medals of Saint-Hélèna] aims to create a database that will be of interest both to genealogists and historians. This work is especially important as the archives held by the Grand Chancellery of the Legion of Honour was destroyed in Paris in 1871. The Saint Helena medal, created in 1857 by Napoleon III, was awarded to the 405,000 soldiers still living in 1857, who had fought with Napoleon I during the 1792-1815 wars.<br />
* [http://search.ourontario.ca OurOntario] for search about Ontario province (Canada).<br />
<br />
==German information sites==<br />
* [http://www.denkmalprojekt.org/index.htm Denkmäler] is to memorialize the names of the dead and to collect, archive and make publicly available, particularly for use by genealogists, inscriptions from war memorials of the German and Austrian armies.<br />
* [http://compgen.de/ compgen.de] is a portal for genealogy in Germany. There you can find German genealogy-wiki, local online heritage books, online databases, address books and many more.<br />
* [http://www.volksbund.de/graebersuche.html Volksbund Deutsche Kriegsgräberfürsorge] is registering the German war dead abroad and to ensuring that it is updated and monitored.<br />
* Die [https://www.deutsche-digitale-bibliothek.de/ Deutsche Digitale Bibliothek] offers everyone unrestricted access to Germany’s cultural and scientific heritage, that is, access to millions of books, archived items, images, sculptures, pieces of music and other sound documents, as well as films and scores, from all over Germany.<br />
* [http://des.genealogy.net/eingabe-verlustlisten/search/index online transcription] for the WW1 casualty lists.<br />
<br />
===Online search===<br />
* [http://familie-beuss.de/Crawl GlobalGenSearch] - Genealogische Datenbank Familie Beuss<br />
<br />
==Italian resources==<br />
* [https://familysearch.org/italy Italian Genealogy] on FamilySearch.org<br />
* [http://www.cyndislist.com/italy Italy's Cyndi's List] of genealogy sites on internet.<br />
<br />
[[Category:Genealogy|All articles]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Talk:Other_genealogy_software-Freeware-Shareware-Commercial&diff=78630Talk:Other genealogy software-Freeware-Shareware-Commercial2020-05-28T08:47:43Z<p>GulliblePangolin: </p>
<hr />
<div>== Do we need this page ==<br />
<br />
I am no fan of this page, but it is clear that users will add this kind of page, so here is a framework, with the content User Adrian already posted in the wiki. <br />
[[User:Bmcage|bmcage]] 06:12, 19 March 2007 (EDT)<br />
::I was wondering why even have this page? Maybe merge with the others and copy the reasons to Gramps to the features page? [[User:GulliblePangolin|GulliblePangolin]] ([[User talk:GulliblePangolin|talk]]) 08:47, 28 May 2020 (UTC)<br />
<br />
== What should you do with this page ? ==<br />
<br />
OK this page exist but not register into a [http://www.gramps-project.org/wiki/index.php?title=Special:Uncategorizedpages category] ...</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Other_genealogy_software-Freeware-Shareware-Commercial&diff=78629Other genealogy software-Freeware-Shareware-Commercial2020-05-28T08:43:30Z<p>GulliblePangolin: </p>
<hr />
<div>{{languages|Other genealogy software-Freeware-Shareware-Commercial}}<br />
Freeware, shareware and commercial genealogy applications are available. <br />
<br />
{{man warn|You do not have full freedom when using this software, be aware of this!|We advise you '''read the copyright/license notice''' on what you can do. Some do not allow selling of output you create, some limit what you can do in the free version, ...}}<br />
<br />
The Gramps project supports [[Other genealogy software|open source genealogical software]], for the freedoms it offers the users. These freedoms are important for genealogists:<br />
*You fully own the content you create<br />
*No vendor lock-in due to use of obscure formats<br />
*Code sources available (fork or still active development if there is no more support for users)<br />
<br />
==FLOSS applications==<br />
[[Gramps:About|Gramps]] is [http://en.wikipedia.org/wiki/Free_and_open-source_software free/libre and open source], a list of other free/libre and open source applications: [[Other genealogy software]]<br />
<br />
==Freeware==<br />
Freeware are free programs under a generic license which is not considered Open Source.<br />
<br />
===GED Browser===<br />
====License====<br />
Free software. <br />
<br />
'''Catch''': to obtain it you need to leave mailing information. The software is released by a commercial firm that will use this information for its commercial products. The company has the right to change the license whenever they feel like it.<br />
<br />
====Platform====<br />
Windows<br />
<br />
====Description====<br />
[http://misbach.org/gedbrowser/ GED Browser] is a GEDCOM converter that produces HTML to display GEDCOM files. The description from the GED Browser website is as follows:<br />
<blockquote>The ultimate tool for converting your genealogy to HTML. No other tool uses such a unique and appealing design that displays both descendants and ancestors in one chart, giving virtually all the information found on a family group sheet. No other tool creates a "Site Map" view of your genealogy showing your entire genealogical tree in a way that graphically depicts the shape of your tree. With every individual represented and linked to their individual pedigree chart.</blockquote><br />
<br />
===The Dynamic Family Tree===<br />
====License====<br />
See http://dftcom2.co.uk/copyrght.html. A form of freeware, forbidden to modify or sell.<br />
<br />
'''Catch''': You can not sell trees made with the software.<br />
<br />
====Platform====<br />
Windows<br />
<br />
====Description====<br />
<br />
[http://dftcom2.co.uk/ The Dynamic Family Tree] is an MS windows GEDCOM compiler that produces Java based interface to display GEDCOM files in a tree structure. The description from the Dynamic Family Tree website is as follows:<br />
<blockquote><br />
# Displays fully graphical, interactive family tree on a web browser ([http://dftcom2.co.uk/web/index.html see example]).<br />
# Implemented as a Java Applet - very fast response to user actions.<br />
# Shows children, spouse and four generations of ancestors of the individual at the tree focus.<br />
# Individuals colour coded according to relationship to the tree owner<br />
# Display details by positioning mouse pointer over an individual.<br />
# Display Image (where available) of individual at the tree focus. </blockquote><br />
<br />
===Wintree/GWintree===<br />
====License====<br />
* Wintree is shareware, and free to download and try, with no obligation.<br />
* GWintree is freeware, but not open source.<br />
<br />
====Platform====<br />
* Wintree: Windows<br />
* GWintree: Mac OS X, Solaris, Linux<br />
<br />
====Description====<br />
* [http://www.wintree.plus.com/wintree.html Wintree] Wintree is an easy-to-use family tree program which provides facilities to manage genealogical data in the standard GEDCOM format, to create, view, edit and merge GEDCOM files, and to produce reports, charts and family trees.<br />
<br />
Family trees can be created showing all blood relatives - all ancestors, all descendants, and all descendants of all ancestors.<br />
<br />
[[File:GWintree.png|thumb|600px|GWintree under Ubuntu 10.10]]<br />
<br />
* [http://www.wintree.plus.com/gwintree.html GWintree] provides GEDCOM-based facilities to record, view, edit and merge genealogy data, and to produce reports, family trees showing all relatives, and other charts, The program is a port to Linux of Wintree v5.1, offering similar functionality.<br />
<br />
[[Category:Genealogy|All articles]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Debugging_Gramps&diff=78411Debugging Gramps2020-05-26T00:33:04Z<p>GulliblePangolin: </p>
<hr />
<div>{{man tip|Please note when doing debugging,|that the document mentions <code>src/gramps.py</code> and <code>Gramps.py</code>. Since you never have both in a single Gramps setup, please use <code>src/gramps.py</code> when running Gramps 3.x and earlier, and <code>Gramps.py</code> for 4.x and newer.}}<br />
<br />
An overview on how to debug Gramps.<br />
<br />
== Hard crash ==<br />
When a hard crash occurs, you typically have no idea where the crash occurs. It is important to know the line where the crash occurs. So if you are able to reproduce the crash, restart Gramps with the command:<br />
<br />
python -m trace -t Gramps.py<br />
<br />
This will usually generate vast terminal output and slow the system down for that, so redirecting output to a file is usually good:<br />
<br />
python -m trace -t Gramps.py >/tmp/trace.out<br />
<br />
Then check the file "/tmp/trace.out" and save if needed, or redirect to somewhere else in the earlier step.<br />
<br />
== Add debug statements ==<br />
Gramps is run with the optimize flag. <br />
<br />
python -O Gramps.py<br />
<br />
This gives you the option of adding debug statements. You can use the __debug__ variable or the assert statement for this. This allows us to add code to Gramps that will be printed out when Gramps runs without the optimize flag:<br />
<br />
python Gramps.py<br />
<br />
More info: [http://docs.python.org/reference/simple_stmts.html#the-assert-statement]<br />
<br />
== Use the log infrastructure == <br />
Gramps has built in the python log infrastructure. Gramps runs with logging level logging.DEBUG to stderrh.<br />
<br />
More info: [[Logging system]]<br />
<br />
Short: in your code add data to the logger with: log.warning(), log.error(), log.info()... <br />
<br />
Start Gramps with the --debug flag: <br />
python Gramps.py --debug="name_of_the_logger"<br />
<br />
This is useful when working in different parts, adding info output, and selecting on the command line with --debug the logger you want to see output with.<br />
<br />
== Use profiling ==<br />
Gramps has a convenience hook to allow you to do profiling. Profiling gives an overview how many times methods are called in a code fragment and how long each one took. It helps to find performance bottlenecks. <br />
<br />
An example usage:<br />
<br />
Add at the top of the file you want to use profiling:<br />
<br />
from gramps.gen.utils.debug import profile<br />
<br />
Then, suppose you want to profile a save function on one of the editors. The save is called due to a connect done in the method _connect_signals. So, change the connect to save to a new method testsave you make:<br />
<br />
#self.define_ok_button(self.top.get_widget("ok"), self.save)<br />
self.define_ok_button(self.top.get_widget("ok"), self.testsave)<br />
<br />
Now add the testsave function as follows, where you use the profile convenience function:<br />
<br />
def testsave(self, *obj):<br />
profile(self.save, *obj)<br />
<br />
Then run Gramps, every time you save, the profiler kicks in and prints to command line a report with the time for each function. <br />
<br />
So in short: replace the call to a function/method to calling profile with as first parameter the function/method, and other parameters the parameters of the function/method.<br />
<br />
That's it.<br />
<br />
See also [[GEPS_016:_Enhancing_Gramps_Processing_Speed]] for a sample of Profile Analysis.<br />
<br />
== Use the winpdb python debugger ==<br />
{{man note|Note|There are some issues with the winpdb debugger. For a workaround see bug ticket: {{bug|2564}} }}<br />
<br />
[https://pypi.org/project/winpdb-reborn/ Winpdb] (Ubuntu: sudo apt-get install winpdb) is a graphical interface for the python debugger. <br />
Start it with:<br />
<br />
winpdb Gramps.py<br />
<br />
[[Image:Winpdb.png|thumb|right|400px|Winpdb with Gramps loaded]]<br />
<br />
Now, in File menu, select 'Open Source', and open the source file you want to debug. Now all debug options are possible. Eg, go to a line in the file with the cursor, and click the ''run to line'' button. The debugger will run to that point, and left show you all defined local variables with their value, as well as the stack frame. <br />
<br />
Try it!<br />
<br />
{{-}}<br />
<br />
== Use gdb C debugger ==<br />
{{man note|Note |Knowledge of the C programming language required.}} <br />
<br />
With GObject introspection, much more can go wrong on a lower level, causing C errors. For these gdb can be used. You should install some debug libraries like libglib2.0-0-dbg, python-gobject-dbg, ... .<br />
<br />
Then, you start in a terminal gdb in the directory where Gramps.py is stored with<br />
<br />
gdb python<br />
<br />
You should see something like:<br />
<br />
<pre><br />
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2<br />
Copyright (C) 2010 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "x86_64-linux-gnu".<br />
For bug reporting instructions, please see:<br />
<http://www.gnu.org/software/gdb/bugs/>...<br />
Reading symbols from /usr/bin/python...Reading symbols from /usr/lib/debug/usr/bin/python2.7...done.<br />
done.<br />
(gdb) <br />
</pre><br />
<br />
You just type now:<br />
<br />
run Gramps.py<br />
<br />
and then navigate gramps to the '''segmentation fault'''. After that, you see something like<br />
<br />
Program received signal SIGSEGV, Segmentation fault.<br />
0x00007ffff5e7226b in g_type_check_value () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0<br />
(gdb)<br />
<br />
Now you request the backtrace, to see the code that leads to the error:<br />
<br />
(gdb) bt<br />
<br />
which will print the backtrace. You are now ready to use your C knowledge to fix the bug!<br />
<br />
=== Trace GObject/GTK warnings ===<br />
GTK has several possible warning levels, which might pop up on the terminal, without visible problems in Gramps. To trace these, do the following in the :<br />
<br />
gdb python<br />
<br />
and at the gdb prompt indicate to stop on log output:<br />
<br />
b g_log if log level < 32<br />
r Gramps.py<br />
<br />
Now Gramps will stop on serious messages, and you can use<br />
<br />
bt<br />
<br />
to get a backtrace of the C stack showing where the message originated and what called the function, etc. <br />
<br />
You can force a hard crash on warnings by setting G_DEBUG.<br />
<br />
For example:<br />
LC_ALL=C G_DEBUG=fatal-warnings python -m trace -t Gramps.py<br />
<br />
Different values possible: [https://developer.gnome.org/glib/2.60/glib-running.html]<br />
<br />
=== Learn More ===<br />
<br />
To learn more about debugging python and C debugging with gdb, see [https://web.archive.org/web/20180806035308/http://grapsus.net:80/blog/post/Low-level-Python-debugging-with-GDB] and [https://www.sourceware.org/gdb/onlinedocs/gdb.html].<br />
<br />
;Learning C tutorials<br />
The Python language implementation is written in the C programming language.<br />
<br />
*[http://www.learn-c.org/ Learn C the free interactive C tutorial.]<br />
*[https://learncodethehardway.org/c/ Learn C The Hard Way] ($)<br />
<br />
<br />
[[Category:Developers/Reference]]<br />
[[Category:Developers/Tutorials]]<br />
[[Category:Developers/General]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Debugging_Gramps&diff=78410Debugging Gramps2020-05-26T00:32:41Z<p>GulliblePangolin: </p>
<hr />
<div>{{man tip|Note when doing debugging,|Please note that the document mentions <code>src/gramps.py</code> and <code>Gramps.py</code>. Since you never have both in a single Gramps setup, please use <code>src/gramps.py</code> when running Gramps 3.x and earlier, and <code>Gramps.py</code> for 4.x and newer.}}<br />
<br />
An overview on how to debug Gramps.<br />
<br />
== Hard crash ==<br />
When a hard crash occurs, you typically have no idea where the crash occurs. It is important to know the line where the crash occurs. So if you are able to reproduce the crash, restart Gramps with the command:<br />
<br />
python -m trace -t Gramps.py<br />
<br />
This will usually generate vast terminal output and slow the system down for that, so redirecting output to a file is usually good:<br />
<br />
python -m trace -t Gramps.py >/tmp/trace.out<br />
<br />
Then check the file "/tmp/trace.out" and save if needed, or redirect to somewhere else in the earlier step.<br />
<br />
== Add debug statements ==<br />
Gramps is run with the optimize flag. <br />
<br />
python -O Gramps.py<br />
<br />
This gives you the option of adding debug statements. You can use the __debug__ variable or the assert statement for this. This allows us to add code to Gramps that will be printed out when Gramps runs without the optimize flag:<br />
<br />
python Gramps.py<br />
<br />
More info: [http://docs.python.org/reference/simple_stmts.html#the-assert-statement]<br />
<br />
== Use the log infrastructure == <br />
Gramps has built in the python log infrastructure. Gramps runs with logging level logging.DEBUG to stderrh.<br />
<br />
More info: [[Logging system]]<br />
<br />
Short: in your code add data to the logger with: log.warning(), log.error(), log.info()... <br />
<br />
Start Gramps with the --debug flag: <br />
python Gramps.py --debug="name_of_the_logger"<br />
<br />
This is useful when working in different parts, adding info output, and selecting on the command line with --debug the logger you want to see output with.<br />
<br />
== Use profiling ==<br />
Gramps has a convenience hook to allow you to do profiling. Profiling gives an overview how many times methods are called in a code fragment and how long each one took. It helps to find performance bottlenecks. <br />
<br />
An example usage:<br />
<br />
Add at the top of the file you want to use profiling:<br />
<br />
from gramps.gen.utils.debug import profile<br />
<br />
Then, suppose you want to profile a save function on one of the editors. The save is called due to a connect done in the method _connect_signals. So, change the connect to save to a new method testsave you make:<br />
<br />
#self.define_ok_button(self.top.get_widget("ok"), self.save)<br />
self.define_ok_button(self.top.get_widget("ok"), self.testsave)<br />
<br />
Now add the testsave function as follows, where you use the profile convenience function:<br />
<br />
def testsave(self, *obj):<br />
profile(self.save, *obj)<br />
<br />
Then run Gramps, every time you save, the profiler kicks in and prints to command line a report with the time for each function. <br />
<br />
So in short: replace the call to a function/method to calling profile with as first parameter the function/method, and other parameters the parameters of the function/method.<br />
<br />
That's it.<br />
<br />
See also [[GEPS_016:_Enhancing_Gramps_Processing_Speed]] for a sample of Profile Analysis.<br />
<br />
== Use the winpdb python debugger ==<br />
{{man note|Note|There are some issues with the winpdb debugger. For a workaround see bug ticket: {{bug|2564}} }}<br />
<br />
[https://pypi.org/project/winpdb-reborn/ Winpdb] (Ubuntu: sudo apt-get install winpdb) is a graphical interface for the python debugger. <br />
Start it with:<br />
<br />
winpdb Gramps.py<br />
<br />
[[Image:Winpdb.png|thumb|right|400px|Winpdb with Gramps loaded]]<br />
<br />
Now, in File menu, select 'Open Source', and open the source file you want to debug. Now all debug options are possible. Eg, go to a line in the file with the cursor, and click the ''run to line'' button. The debugger will run to that point, and left show you all defined local variables with their value, as well as the stack frame. <br />
<br />
Try it!<br />
<br />
{{-}}<br />
<br />
== Use gdb C debugger ==<br />
{{man note|Note |Knowledge of the C programming language required.}} <br />
<br />
With GObject introspection, much more can go wrong on a lower level, causing C errors. For these gdb can be used. You should install some debug libraries like libglib2.0-0-dbg, python-gobject-dbg, ... .<br />
<br />
Then, you start in a terminal gdb in the directory where Gramps.py is stored with<br />
<br />
gdb python<br />
<br />
You should see something like:<br />
<br />
<pre><br />
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2<br />
Copyright (C) 2010 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "x86_64-linux-gnu".<br />
For bug reporting instructions, please see:<br />
<http://www.gnu.org/software/gdb/bugs/>...<br />
Reading symbols from /usr/bin/python...Reading symbols from /usr/lib/debug/usr/bin/python2.7...done.<br />
done.<br />
(gdb) <br />
</pre><br />
<br />
You just type now:<br />
<br />
run Gramps.py<br />
<br />
and then navigate gramps to the '''segmentation fault'''. After that, you see something like<br />
<br />
Program received signal SIGSEGV, Segmentation fault.<br />
0x00007ffff5e7226b in g_type_check_value () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0<br />
(gdb)<br />
<br />
Now you request the backtrace, to see the code that leads to the error:<br />
<br />
(gdb) bt<br />
<br />
which will print the backtrace. You are now ready to use your C knowledge to fix the bug!<br />
<br />
=== Trace GObject/GTK warnings ===<br />
GTK has several possible warning levels, which might pop up on the terminal, without visible problems in Gramps. To trace these, do the following in the :<br />
<br />
gdb python<br />
<br />
and at the gdb prompt indicate to stop on log output:<br />
<br />
b g_log if log level < 32<br />
r Gramps.py<br />
<br />
Now Gramps will stop on serious messages, and you can use<br />
<br />
bt<br />
<br />
to get a backtrace of the C stack showing where the message originated and what called the function, etc. <br />
<br />
You can force a hard crash on warnings by setting G_DEBUG.<br />
<br />
For example:<br />
LC_ALL=C G_DEBUG=fatal-warnings python -m trace -t Gramps.py<br />
<br />
Different values possible: [https://developer.gnome.org/glib/2.60/glib-running.html]<br />
<br />
=== Learn More ===<br />
<br />
To learn more about debugging python and C debugging with gdb, see [https://web.archive.org/web/20180806035308/http://grapsus.net:80/blog/post/Low-level-Python-debugging-with-GDB] and [https://www.sourceware.org/gdb/onlinedocs/gdb.html].<br />
<br />
;Learning C tutorials<br />
The Python language implementation is written in the C programming language.<br />
<br />
*[http://www.learn-c.org/ Learn C the free interactive C tutorial.]<br />
*[https://learncodethehardway.org/c/ Learn C The Hard Way] ($)<br />
<br />
<br />
[[Category:Developers/Reference]]<br />
[[Category:Developers/Tutorials]]<br />
[[Category:Developers/General]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Database_Formats&diff=78409Database Formats2020-05-26T00:25:31Z<p>GulliblePangolin: /* History */</p>
<hr />
<div>{{languages|Database Formats}}<br />
==History==<br />
<br />
Gramps default data format has evolved over time. Each major change in format usually results in an increase in the major version number.<br />
<br />
=== Table of Changes ===<br />
<br />
This table lists the database changes for each version.<br />
* See also [[Gramps XML]] - for a more detailed summary.<br />
<br />
{|{{prettytable}} <br />
!Gramps<br />
!Database<br />
!Changes from previous version<br />
|-<br />
|Gramps 5.1<br />
|18<br />
|<br />
* SQLite is default<br />
|-<br />
|Gramps 5.0<br />
|18<br />
|<br />
* Database backends become plugins<br />
* BSDDB is default<br />
* DB-API (SQL) is tested as viable replacement<br />
* Convert default handle to string<br />
|-<br />
|Gramps 4.2<br />
|18<br />
|<br />
* added PlaceNames (with Date and Language) Place<br />
|- <br />
|Gramps 4.1<br />
|17<br />
|<br />
* added Tags to Event, Place, Repository, Source, and Citation<br />
* added alternate names to Place<br />
* Source.data became SourceAttributes<br />
* Added optional support for checksum on Media object<br />
* Added PlaceRef and Place Hierarchies<br />
|- <br />
|Gramps 3.4 - 4.0<br />
|16<br />
|<br />
* converted SourceRef to new Citation object<br />
* Source and Citation objects gained a private flag<br />
|- <br />
|Gramps 3.1 - 3.3<br />
|15<br />
|<br />
* added Tags to Person, Family, and Note<br />
* added Surname list<br />
* removed Marker <br />
|- <br />
|Gramps 3.0<br />
|14<br />
|<br />
* added newyear to Dates<br />
* Replace plain text with StyledText in Notes<br />
|- <br />
|Gramps 2.x<br />
|13<br />
|<br />
* changed name formats <br />
|- <br />
|Gramps 1.x<br />
|N/A<br />
|<br />
* Used XML directly<br />
|}<br />
<br />
===Gramps 1.0 and earlier===<br />
<br />
Gramps 1.0 used XML as its default format. This format is portable and easily read by both computers and people. It has two major issues that caused problems when it was used as the default format.<br />
<br />
* Slow to load and save. The entire file had to be parsed to load the data, and parsing XML is not fast. Similarly, to save any changes, the entire file had to be written. People with larger databases (thousands of persons) found the load and save times to be unusable.<br />
<br />
* Consumes a lot of memory. The XML format required that all data be loaded and stored in memory. Larger databases could consume all memory on the system and as a result bring the system to a virtual halt.<br />
<br />
===Gramps 2.0===<br />
<br />
To solve the capacity issues, Gramps 2.0 switched to using the Berkeley database, using the ".grdb" extension to identify the file. All database information was stored in this file. This resolved both the load/save time issues and the memory consumption issues. Using a real database backend allowed us to only load the data into memory when we needed it.<br />
<br />
The grdb format was a significant step forward for Gramps. However, it was susceptible to data corruption. Since data commits were not atomic (all related changes saved at once), data could get corrupted if an error occurred while a change was being made.<br />
<br />
===Gramps 2.2===<br />
<br />
Gramps 2.2 started using the transaction capability of the Berkeley database. This feature ensures that all related data is committed at once. So, if an error occurs while that data is being saved, the database remains intact. Either the entire set of changes makes it to the database, or none of the changes make it.<br />
<br />
The problem with the approach in 2.2 is that a single file (the grdb file) is no longer enough for the Berkeley database to handle the data. An "environment" directory is needed to store the transactions log files. A place was needed to keep these files so that the user would not delete them. An environment directory under the ~/.gramps directory was chosen for this. The log files are mapped to the database using the path name of the original grdb file.<br />
<br />
This works very well as long as the file is never moved. If the user renames the file, restores a backup of the file, or copies it to another machine, [[Recover_corrupted_family_tree#What_causes_this_corruption.3F_2|the file will no longer work]], since it would no longer correlate to the log files stored under ~/.gramps.<br />
<br />
===Gramps 3.0===<br />
<br />
A new approach was taken with Gramps 3.0. While the Berkeley database is still used, the user will no longer see a file. Instead of the actual database file, user opens a symbolic database name. This name will map to a subdirectory under ~/.gramps directory which contains all the needed database files.<br />
<br />
Since all the files will be in the same directory, advanced users can make a backup of the entire directory, preserving the entire data. New users, who may not be familiar with the Linux filesystem, will not have to worry about finding their database, since a new Family Tree Manager will replace the old Open File dialog.<br />
<br />
====Family Tree Manager====<br />
<br />
The new Family Tree Manager replaces the File Open dialog. Version 3.0 does not work on files, but on Family Tree Databases. Since there is no file to open, a file open dialog makes no sense. The Open button has been replaced with a Family Trees button. Clicking this button brings up the Family Tree Manager, shown below.<br />
<br />
[[Image:ManageFamilyTrees-40.png]]<br />
<br />
The Family Tree Manager allows the user to create a new database, rename an existing database, delete a database, or load a database. All databases appear in the list, so the user does not need to worry about where the databases are located. If a database is open, an icon will appear next to the name.<br />
<br />
===== Versions =====<br />
<br />
If the RCS revision control system is installed on your system, Gramps allows you to archive specified versions of your database. To save a version, open the Family Tree Manager and select the opened database. Simply clicking on the Archive button will save the current version to the revision control system. If a database has one or more saved versions, the databases appear as a tree view, with the available versions displayed under them.<br />
<br />
[[Image:Dbmanager03.png]]<br />
<br />
In this example, the ''Gramps Example'' database has two versions which have been saved. These versions are saved snapshots of your database contents.<br />
<br />
The advantage of storing versions is that you can go back to one of these saved versions. To select a version to restore, select the version and click on the Restore button.<br />
<br />
[[File:ManageFamilyTrees-Archive-Selected-to-Extract-example-50.png|Selecting a version to restore]]<br />
<br />
Gramps will extract the version into a new database. The database name is based on the original database name and the revision name.<br />
<br />
[[File:ManageFamilyTrees-Archive-Extracted-version-highlighted-example-50.png|Restored version]]<br />
<br />
Versions may be deleted and renamed.<br />
<br />
===== Multiple users =====<br />
<br />
Unlike previous versions, Gramps 3.0 supports limited sharing of databases. Multiple users may edit the same database, just not at the same time. The Family Tree Manager will identify a database that is open for another user, and you will not be able to load the database until the other user has closed the database.<br />
<br />
[[Image:Dbmanager06.png]]<br />
<br />
===== Repairing a Corrupt Database =====<br />
<br />
On the odd chance that database corruption occurs, the Family Tree Manager will show the corrupted file with an Error icon next to it. If this database is selected, a Repair button will appear (as seen below).<br />
<br />
[[File:FamilyTreesManager-Dialog-ShowingRedErrorStatusIcon-Sample-50.png]]<br />
<br />
Clicking the repair button will rebuild the database from the backup files that are automatically created on exit.<br />
<br />
====Automatic Backup Files====<br />
<br />
To protect against file corruption problems in the Berkeley database, Gramps 3.0 will generate a backup file at exit if any data has changed.<br />
<br />
Unlike in Gramps 2.2, the backup files are not in XML format. The new backup files are a dump of the database tables. This allows the data to be saved quickly. One backup file exists for each primary table in the database. The backup files are not visible to the user, being held in the database directory.<br />
<br />
==== Why no simultaneous access? ====<br />
<br />
From time to time people want to use Gramps for collaborative research, and are then stopped as Gramps does not allow simultaneous access. That is, you can simultaneously access the database, but this typically results in corrupt data, destroying your database. <br />
<br />
The motivation for this is the following:<br />
#We would need a server/client infrastructure, like eg MySQL. However, this is also why MySQL is non-trivial for most users to maintain. We get into system startup files, gramps daemons running, and a whole mess of other stuff. And when you consider that probably under 5% of the users would be interested in something like this, we have to wonder about our return on investment. Is our time more valuable working on other stuff?<br />
#Who to maintain this code? The core developers don't need this feature. Somebody should join the team to make this happen.<br />
<br />
Technically, BSDDB can be made to work with a server environment. However, in Gramps we give the <code>env.open()</code> the <code>DB_PRIVATE flag</code>. The docs say:<br />
;<code>DB_PRIVATE</code>:Specify that the environment will only be accessed by a single process (although that process may be multithreaded). This flag has two effects on the Berkeley DB environment. First, all underlying data structures are allocated from per-process memory instead of from shared memory that is potentially accessible to more than a single process. Second, mutexes are only configured to work between threads.<br />
<br />
:This flag should not be specified if more than a single process is accessing the environment because it is likely to cause database corruption and unpredictable behavior. For example, if both a server application and the Berkeley DB utility db_stat are expected to access the environment, the DB_PRIVATE flag should not be specified.<br />
<br />
:Source: [http://pybsddb.sourceforge.net/api_c/env_open.html DB_ENV->open]<br />
<br />
Note however that consecutive access from different places to the same underlying database is possible with Gramps 3.0, so a collaboration based on time sharing (using different hours to input data in Gramps) is possible.<br />
<br />
===Gramps 5.0===<br />
<br />
In Gramps 5.0, the database backend became a plugin. This version still uses the same backend as previous versions; however, an new backend is introduced called "DB-API". This is a SQL-based backend. After testing was successful, Gramps 5.1 released with the SQlite backend as the default.<br />
<br />
You can read more about this back in [[DB-API Database Backend]].<br />
<br />
==See also==<br />
* [[Gramps XML]]<br />
* [[Generate XML]]<br />
* [[GEDCOM]]<br />
* [[Gramps and GEDCOM]]<br />
* [[Gramps Old database]]<br />
* [[Previous releases of Gramps]]<br />
* [[Using_database_API|Programmer's Introduction to the Gramps database API]]<br />
<br />
[[Category:Developers/General]]<br />
[[Category:Developers/Reference]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Database_Formats&diff=78408Database Formats2020-05-26T00:23:22Z<p>GulliblePangolin: /* Table of Changes */</p>
<hr />
<div>{{languages|Database Formats}}<br />
==History==<br />
<br />
Gramps default data format has evolved over time. Each major change in format usually results in an increase in the major version number.<br />
<br />
* See also [[Gramps XML]]<br />
<br />
=== Table of Changes ===<br />
<br />
This table lists the database changes for each version.<br />
<br />
{|{{prettytable}} <br />
!Gramps<br />
!Database<br />
!Changes from previous version<br />
|-<br />
|Gramps 5.1<br />
|18<br />
|<br />
* SQLite is default<br />
|-<br />
|Gramps 5.0<br />
|18<br />
|<br />
* Database backends become plugins<br />
* BSDDB is default<br />
* DB-API (SQL) is tested as viable replacement<br />
* Convert default handle to string<br />
|-<br />
|Gramps 4.2<br />
|18<br />
|<br />
* added PlaceNames (with Date and Language) Place<br />
|- <br />
|Gramps 4.1<br />
|17<br />
|<br />
* added Tags to Event, Place, Repository, Source, and Citation<br />
* added alternate names to Place<br />
* Source.data became SourceAttributes<br />
* Added optional support for checksum on Media object<br />
* Added PlaceRef and Place Hierarchies<br />
|- <br />
|Gramps 3.4 - 4.0<br />
|16<br />
|<br />
* converted SourceRef to new Citation object<br />
* Source and Citation objects gained a private flag<br />
|- <br />
|Gramps 3.1 - 3.3<br />
|15<br />
|<br />
* added Tags to Person, Family, and Note<br />
* added Surname list<br />
* removed Marker <br />
|- <br />
|Gramps 3.0<br />
|14<br />
|<br />
* added newyear to Dates<br />
* Replace plain text with StyledText in Notes<br />
|- <br />
|Gramps 2.x<br />
|13<br />
|<br />
* changed name formats <br />
|- <br />
|Gramps 1.x<br />
|N/A<br />
|<br />
* Used XML directly<br />
|}<br />
<br />
===Gramps 1.0 and earlier===<br />
<br />
Gramps 1.0 used XML as its default format. This format is portable and easily read by both computers and people. It has two major issues that caused problems when it was used as the default format.<br />
<br />
* Slow to load and save. The entire file had to be parsed to load the data, and parsing XML is not fast. Similarly, to save any changes, the entire file had to be written. People with larger databases (thousands of persons) found the load and save times to be unusable.<br />
<br />
* Consumes a lot of memory. The XML format required that all data be loaded and stored in memory. Larger databases could consume all memory on the system and as a result bring the system to a virtual halt.<br />
<br />
===Gramps 2.0===<br />
<br />
To solve the capacity issues, Gramps 2.0 switched to using the Berkeley database, using the ".grdb" extension to identify the file. All database information was stored in this file. This resolved both the load/save time issues and the memory consumption issues. Using a real database backend allowed us to only load the data into memory when we needed it.<br />
<br />
The grdb format was a significant step forward for Gramps. However, it was susceptible to data corruption. Since data commits were not atomic (all related changes saved at once), data could get corrupted if an error occurred while a change was being made.<br />
<br />
===Gramps 2.2===<br />
<br />
Gramps 2.2 started using the transaction capability of the Berkeley database. This feature ensures that all related data is committed at once. So, if an error occurs while that data is being saved, the database remains intact. Either the entire set of changes makes it to the database, or none of the changes make it.<br />
<br />
The problem with the approach in 2.2 is that a single file (the grdb file) is no longer enough for the Berkeley database to handle the data. An "environment" directory is needed to store the transactions log files. A place was needed to keep these files so that the user would not delete them. An environment directory under the ~/.gramps directory was chosen for this. The log files are mapped to the database using the path name of the original grdb file.<br />
<br />
This works very well as long as the file is never moved. If the user renames the file, restores a backup of the file, or copies it to another machine, [[Recover_corrupted_family_tree#What_causes_this_corruption.3F_2|the file will no longer work]], since it would no longer correlate to the log files stored under ~/.gramps.<br />
<br />
===Gramps 3.0===<br />
<br />
A new approach was taken with Gramps 3.0. While the Berkeley database is still used, the user will no longer see a file. Instead of the actual database file, user opens a symbolic database name. This name will map to a subdirectory under ~/.gramps directory which contains all the needed database files.<br />
<br />
Since all the files will be in the same directory, advanced users can make a backup of the entire directory, preserving the entire data. New users, who may not be familiar with the Linux filesystem, will not have to worry about finding their database, since a new Family Tree Manager will replace the old Open File dialog.<br />
<br />
====Family Tree Manager====<br />
<br />
The new Family Tree Manager replaces the File Open dialog. Version 3.0 does not work on files, but on Family Tree Databases. Since there is no file to open, a file open dialog makes no sense. The Open button has been replaced with a Family Trees button. Clicking this button brings up the Family Tree Manager, shown below.<br />
<br />
[[Image:ManageFamilyTrees-40.png]]<br />
<br />
The Family Tree Manager allows the user to create a new database, rename an existing database, delete a database, or load a database. All databases appear in the list, so the user does not need to worry about where the databases are located. If a database is open, an icon will appear next to the name.<br />
<br />
===== Versions =====<br />
<br />
If the RCS revision control system is installed on your system, Gramps allows you to archive specified versions of your database. To save a version, open the Family Tree Manager and select the opened database. Simply clicking on the Archive button will save the current version to the revision control system. If a database has one or more saved versions, the databases appear as a tree view, with the available versions displayed under them.<br />
<br />
[[Image:Dbmanager03.png]]<br />
<br />
In this example, the ''Gramps Example'' database has two versions which have been saved. These versions are saved snapshots of your database contents.<br />
<br />
The advantage of storing versions is that you can go back to one of these saved versions. To select a version to restore, select the version and click on the Restore button.<br />
<br />
[[File:ManageFamilyTrees-Archive-Selected-to-Extract-example-50.png|Selecting a version to restore]]<br />
<br />
Gramps will extract the version into a new database. The database name is based on the original database name and the revision name.<br />
<br />
[[File:ManageFamilyTrees-Archive-Extracted-version-highlighted-example-50.png|Restored version]]<br />
<br />
Versions may be deleted and renamed.<br />
<br />
===== Multiple users =====<br />
<br />
Unlike previous versions, Gramps 3.0 supports limited sharing of databases. Multiple users may edit the same database, just not at the same time. The Family Tree Manager will identify a database that is open for another user, and you will not be able to load the database until the other user has closed the database.<br />
<br />
[[Image:Dbmanager06.png]]<br />
<br />
===== Repairing a Corrupt Database =====<br />
<br />
On the odd chance that database corruption occurs, the Family Tree Manager will show the corrupted file with an Error icon next to it. If this database is selected, a Repair button will appear (as seen below).<br />
<br />
[[File:FamilyTreesManager-Dialog-ShowingRedErrorStatusIcon-Sample-50.png]]<br />
<br />
Clicking the repair button will rebuild the database from the backup files that are automatically created on exit.<br />
<br />
====Automatic Backup Files====<br />
<br />
To protect against file corruption problems in the Berkeley database, Gramps 3.0 will generate a backup file at exit if any data has changed.<br />
<br />
Unlike in Gramps 2.2, the backup files are not in XML format. The new backup files are a dump of the database tables. This allows the data to be saved quickly. One backup file exists for each primary table in the database. The backup files are not visible to the user, being held in the database directory.<br />
<br />
==== Why no simultaneous access? ====<br />
<br />
From time to time people want to use Gramps for collaborative research, and are then stopped as Gramps does not allow simultaneous access. That is, you can simultaneously access the database, but this typically results in corrupt data, destroying your database. <br />
<br />
The motivation for this is the following:<br />
#We would need a server/client infrastructure, like eg MySQL. However, this is also why MySQL is non-trivial for most users to maintain. We get into system startup files, gramps daemons running, and a whole mess of other stuff. And when you consider that probably under 5% of the users would be interested in something like this, we have to wonder about our return on investment. Is our time more valuable working on other stuff?<br />
#Who to maintain this code? The core developers don't need this feature. Somebody should join the team to make this happen.<br />
<br />
Technically, BSDDB can be made to work with a server environment. However, in Gramps we give the <code>env.open()</code> the <code>DB_PRIVATE flag</code>. The docs say:<br />
;<code>DB_PRIVATE</code>:Specify that the environment will only be accessed by a single process (although that process may be multithreaded). This flag has two effects on the Berkeley DB environment. First, all underlying data structures are allocated from per-process memory instead of from shared memory that is potentially accessible to more than a single process. Second, mutexes are only configured to work between threads.<br />
<br />
:This flag should not be specified if more than a single process is accessing the environment because it is likely to cause database corruption and unpredictable behavior. For example, if both a server application and the Berkeley DB utility db_stat are expected to access the environment, the DB_PRIVATE flag should not be specified.<br />
<br />
:Source: [http://pybsddb.sourceforge.net/api_c/env_open.html DB_ENV->open]<br />
<br />
Note however that consecutive access from different places to the same underlying database is possible with Gramps 3.0, so a collaboration based on time sharing (using different hours to input data in Gramps) is possible.<br />
<br />
===Gramps 5.0===<br />
<br />
In Gramps 5.0, the database backend became a plugin. This version still uses the same backend as previous versions; however, an new backend is introduced called "DB-API". This is a SQL-based backend. After testing was successful, Gramps 5.1 released with the SQlite backend as the default.<br />
<br />
You can read more about this back in [[DB-API Database Backend]].<br />
<br />
==See also==<br />
* [[Gramps XML]]<br />
* [[Generate XML]]<br />
* [[GEDCOM]]<br />
* [[Gramps and GEDCOM]]<br />
* [[Gramps Old database]]<br />
* [[Previous releases of Gramps]]<br />
* [[Using_database_API|Programmer's Introduction to the Gramps database API]]<br />
<br />
[[Category:Developers/General]]<br />
[[Category:Developers/Reference]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Database_Formats&diff=78407Database Formats2020-05-26T00:21:45Z<p>GulliblePangolin: </p>
<hr />
<div>{{languages|Database Formats}}<br />
==History==<br />
<br />
Gramps default data format has evolved over time. Each major change in format usually results in an increase in the major version number.<br />
<br />
* See also [[Gramps XML]]<br />
<br />
=== Table of Changes ===<br />
<br />
This table lists the database changes for each version.<br />
<br />
{|{{prettytable}} <br />
!Gramps<br />
!Database<br />
!Changes from previous version<br />
|-<br />
|Gramps 5.1<br />
|18<br />
|<br />
* SQLite is default<br />
|-<br />
|Gramps 5.0<br />
|18<br />
|<br />
* Database backends become plugins<br />
* BSDDB is default<br />
* DB-API (SQL) is tested as viable replacement<br />
* Convert default handle to string<br />
|-<br />
|Gramps 4.2<br />
|18<br />
|<br />
* added PlaceNames (with Date and Language) Place<br />
|- <br />
|Gramps 4.1<br />
|17<br />
|<br />
* added Tags to Event, Place, Repository, Source, and Citation<br />
* added alternate names to Place<br />
* Source.data became SourceAttributes<br />
* Added optional support for checksum on Media object<br />
* Added PlaceRef and Place Hierarchies<br />
|- <br />
|Gramps 3.4 - 4.0<br />
|16<br />
|<br />
* converted SourceRef to new Citation object<br />
* Source and Citation objects gained a private flag<br />
|- <br />
|Gramps 3.1 - 3.3<br />
|15<br />
|<br />
* added Tags to Person, Family, and Note<br />
* added Surname list<br />
* removed Marker <br />
|- <br />
|Gramps 3.0<br />
|14<br />
|<br />
* added newyear to Dates<br />
* Replace plain text with StyledText in Notes<br />
|- <br />
|Gramps 2.x<br />
|13<br />
|<br />
* changed name formats <br />
|}<br />
<br />
===Gramps 1.0 and earlier===<br />
<br />
Gramps 1.0 used XML as its default format. This format is portable and easily read by both computers and people. It has two major issues that caused problems when it was used as the default format.<br />
<br />
* Slow to load and save. The entire file had to be parsed to load the data, and parsing XML is not fast. Similarly, to save any changes, the entire file had to be written. People with larger databases (thousands of persons) found the load and save times to be unusable.<br />
<br />
* Consumes a lot of memory. The XML format required that all data be loaded and stored in memory. Larger databases could consume all memory on the system and as a result bring the system to a virtual halt.<br />
<br />
===Gramps 2.0===<br />
<br />
To solve the capacity issues, Gramps 2.0 switched to using the Berkeley database, using the ".grdb" extension to identify the file. All database information was stored in this file. This resolved both the load/save time issues and the memory consumption issues. Using a real database backend allowed us to only load the data into memory when we needed it.<br />
<br />
The grdb format was a significant step forward for Gramps. However, it was susceptible to data corruption. Since data commits were not atomic (all related changes saved at once), data could get corrupted if an error occurred while a change was being made.<br />
<br />
===Gramps 2.2===<br />
<br />
Gramps 2.2 started using the transaction capability of the Berkeley database. This feature ensures that all related data is committed at once. So, if an error occurs while that data is being saved, the database remains intact. Either the entire set of changes makes it to the database, or none of the changes make it.<br />
<br />
The problem with the approach in 2.2 is that a single file (the grdb file) is no longer enough for the Berkeley database to handle the data. An "environment" directory is needed to store the transactions log files. A place was needed to keep these files so that the user would not delete them. An environment directory under the ~/.gramps directory was chosen for this. The log files are mapped to the database using the path name of the original grdb file.<br />
<br />
This works very well as long as the file is never moved. If the user renames the file, restores a backup of the file, or copies it to another machine, [[Recover_corrupted_family_tree#What_causes_this_corruption.3F_2|the file will no longer work]], since it would no longer correlate to the log files stored under ~/.gramps.<br />
<br />
===Gramps 3.0===<br />
<br />
A new approach was taken with Gramps 3.0. While the Berkeley database is still used, the user will no longer see a file. Instead of the actual database file, user opens a symbolic database name. This name will map to a subdirectory under ~/.gramps directory which contains all the needed database files.<br />
<br />
Since all the files will be in the same directory, advanced users can make a backup of the entire directory, preserving the entire data. New users, who may not be familiar with the Linux filesystem, will not have to worry about finding their database, since a new Family Tree Manager will replace the old Open File dialog.<br />
<br />
====Family Tree Manager====<br />
<br />
The new Family Tree Manager replaces the File Open dialog. Version 3.0 does not work on files, but on Family Tree Databases. Since there is no file to open, a file open dialog makes no sense. The Open button has been replaced with a Family Trees button. Clicking this button brings up the Family Tree Manager, shown below.<br />
<br />
[[Image:ManageFamilyTrees-40.png]]<br />
<br />
The Family Tree Manager allows the user to create a new database, rename an existing database, delete a database, or load a database. All databases appear in the list, so the user does not need to worry about where the databases are located. If a database is open, an icon will appear next to the name.<br />
<br />
===== Versions =====<br />
<br />
If the RCS revision control system is installed on your system, Gramps allows you to archive specified versions of your database. To save a version, open the Family Tree Manager and select the opened database. Simply clicking on the Archive button will save the current version to the revision control system. If a database has one or more saved versions, the databases appear as a tree view, with the available versions displayed under them.<br />
<br />
[[Image:Dbmanager03.png]]<br />
<br />
In this example, the ''Gramps Example'' database has two versions which have been saved. These versions are saved snapshots of your database contents.<br />
<br />
The advantage of storing versions is that you can go back to one of these saved versions. To select a version to restore, select the version and click on the Restore button.<br />
<br />
[[File:ManageFamilyTrees-Archive-Selected-to-Extract-example-50.png|Selecting a version to restore]]<br />
<br />
Gramps will extract the version into a new database. The database name is based on the original database name and the revision name.<br />
<br />
[[File:ManageFamilyTrees-Archive-Extracted-version-highlighted-example-50.png|Restored version]]<br />
<br />
Versions may be deleted and renamed.<br />
<br />
===== Multiple users =====<br />
<br />
Unlike previous versions, Gramps 3.0 supports limited sharing of databases. Multiple users may edit the same database, just not at the same time. The Family Tree Manager will identify a database that is open for another user, and you will not be able to load the database until the other user has closed the database.<br />
<br />
[[Image:Dbmanager06.png]]<br />
<br />
===== Repairing a Corrupt Database =====<br />
<br />
On the odd chance that database corruption occurs, the Family Tree Manager will show the corrupted file with an Error icon next to it. If this database is selected, a Repair button will appear (as seen below).<br />
<br />
[[File:FamilyTreesManager-Dialog-ShowingRedErrorStatusIcon-Sample-50.png]]<br />
<br />
Clicking the repair button will rebuild the database from the backup files that are automatically created on exit.<br />
<br />
====Automatic Backup Files====<br />
<br />
To protect against file corruption problems in the Berkeley database, Gramps 3.0 will generate a backup file at exit if any data has changed.<br />
<br />
Unlike in Gramps 2.2, the backup files are not in XML format. The new backup files are a dump of the database tables. This allows the data to be saved quickly. One backup file exists for each primary table in the database. The backup files are not visible to the user, being held in the database directory.<br />
<br />
==== Why no simultaneous access? ====<br />
<br />
From time to time people want to use Gramps for collaborative research, and are then stopped as Gramps does not allow simultaneous access. That is, you can simultaneously access the database, but this typically results in corrupt data, destroying your database. <br />
<br />
The motivation for this is the following:<br />
#We would need a server/client infrastructure, like eg MySQL. However, this is also why MySQL is non-trivial for most users to maintain. We get into system startup files, gramps daemons running, and a whole mess of other stuff. And when you consider that probably under 5% of the users would be interested in something like this, we have to wonder about our return on investment. Is our time more valuable working on other stuff?<br />
#Who to maintain this code? The core developers don't need this feature. Somebody should join the team to make this happen.<br />
<br />
Technically, BSDDB can be made to work with a server environment. However, in Gramps we give the <code>env.open()</code> the <code>DB_PRIVATE flag</code>. The docs say:<br />
;<code>DB_PRIVATE</code>:Specify that the environment will only be accessed by a single process (although that process may be multithreaded). This flag has two effects on the Berkeley DB environment. First, all underlying data structures are allocated from per-process memory instead of from shared memory that is potentially accessible to more than a single process. Second, mutexes are only configured to work between threads.<br />
<br />
:This flag should not be specified if more than a single process is accessing the environment because it is likely to cause database corruption and unpredictable behavior. For example, if both a server application and the Berkeley DB utility db_stat are expected to access the environment, the DB_PRIVATE flag should not be specified.<br />
<br />
:Source: [http://pybsddb.sourceforge.net/api_c/env_open.html DB_ENV->open]<br />
<br />
Note however that consecutive access from different places to the same underlying database is possible with Gramps 3.0, so a collaboration based on time sharing (using different hours to input data in Gramps) is possible.<br />
<br />
===Gramps 5.0===<br />
<br />
In Gramps 5.0, the database backend became a plugin. This version still uses the same backend as previous versions; however, an new backend is introduced called "DB-API". This is a SQL-based backend. After testing was successful, Gramps 5.1 released with the SQlite backend as the default.<br />
<br />
You can read more about this back in [[DB-API Database Backend]].<br />
<br />
==See also==<br />
* [[Gramps XML]]<br />
* [[Generate XML]]<br />
* [[GEDCOM]]<br />
* [[Gramps and GEDCOM]]<br />
* [[Gramps Old database]]<br />
* [[Previous releases of Gramps]]<br />
* [[Using_database_API|Programmer's Introduction to the Gramps database API]]<br />
<br />
[[Category:Developers/General]]<br />
[[Category:Developers/Reference]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Database_Formats&diff=78406Database Formats2020-05-26T00:21:34Z<p>GulliblePangolin: </p>
<hr />
<div>{{languages|Database Formats}}<br />
==History==<br />
<br />
Gramps default data format has evolved over time. Each major change in format usually results in an increase in the major version number.<br />
<br />
* See also [[Gramps XML]]<br />
<br />
== Table of Changes ==<br />
<br />
This table lists the database changes for each version.<br />
<br />
{|{{prettytable}} <br />
!Gramps<br />
!Database<br />
!Changes from previous version<br />
|-<br />
|Gramps 5.1<br />
|18<br />
|<br />
* SQLite is default<br />
|-<br />
|Gramps 5.0<br />
|18<br />
|<br />
* Database backends become plugins<br />
* BSDDB is default<br />
* DB-API (SQL) is tested as viable replacement<br />
* Convert default handle to string<br />
|-<br />
|Gramps 4.2<br />
|18<br />
|<br />
* added PlaceNames (with Date and Language) Place<br />
|- <br />
|Gramps 4.1<br />
|17<br />
|<br />
* added Tags to Event, Place, Repository, Source, and Citation<br />
* added alternate names to Place<br />
* Source.data became SourceAttributes<br />
* Added optional support for checksum on Media object<br />
* Added PlaceRef and Place Hierarchies<br />
|- <br />
|Gramps 3.4 - 4.0<br />
|16<br />
|<br />
* converted SourceRef to new Citation object<br />
* Source and Citation objects gained a private flag<br />
|- <br />
|Gramps 3.1 - 3.3<br />
|15<br />
|<br />
* added Tags to Person, Family, and Note<br />
* added Surname list<br />
* removed Marker <br />
|- <br />
|Gramps 3.0<br />
|14<br />
|<br />
* added newyear to Dates<br />
* Replace plain text with StyledText in Notes<br />
|- <br />
|Gramps 2.x<br />
|13<br />
|<br />
* changed name formats <br />
|}<br />
<br />
===Gramps 1.0 and earlier===<br />
<br />
Gramps 1.0 used XML as its default format. This format is portable and easily read by both computers and people. It has two major issues that caused problems when it was used as the default format.<br />
<br />
* Slow to load and save. The entire file had to be parsed to load the data, and parsing XML is not fast. Similarly, to save any changes, the entire file had to be written. People with larger databases (thousands of persons) found the load and save times to be unusable.<br />
<br />
* Consumes a lot of memory. The XML format required that all data be loaded and stored in memory. Larger databases could consume all memory on the system and as a result bring the system to a virtual halt.<br />
<br />
===Gramps 2.0===<br />
<br />
To solve the capacity issues, Gramps 2.0 switched to using the Berkeley database, using the ".grdb" extension to identify the file. All database information was stored in this file. This resolved both the load/save time issues and the memory consumption issues. Using a real database backend allowed us to only load the data into memory when we needed it.<br />
<br />
The grdb format was a significant step forward for Gramps. However, it was susceptible to data corruption. Since data commits were not atomic (all related changes saved at once), data could get corrupted if an error occurred while a change was being made.<br />
<br />
===Gramps 2.2===<br />
<br />
Gramps 2.2 started using the transaction capability of the Berkeley database. This feature ensures that all related data is committed at once. So, if an error occurs while that data is being saved, the database remains intact. Either the entire set of changes makes it to the database, or none of the changes make it.<br />
<br />
The problem with the approach in 2.2 is that a single file (the grdb file) is no longer enough for the Berkeley database to handle the data. An "environment" directory is needed to store the transactions log files. A place was needed to keep these files so that the user would not delete them. An environment directory under the ~/.gramps directory was chosen for this. The log files are mapped to the database using the path name of the original grdb file.<br />
<br />
This works very well as long as the file is never moved. If the user renames the file, restores a backup of the file, or copies it to another machine, [[Recover_corrupted_family_tree#What_causes_this_corruption.3F_2|the file will no longer work]], since it would no longer correlate to the log files stored under ~/.gramps.<br />
<br />
===Gramps 3.0===<br />
<br />
A new approach was taken with Gramps 3.0. While the Berkeley database is still used, the user will no longer see a file. Instead of the actual database file, user opens a symbolic database name. This name will map to a subdirectory under ~/.gramps directory which contains all the needed database files.<br />
<br />
Since all the files will be in the same directory, advanced users can make a backup of the entire directory, preserving the entire data. New users, who may not be familiar with the Linux filesystem, will not have to worry about finding their database, since a new Family Tree Manager will replace the old Open File dialog.<br />
<br />
====Family Tree Manager====<br />
<br />
The new Family Tree Manager replaces the File Open dialog. Version 3.0 does not work on files, but on Family Tree Databases. Since there is no file to open, a file open dialog makes no sense. The Open button has been replaced with a Family Trees button. Clicking this button brings up the Family Tree Manager, shown below.<br />
<br />
[[Image:ManageFamilyTrees-40.png]]<br />
<br />
The Family Tree Manager allows the user to create a new database, rename an existing database, delete a database, or load a database. All databases appear in the list, so the user does not need to worry about where the databases are located. If a database is open, an icon will appear next to the name.<br />
<br />
===== Versions =====<br />
<br />
If the RCS revision control system is installed on your system, Gramps allows you to archive specified versions of your database. To save a version, open the Family Tree Manager and select the opened database. Simply clicking on the Archive button will save the current version to the revision control system. If a database has one or more saved versions, the databases appear as a tree view, with the available versions displayed under them.<br />
<br />
[[Image:Dbmanager03.png]]<br />
<br />
In this example, the ''Gramps Example'' database has two versions which have been saved. These versions are saved snapshots of your database contents.<br />
<br />
The advantage of storing versions is that you can go back to one of these saved versions. To select a version to restore, select the version and click on the Restore button.<br />
<br />
[[File:ManageFamilyTrees-Archive-Selected-to-Extract-example-50.png|Selecting a version to restore]]<br />
<br />
Gramps will extract the version into a new database. The database name is based on the original database name and the revision name.<br />
<br />
[[File:ManageFamilyTrees-Archive-Extracted-version-highlighted-example-50.png|Restored version]]<br />
<br />
Versions may be deleted and renamed.<br />
<br />
===== Multiple users =====<br />
<br />
Unlike previous versions, Gramps 3.0 supports limited sharing of databases. Multiple users may edit the same database, just not at the same time. The Family Tree Manager will identify a database that is open for another user, and you will not be able to load the database until the other user has closed the database.<br />
<br />
[[Image:Dbmanager06.png]]<br />
<br />
===== Repairing a Corrupt Database =====<br />
<br />
On the odd chance that database corruption occurs, the Family Tree Manager will show the corrupted file with an Error icon next to it. If this database is selected, a Repair button will appear (as seen below).<br />
<br />
[[File:FamilyTreesManager-Dialog-ShowingRedErrorStatusIcon-Sample-50.png]]<br />
<br />
Clicking the repair button will rebuild the database from the backup files that are automatically created on exit.<br />
<br />
====Automatic Backup Files====<br />
<br />
To protect against file corruption problems in the Berkeley database, Gramps 3.0 will generate a backup file at exit if any data has changed.<br />
<br />
Unlike in Gramps 2.2, the backup files are not in XML format. The new backup files are a dump of the database tables. This allows the data to be saved quickly. One backup file exists for each primary table in the database. The backup files are not visible to the user, being held in the database directory.<br />
<br />
==== Why no simultaneous access? ====<br />
<br />
From time to time people want to use Gramps for collaborative research, and are then stopped as Gramps does not allow simultaneous access. That is, you can simultaneously access the database, but this typically results in corrupt data, destroying your database. <br />
<br />
The motivation for this is the following:<br />
#We would need a server/client infrastructure, like eg MySQL. However, this is also why MySQL is non-trivial for most users to maintain. We get into system startup files, gramps daemons running, and a whole mess of other stuff. And when you consider that probably under 5% of the users would be interested in something like this, we have to wonder about our return on investment. Is our time more valuable working on other stuff?<br />
#Who to maintain this code? The core developers don't need this feature. Somebody should join the team to make this happen.<br />
<br />
Technically, BSDDB can be made to work with a server environment. However, in Gramps we give the <code>env.open()</code> the <code>DB_PRIVATE flag</code>. The docs say:<br />
;<code>DB_PRIVATE</code>:Specify that the environment will only be accessed by a single process (although that process may be multithreaded). This flag has two effects on the Berkeley DB environment. First, all underlying data structures are allocated from per-process memory instead of from shared memory that is potentially accessible to more than a single process. Second, mutexes are only configured to work between threads.<br />
<br />
:This flag should not be specified if more than a single process is accessing the environment because it is likely to cause database corruption and unpredictable behavior. For example, if both a server application and the Berkeley DB utility db_stat are expected to access the environment, the DB_PRIVATE flag should not be specified.<br />
<br />
:Source: [http://pybsddb.sourceforge.net/api_c/env_open.html DB_ENV->open]<br />
<br />
Note however that consecutive access from different places to the same underlying database is possible with Gramps 3.0, so a collaboration based on time sharing (using different hours to input data in Gramps) is possible.<br />
<br />
===Gramps 5.0===<br />
<br />
In Gramps 5.0, the database backend became a plugin. This version still uses the same backend as previous versions; however, an new backend is introduced called "DB-API". This is a SQL-based backend. After testing was successful, Gramps 5.1 released with the SQlite backend as the default.<br />
<br />
You can read more about this back in [[DB-API Database Backend]].<br />
<br />
==See also==<br />
* [[Gramps XML]]<br />
* [[Generate XML]]<br />
* [[GEDCOM]]<br />
* [[Gramps and GEDCOM]]<br />
* [[Gramps Old database]]<br />
* [[Previous releases of Gramps]]<br />
* [[Using_database_API|Programmer's Introduction to the Gramps database API]]<br />
<br />
[[Category:Developers/General]]<br />
[[Category:Developers/Reference]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Database_Formats&diff=78405Database Formats2020-05-26T00:20:24Z<p>GulliblePangolin: </p>
<hr />
<div>{{languages|Database Formats}}<br />
==History==<br />
<br />
Gramps default data format has evolved over time. Each major change in format usually results in an increase in the major version number.<br />
<br />
* See also [[Gramps XML]]<br />
<br />
===Gramps 1.0 and earlier===<br />
<br />
Gramps 1.0 used XML as its default format. This format is portable and easily read by both computers and people. It has two major issues that caused problems when it was used as the default format.<br />
<br />
* Slow to load and save. The entire file had to be parsed to load the data, and parsing XML is not fast. Similarly, to save any changes, the entire file had to be written. People with larger databases (thousands of persons) found the load and save times to be unusable.<br />
<br />
* Consumes a lot of memory. The XML format required that all data be loaded and stored in memory. Larger databases could consume all memory on the system and as a result bring the system to a virtual halt.<br />
<br />
===Gramps 2.0===<br />
<br />
To solve the capacity issues, Gramps 2.0 switched to using the Berkeley database, using the ".grdb" extension to identify the file. All database information was stored in this file. This resolved both the load/save time issues and the memory consumption issues. Using a real database backend allowed us to only load the data into memory when we needed it.<br />
<br />
The grdb format was a significant step forward for Gramps. However, it was susceptible to data corruption. Since data commits were not atomic (all related changes saved at once), data could get corrupted if an error occurred while a change was being made.<br />
<br />
===Gramps 2.2===<br />
<br />
Gramps 2.2 started using the transaction capability of the Berkeley database. This feature ensures that all related data is committed at once. So, if an error occurs while that data is being saved, the database remains intact. Either the entire set of changes makes it to the database, or none of the changes make it.<br />
<br />
The problem with the approach in 2.2 is that a single file (the grdb file) is no longer enough for the Berkeley database to handle the data. An "environment" directory is needed to store the transactions log files. A place was needed to keep these files so that the user would not delete them. An environment directory under the ~/.gramps directory was chosen for this. The log files are mapped to the database using the path name of the original grdb file.<br />
<br />
This works very well as long as the file is never moved. If the user renames the file, restores a backup of the file, or copies it to another machine, [[Recover_corrupted_family_tree#What_causes_this_corruption.3F_2|the file will no longer work]], since it would no longer correlate to the log files stored under ~/.gramps.<br />
<br />
===Gramps 3.0===<br />
<br />
A new approach was taken with Gramps 3.0. While the Berkeley database is still used, the user will no longer see a file. Instead of the actual database file, user opens a symbolic database name. This name will map to a subdirectory under ~/.gramps directory which contains all the needed database files.<br />
<br />
Since all the files will be in the same directory, advanced users can make a backup of the entire directory, preserving the entire data. New users, who may not be familiar with the Linux filesystem, will not have to worry about finding their database, since a new Family Tree Manager will replace the old Open File dialog.<br />
<br />
====Family Tree Manager====<br />
<br />
The new Family Tree Manager replaces the File Open dialog. Version 3.0 does not work on files, but on Family Tree Databases. Since there is no file to open, a file open dialog makes no sense. The Open button has been replaced with a Family Trees button. Clicking this button brings up the Family Tree Manager, shown below.<br />
<br />
[[Image:ManageFamilyTrees-40.png]]<br />
<br />
The Family Tree Manager allows the user to create a new database, rename an existing database, delete a database, or load a database. All databases appear in the list, so the user does not need to worry about where the databases are located. If a database is open, an icon will appear next to the name.<br />
<br />
===== Versions =====<br />
<br />
If the RCS revision control system is installed on your system, Gramps allows you to archive specified versions of your database. To save a version, open the Family Tree Manager and select the opened database. Simply clicking on the Archive button will save the current version to the revision control system. If a database has one or more saved versions, the databases appear as a tree view, with the available versions displayed under them.<br />
<br />
[[Image:Dbmanager03.png]]<br />
<br />
In this example, the ''Gramps Example'' database has two versions which have been saved. These versions are saved snapshots of your database contents.<br />
<br />
The advantage of storing versions is that you can go back to one of these saved versions. To select a version to restore, select the version and click on the Restore button.<br />
<br />
[[File:ManageFamilyTrees-Archive-Selected-to-Extract-example-50.png|Selecting a version to restore]]<br />
<br />
Gramps will extract the version into a new database. The database name is based on the original database name and the revision name.<br />
<br />
[[File:ManageFamilyTrees-Archive-Extracted-version-highlighted-example-50.png|Restored version]]<br />
<br />
Versions may be deleted and renamed.<br />
<br />
===== Multiple users =====<br />
<br />
Unlike previous versions, Gramps 3.0 supports limited sharing of databases. Multiple users may edit the same database, just not at the same time. The Family Tree Manager will identify a database that is open for another user, and you will not be able to load the database until the other user has closed the database.<br />
<br />
[[Image:Dbmanager06.png]]<br />
<br />
===== Repairing a Corrupt Database =====<br />
<br />
On the odd chance that database corruption occurs, the Family Tree Manager will show the corrupted file with an Error icon next to it. If this database is selected, a Repair button will appear (as seen below).<br />
<br />
[[File:FamilyTreesManager-Dialog-ShowingRedErrorStatusIcon-Sample-50.png]]<br />
<br />
Clicking the repair button will rebuild the database from the backup files that are automatically created on exit.<br />
<br />
====Automatic Backup Files====<br />
<br />
To protect against file corruption problems in the Berkeley database, Gramps 3.0 will generate a backup file at exit if any data has changed.<br />
<br />
Unlike in Gramps 2.2, the backup files are not in XML format. The new backup files are a dump of the database tables. This allows the data to be saved quickly. One backup file exists for each primary table in the database. The backup files are not visible to the user, being held in the database directory.<br />
<br />
==== Why no simultaneous access? ====<br />
<br />
From time to time people want to use Gramps for collaborative research, and are then stopped as Gramps does not allow simultaneous access. That is, you can simultaneously access the database, but this typically results in corrupt data, destroying your database. <br />
<br />
The motivation for this is the following:<br />
#We would need a server/client infrastructure, like eg MySQL. However, this is also why MySQL is non-trivial for most users to maintain. We get into system startup files, gramps daemons running, and a whole mess of other stuff. And when you consider that probably under 5% of the users would be interested in something like this, we have to wonder about our return on investment. Is our time more valuable working on other stuff?<br />
#Who to maintain this code? The core developers don't need this feature. Somebody should join the team to make this happen.<br />
<br />
Technically, BSDDB can be made to work with a server environment. However, in Gramps we give the <code>env.open()</code> the <code>DB_PRIVATE flag</code>. The docs say:<br />
;<code>DB_PRIVATE</code>:Specify that the environment will only be accessed by a single process (although that process may be multithreaded). This flag has two effects on the Berkeley DB environment. First, all underlying data structures are allocated from per-process memory instead of from shared memory that is potentially accessible to more than a single process. Second, mutexes are only configured to work between threads.<br />
<br />
:This flag should not be specified if more than a single process is accessing the environment because it is likely to cause database corruption and unpredictable behavior. For example, if both a server application and the Berkeley DB utility db_stat are expected to access the environment, the DB_PRIVATE flag should not be specified.<br />
<br />
:Source: [http://pybsddb.sourceforge.net/api_c/env_open.html DB_ENV->open]<br />
<br />
Note however that consecutive access from different places to the same underlying database is possible with Gramps 3.0, so a collaboration based on time sharing (using different hours to input data in Gramps) is possible.<br />
<br />
===Gramps 5.0===<br />
<br />
In Gramps 5.0, the database backend became a plugin. This version still uses the same backend as previous versions; however, an new backend is introduced called "DB-API". This is a SQL-based backend. After testing was successful, Gramps 5.1 released with the SQlite backend as the default.<br />
<br />
You can read more about this back in [[DB-API Database Backend]].<br />
<br />
== Detailed Changes ==<br />
<br />
This table lists the database changes for each version.<br />
<br />
{|{{prettytable}} <br />
!Gramps<br />
!Database<br />
!Changes from previous version<br />
|-<br />
|Gramps 5.1<br />
|18<br />
|<br />
* SQLite is default<br />
|-<br />
|Gramps 5.0<br />
|18<br />
|<br />
* Database backends become plugins<br />
* BSDDB is default<br />
* DB-API (SQL) is tested as viable replacement<br />
* Convert default handle to string<br />
|-<br />
|Gramps 4.2<br />
|18<br />
|<br />
* added PlaceNames (with Date and Language) Place<br />
|- <br />
|Gramps 4.1<br />
|17<br />
|<br />
* added Tags to Event, Place, Repository, Source, and Citation<br />
* added alternate names to Place<br />
* Source.data became SourceAttributes<br />
* Added optional support for checksum on Media object<br />
* Added PlaceRef and Place Hierarchies<br />
|- <br />
|Gramps 3.4 - 4.0<br />
|16<br />
|<br />
* converted SourceRef to new Citation object<br />
* Source and Citation objects gained a private flag<br />
|- <br />
|Gramps 3.1 - 3.3<br />
|15<br />
|<br />
* added Tags to Person, Family, and Note<br />
* added Surname list<br />
* removed Marker <br />
|- <br />
|Gramps 3.0<br />
|14<br />
|<br />
* added newyear to Dates<br />
* Replace plain text with StyledText in Notes<br />
|- <br />
|Gramps 2.x<br />
|13<br />
|<br />
* changed name formats <br />
|}<br />
<br />
==See also==<br />
* [[Gramps XML]]<br />
* [[Generate XML]]<br />
* [[GEDCOM]]<br />
* [[Gramps and GEDCOM]]<br />
* [[Gramps Old database]]<br />
* [[Previous releases of Gramps]]<br />
* [[Using_database_API|Programmer's Introduction to the Gramps database API]]<br />
<br />
[[Category:Developers/General]]<br />
[[Category:Developers/Reference]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Talk:Gramps_Glossary&diff=78404Talk:Gramps Glossary2020-05-26T00:12:10Z<p>GulliblePangolin: </p>
<hr />
<div>;<span id="active_person">Active Person</span>: (''core concept'') - The person designated as the momentary center of focus in the open Gramps database. The perspective of this person defines the context for actions and for displaying all the surrounding information. Changing this focus is done by [[Gramps_{{Version manual}}_Wiki_Manual_-_Navigation#Setting_the_Active_Person|navigating the Active Person]] selection to another person. <br />
<br />
;<span id="active_person"><span id = "personne_actif">Personne Actif</span> ''<small>(Active Person)</small>''</span>: (''concept principal'') - La personne désignée comme le centre de concentration momentané dans la base de données Gramps ouverte. La perspective de cette personne définit le contexte des actions et de l'affichage de toutes les informations environnantes. La modification de ce focus se fait en sélectionnant [[Fr:Manuel_wiki_pour_Gramps_{{Version manual}}_-_Navigation#Choisir_le_de_Cujus.2C_la_souche|naviguer le Personne Actif]] vers une autre personne.<br />
<br />
==How should Gramps ID be added?==<br />
Under "G" or "I"? Gramps ID [[Gramps_5.1_Wiki_Manual_-_Settings#ID_Formats]] [[User:GulliblePangolin|GulliblePangolin]] ([[User talk:GulliblePangolin|talk]]) 00:12, 26 May 2020 (UTC)</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_Keybindings&diff=78403Gramps 5.1 Wiki Manual - Keybindings2020-05-26T00:09:13Z<p>GulliblePangolin: /* Common keybindings */</p>
<hr />
<div>{{man index|Gramps 5.1 Wiki Manual - FAQ|Gramps 5.1 Wiki Manual - Command Line|5.1}}<br />
{{languages|Gramps_5.1_Wiki_Manual_-_Keybindings}}<br />
{{#vardefine:chapter|B}}<br />
{{#vardefine:figure|0}}<br />
This appendix lists keybindings (also known as ''Keyboard shortcuts'' or ''hotkeys'') that can be used in the Gramps dialogs as an alternative to using the mouse.<br />
<br />
Some keybindings require the user to press a single key or a sequence of keys one after the other. Other keybindings require pressing and holding several keys simultaneously. <br />
== List Views ==<br />
=== Common keybindings ===<br />
<br />
{{man tip|Keyboards are not all the same!|<br />
Keybindings may depend on the keyboard layout (localization) and on your computer&rsquo;s Operating System.{{-}}<br />
[[File:windows_180x160.png|128px]] [[File:macos_200x200.png|128px]] [[File:Linux_220x261.png|128px]] [[File:Bsd daemon.png|128px]]}}<br />
The following keybindings are available in all category [[Gramps_Glossary#view|views]].<br />
{|{{prettytable}}<br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME <br />
|-<!--- ############ WARNING once an id="x" number has been assigned do not change as referenced else where in UserManual --><br />
|<!-- Action/Function --> id="1" | [[Gramps_5.1_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|Manage family trees]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|O}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|O}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|O}}<br />
|-<br />
|<!-- Action/Function --> id="2" | [[Gramps_5.1_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Import family tree]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|I}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|I}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|I}}<br />
|-<br />
|<!-- Action/Function --> id="3" | [[Gramps_5.1_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|Export family tree]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|E}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|E}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|E}}<br />
|-<br />
|<!-- Action/Function --> id="4" | Changes to the next [[Gramps_5.1_Wiki_Manual_-_Main_Window#Switching_Categories|Category]].<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|N}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|N}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|N}}<br />
|-<br />
|<!-- Action/Function --> id="5" |Changes to the previous [[Gramps_5.1_Wiki_Manual_-_Main_Window#Switching_Categories|Category]].<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|P}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|P}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|P}}<br />
|-<br />
|<!-- Action/Function --> id="45" |Change [[Gramps_5.1_Wiki_Manual_-_Main_Window#Switching_Categories|Category]]<br>to Category number 0/1/2/../9<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|1}}<br>{{Man key press|Ctrl|2}}<br>{{Man key press|Ctrl|3}} ...<br />
|<!-- Mac OS --> |{{Man key press|Cmd|1}}<br>{{Man key press|Cmd|2}}<br>{{Man key press|Cmd|3}}..<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|1}}<br>{{Man key press|Ctrl|2}}<br>{{Man key press|Ctrl|3}}..<br />
|-<br />
|<!-- Action/Function --> id="6" |Within the Category changes the [[Gramps_5.1_Wiki_Manual_-_Main_Window#Switching_Views|view]]<br>to view mode number 0/1/2/../9<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Alt|1}}<br>{{Man key press|Ctrl|Alt|2}}<br>{{Man key press|Ctrl|Alt|3}} ...<br />
|<!-- Mac OS --> |{{Man key press|Cmd|Opt|1}}<br>{{Man key press|Cmd|Opt|2}}<br>{{Man key press|Cmd|Opt|3}}..<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Alt|1}}<br>{{Man key press|Ctrl|Alt|2}}<br>{{Man key press|Ctrl|Alt|3}}..<br />
|-<br />
|<!-- Action/Function --> id="8" |[[Gramps_5.1_Wiki_Manual_-_Navigation#Using_the_Clipboard|Open the Clipboard]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|B}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|B}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|B}}<br />
|-<br />
|<!-- Action/Function --> id="9" |Add the selected item as a [[Gramps_5.1_Wiki_Manual_-_Navigation#Bookmarks|bookmark]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|D}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|D}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|D}}<br />
|-<br />
|<!-- Action/Function --> id="10" |[[Gramps_5.1_Wiki_Manual_-_Navigation#Bookmarks|Organize the bookmarks]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Shift|Ctrl|D}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|D}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Shift|Ctrl|D}}<br />
|-<br />
|<!-- Action/Function --> id="11" |Open the {{man label|[[Gramps_5.1_Wiki_Manual_-_Navigation#Edit|Undo History]]}} dialog<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|H}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|H}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|H}}<br />
|-<br />
|<!-- Action/Function --> id="12" |Jump to an [[Gramps_5.1_Wiki_Manual_-_Settings#ID_Formats|Gramps ID]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|J}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|J}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|J}}<br />
|-<br />
|<!-- Action/Function --> id="13" |Move to previous item in history<br />
|<!-- Microsoft Windows --> |{{Man key press|Alt|Left}} (Left arrow)<br />
|<!-- Mac OS --> |{{Man key press|Ctrl|Opt|Left}} (Left arrow)<br />
|<!-- KDE/GNOME --> |{{Man key press|Alt|Left}} (Left arrow)<br />
|-<br />
|<!-- Action/Function --> id="14" |Move to next item in history<br />
|<!-- Microsoft Windows --> |{{Man key press|Alt|Right}} (Right arrow)<br />
|<!-- Mac OS --> |{{Man key press|Ctrl|Opt|Right}} (Right arrow)<br />
|<!-- KDE/GNOME --> |{{Man key press|Alt|Right}} (Right arrow)<br />
|-<br />
|<!-- Action/Function --> id="15" |Go to the '''[[Gramps_5.1_Wiki_Manual_-_Settings#Setting_Home_person|Home Person]]'''<br />
|<!-- Microsoft Windows --> |{{Man key press|Alt|Home}}<br />
|<!-- Mac OS --> |<br />
|<!-- KDE/GNOME --> |{{Man key press|Alt|Home}}<br />
|-<br />
|<!-- Action/Function --> id="16" |Same action as the [[File:Gramps-config.png|20px]] Configure active view button<br />
|<!-- Microsoft Windows --> |{{Man key press|Shift|Ctrl|C}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|C}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Shift|Ctrl|C}}<br />
|-<br />
|<!-- Action/Function --> id="7" |Toggle the left gramplet sidebar ([[Gramps_5.1_Wiki_Manual_-_Main_Window#Navigator|Navigator]] panel)<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|M}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|M}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|M}}<br />
|-<br />
|<!-- Action/Function --> id="17" |Toggle the right gramplet sidebar ([[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]])<br />
|<!-- Microsoft Windows --> |{{Man key press|Shift|Ctrl|R}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|R}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Shift|Ctrl|R}}<br />
|-<br />
|<!-- Action/Function --> id="18" |Toggle the bottom gramplet sidebar ([[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]])<br />
|<!-- Microsoft Windows --> |{{Man key press|Shift|Ctrl|B}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|B}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Shift|Ctrl|B}}<br />
|-<br />
|<!-- Action/Function --> id="19" |Undo<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Z}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|Z}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Z}}<br />
|-<br />
|<!-- Action/Function --> id="20" |Do again<br />
|<!-- Microsoft Windows --> |{{Man key press|Shift|Ctrl|Z}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|Z}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Shift|Ctrl|Z}}<br />
|-<br />
|<!-- Action/Function --> id="21" |Quit Gramps<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Q}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|Q}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Q}}<br />
|-<br />
|<!-- Action/Function --> id="xx" | [[Gramps_5.1_Wiki_Manual_-_Navigation#Add|Add/Create]] a new object (Opens the related Editor)<br>Person<br>Family<br>Event<br>Place<br>Source<br>Citation<br>Repository<br>Media<br>Note<br />
|<!-- Microsoft Windows --> |<br>{{Man key press|Shift|Alt|P}}<br>{{Man key press|Shift|Alt|F}}<br>{{Man key press|Shift|Alt|E}}<br>{{Man key press|Shift|Alt|L}}<br>{{Man key press|Shift|Alt|S}}<br>{{Man key press|Shift|Alt|C}}<br>{{Man key press|Shift|Alt|R}}<br>{{Man key press|Shift|Alt|M}}<br>{{Man key press|Shift|Alt|N}}<br />
|<!-- Mac OS --> |<br>{{Man key press|Shift|Ctrl|Opt|P}}<br>{{Man key press|Shift|Ctrl|Opt|F}}<br>{{Man key press|Shift|Ctrl|Opt|E}}<br>{{Man key press|Shift|Ctrl|Opt|L}}<br>{{Man key press|Shift|Ctrl|Opt|S}}<br>{{Man key press|Shift|Ctrl|Opt|C}}<br>{{Man key press|Shift|Ctrl|Opt|R}}<br>{{Man key press|Shift|Ctrl|Opt|M}}<br>{{Man key press|Shift|Ctrl|Opt|N}}<br />
|<!-- KDE/GNOME --> |<br>{{Man key press|Shift|Alt|P}}<br>{{Man key press|Shift|Alt|F}}<br>{{Man key press|Shift|Alt|E}}<br>{{Man key press|Shift|Alt|L}}<br>{{Man key press|Shift|Alt|S}}<br>{{Man key press|Shift|Alt|C}}<br>{{Man key press|Shift|Alt|R}}<br>{{Man key press|Shift|Alt|M}}<br>{{Man key press|Shift|Alt|N}}<br />
|}<br />
<br />
=== All List Views bindings ===<br />
<br />
The following bindings are available in all list views: People, Families, Events, Places, Sources, Citations, Repositories, Media and Notes View.<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME<br />
!Note<br />
|-<br />
|<!-- Action/Function --> id="22" |Edits the selected list item <br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Enter}}<br />
|<!-- Mac OS --> |<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Enter}}<br />
|<!-- Note --> |<br />
|- <br />
|<!-- Action/Function --> id="23" |Adds a new item to the database <br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Insert}}<br />
|<!-- Mac OS --> |<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Insert}}<br />
|<!-- Note --> |<br />
|- <br />
|<!-- Action/Function --> id="24" |Deletes the selected list item <br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Delete}}<br />
|<!-- Mac OS --> |<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Delete}}<br />
|<!-- Note --> |<br />
|-<br />
|<!-- Action/Function --> id="46" |Activate the {{man button|Find}} field<br />
|!-- Microsoft Windows --> |{{Man key press|Ctrl|F}}<br />
|!-- Mac OS --> |{{Man key press|Cmd|F}}<br />
|!-- KDE/GNOME --> |{{Man key press|Ctrl|F}}<br />
|<!-- Note --> | List view interactive search ahead / Quick search<br />
|}<br />
<br />
=== People View bindings ===<br />
<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME<br />
|- <br />
|<!-- Action/Function --> id="25" |Expands and hides entries of the selected surname in Group mode<br />
|<!-- Microsoft Windows --> |{{Man key press|Enter}}<br />
|<!-- Mac OS --> |{{Man key press|Enter}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Enter}}<br />
|}<br />
<br />
==Editors==<br />
<br />
=== Editor Tab bindings ===<br />
These bindings work on the tab pages of the editors (so not on the labels of the tabs!, press tab on label to move to tabpage content).<br />
<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME<br />
|- <br />
|<!-- Action/Function --> id="26" |Same action as the {{icon|Stock_edit}} button when that button is present<br />
|{{Man key press|Enter}}<br />
|{{Man key press|Enter}}<br />
|{{Man key press|Enter}}<br />
|- <br />
|<!-- Action/Function --> id="27" |Same action as the {{icon|Stock_add}} button when that button is present<br />
|{{Man key press|Insert}}<br />
|<br />
|{{Man key press|Insert}}<br />
|- <br />
|<!-- Action/Function --> id="28" |Same action as the {{icon|Stock_remove}} button when that button is present<br />
|{{Man key press|Delete}}<br />
|<br />
|{{Man key press|Delete}}<br />
|- <br />
|<!-- Action/Function --> id="29" |Same action as the {{man button|Share}} button when that button is present<br />
|{{Man key press|Ctrl|O}}<br />
|{{Man key press|Cmd|O}}<br />
|{{Man key press|Ctrl|O}}<br />
|- <br />
|<!-- Action/Function --> id="30" |Change tabpage to the tabpage to the left<br />
|{{Man key press|Alt|Left}} (Left arrow)<br />
|{{Man key press|Ctrl|Alt|Left}} (Left arrow)<br />
|{{Man key press|Alt|Left}} (Left arrow)<br />
|- <br />
|<!-- Action/Function --> id="31" |Change tabpage to the tabpage to the right<br />
|{{Man key press|Alt|Right}} (Right arrow)<br />
|{{Man key press|Ctlr|Alt|Right}} (Right arrow)<br />
|{{Man key press|Alt|Right}} (Right arrow)<br />
|}<br />
<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Mouse Key<br />
|- <br />
|<!-- Action/Function --> id="32" |Call up [https://en.wikipedia.org/wiki/Context_menu context menu] popup<br />
!Right-click<br />
|- <br />
|<!-- Action/Function --> id="33" |Same action as the {{icon|Stock_edit}} {{man button|Edit}} button when that button is present<br />
!Double-click<br />
|- <br />
|<!-- Action/Function --> id="34" |Common action that is not the same as {{icon|Stock_edit}} {{man button|Edit}} button. Eg: on Family Editor Child tab, edit child<br />
!Middle-click<br />
|}<br />
<br />
=== Editor bindings ===<br />
These bindings work on Editors by activating focus or by changing state of toggle buttons ([[Accessibility]]).<br />
<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME<br />
|- <br />
|<!-- Action/Function --> id="35" |Change the privacy status.<br />
|{{Man key press|Ctrl|P}}<br />
|{{Man key press|Cmd|P}}<br />
|{{Man key press|Ctrl|P}}<br />
|- <br />
|<!-- Action/Function --> id="36" |Call the Date editor (if present).<br />
|{{Man key press|Ctrl|D}}<br />
|{{Man key press|Cmd|D}}<br />
|{{Man key press|Ctrl|D}}<br />
|- <br />
|<!-- Action/Function --> id="37" |Activate the {{icon|Stock_add}} {{man button|Add}} button (if present).<br />
|{{Man key press|Ctrl|A}}<br />
|{{Man key press|Cmd|A}}<br />
|{{Man key press|Ctrl|A}}<br />
|- <br />
|<!-- Action/Function --> id="38" |Activate the {{icon|Stock_edit}} {{man button|Edit}} button (if present).<br />
|{{Man key press|Ctrl|E}}<br />
|{{Man key press|Cmd|E}}<br />
|{{Man key press|Ctrl|E}}<br />
|- <br />
|<!-- Action/Function --> id="39" |Activate the {{man button|Select}} button (if present).<br />
|{{Man key press|Ctrl|S}}<br />
|{{Man key press|Cmd|S}}<br />
|{{Man key press|Ctrl|S}}<br />
|- <br />
|<!-- Action/Function --> id="40" |Activate the {{man button|Father}} button (if present).<br />
|{{Man key press|Ctrl|F}}<br />
|{{Man key press|Cmd|F}}<br />
|{{Man key press|Ctrl|F}}<br />
|- <br />
|<!-- Action/Function --> id="41" |Activate the {{man button|Mother}} button (if present).<br />
|{{Man key press|Ctrl|M}}<br />
|{{Man key press|Cmd|M}}<br />
|{{Man key press|Ctrl|M}}<br />
|}<br />
<br />
==Handy Shortcuts==<br />
<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME <br />
!Note<br />
|-<br />
|<!-- Action/Function --> id="42" |Full screen<br />
|{{man key press|F11}}<br />
|<br />
|{{man key press|F11}}<br />
|Maximises Gramps to use the Full screen<br />
|-<br />
|<!-- Action/Function --> id="43" |Show this user manual<br />
|{{man key press|F1}}<br />
|{{man key press|F1}}<br />
|{{man key press|F1}}<br />
|<br />
|-<br />
|<!-- Action/Function --> id="44" |Select the {{man button|OK}} button<br />
|{{man key press|Alt}}+{{man key press|O}}<br />
|<br />
|<br />
|Handy for use with low resolution screens<br />
|-<br />
|<!-- Action/Function --> id="45" |Select the {{man button|Cancel}} button<br />
|{{man key press|Esc}}<br />
|<!-- {{Man key press|&#x238B; Esc}} macOS Escape key unicode symbol placeholder. Esc keybinding not yet confirmed for mac --><br />
|<br />
|Handy for use with low resolution screens<br />
|}<br />
<br />
== See also ==<br />
* [http://en.wikipedia.org/wiki/Table_of_keyboard_shortcuts Table of keyboard shortcuts] - for major operating systems.<br />
<br />
{{-}}<br />
{{man index|Gramps 5.1 Wiki Manual - FAQ|Gramps 5.1 Wiki Manual - Command Line|5.1}}<br />
{{languages|Gramps_5.1_Wiki_Manual_-_Keybindings}}<br />
{{grampsmanualcopyright}}<br />
<br />
[[Category:Documentation]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Narrated_Website_Ancestry_Tree_Design_Notes&diff=78401Narrated Website Ancestry Tree Design Notes2020-05-25T23:20:31Z<p>GulliblePangolin: </p>
<hr />
<div>The source code that generates the Ancestry Tree portion of the Narrated Website can be found below [https://github.com/gramps-project/gramps/tree/master/gramps/plugins/webreport Gramps/gramps/plugins/webreport] in a Gramps source code tree.<br />
<br />
The Narrated Website Report can include an Ancestry Tree. The layout of the tree uses a tree generating algorithm created by Walker[http://www.cs.unc.edu/techreports/89-034.pdf] and then improved by Buchheim et.al[http://dirk.jivas.de/papers/buchheim02improving.pdf].<br />
<br />
The tree is first defined as a series of objects each containing a node plus references to the child-nodes of this node and the Buchheim algorithm then uses these child/parent relationships, together with a minimum separation vertically and horizontally, to determine a reasonable layout. The generated tree provides an X and Y coordinate for each node.<br />
<br />
Within the Gramps Narrated Website Report, the following objects and relationships are generated:<br />
<br />
* Each node (person) is represented by a LayoutTree object which references 'children' objects and stores the handle for a Gramps Person object<br />
* For the Ancestry tree, a 'child' of a node is actually a parent (so we expect there to be only 0/1/2 parents but the algorithm would allow more)<br />
* The top-mode node, the root of the tree, is provided to the Buchheim algorithm which returns a DrawTree object defining the layout.<br />
<br />
Each DrawTree node contains X and Y coordinates and references a LayoutTree node and therefore a Person.<br />
<br />
The Ancestry tree is a series on interconnected boxes so the remainder of the process is drawing the tree based on the DrawTree information. The following gives an overview of the process and references some internal variables in the code.<br />
<br />
* The tree is drawn within an HTML element which defines a space on the page large enough for the tree.<br />
* The tree is drawn _XOFFSET pixels to the right and _YOFFSET down from the top to provide a nice border; similar space is allowed for when defining the containing HTML element.<br />
* The node is draw 'as big as required' up to a maximum depth of _HEIGHT; this can leave some larger vertical gaps between nodes where information about the person is sparse so a small box can contain everything.<br />
* Related node boxes are separated by at least _HGAP horizontally and _VGAP vertically but this gaps can be bigger depending no the layout requirements of other nodes.<br />
* Connecting lines are drawn between the child to parent(s) but this is done in two stages:<br />
** If this child has parents, a line is drawn form the child horizontally towards the parent (stopping at the midpoint between them)<br />
** Each parent draws a horizontal line back towards the child and a vertical line to join the parent and child's horizontal lines<br />
* Connecting lines meet a person box _LOFFSET from the top of the box (and not relative to the bottom). This allows boxes to be be of variable depth without lines either being left floating of the box doesn't reach down to them or requiring complex calculations to determine an offset relative to the bottom of the box.<br />
<br />
The actual Walker and Buchheim algorithms are well documented in the referenced papers and the actual HTML drawing is best understood by reading the code.<br />
<br />
Finally it is noted that although the algorithm draw from left to right, it can easily be modified to draw from right to left, top to bottom or bottom to top.<br />
<br />
The algorithm might also be useful for other parts of Gramps such as the Graphical Reports Ancestor or Descendents Tree.<br />
<br />
==References==<br />
* <nowiki>[1]</nowiki> [http://www.cs.unc.edu/techreports/89-034.pdf A Node-Positioning Algorihm for General Trees. John Q.Walker II]<br />
* <nowiki>[2]</nowiki> [http://dirk.jivas.de/papers/buchheim02improving.pdf Improving Walker's Algorithm to Run in Linear Time. Christoph Buchheim et.al.]<br />
<br />
* [https://github.com/gramps-project/gramps/pull/548 Add Buchheim tree ancestor trees to Narrated Web Report #548]<br />
* [http://gramps.1791082.n4.nabble.com/Where-should-I-put-design-notes-td4681555.html Where should I put design notes? ]<br />
<br />
==See also==<br />
* [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_7#Html_options]] - [x] Include ancestor's tree<br />
<br />
[[Category:Developers/Reference]]<br />
[[Category:Proposed_Report_Specifications]]<br />
[[Category:GEPS]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Portal:Developers&diff=78400Portal:Developers2020-05-25T23:12:02Z<p>GulliblePangolin: </p>
<hr />
<div>{| cellspacing="5" width="auto"<br />
|-<br />
| width="100%" colspan="3" valign="top" style="border: 1px solid #ababab; background: #fff; padding: 0" |<br />
{{Developers/box-header|<big>The Gramps Developers Portal</big>|Developers/Intro}}<br />
|-<br />
| width="100%" valign="top" style="border: 1px solid #ababab; background: #fff; padding: 0" |<br />
{{Developers/box-header|''Report System''|Developers/Write a Report}}<br />
|-<br />
| valign="top" colspan="3" style="border: 1px solid #ababab; background: #fff; padding: 0" |<br />
{{Developers/box-header|''Categories''|Developers/Categories}}<br />
|}<br />
{| cellspacing="5" width="auto"<br />
|-<br />
|<!-- valign="top" colspan="2" | {{#lst:Poll|polldevelpage}} --><br />
|}<br />
<br />
__NOTOC__<br />
<br />
[[Category:Portals|D]]<br />
[[Category:Community/General|G]]<br />
[[Category:Developers/General]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Template:Developers/Categories&diff=78399Template:Developers/Categories2020-05-25T23:11:22Z<p>GulliblePangolin: </p>
<hr />
<div><noinclude><div style="float:left; width:100%;">{{Developers/box-header|''Categories''|Developers/Categories}}<br />
</noinclude><div style="text-align:center;"><!--<br />
-->[[:Category:Developers|Developers Categories]] : <!--<br />
-->[[:Category:Developers/Artwork|Artwork]] | <!-- <br />
-->[[:Category:Developers/General|General]] | <!--<br />
-->[[:Category:Developers/Packaging|Packaging]] | <!--<br />
-->[[:Category:Addons|Addons]] / [[:Category:Plugins|Plugins]] | <!--<br />
-->[[:Category:Developers/Reference|References]] | <!--<br />
-->[[:Category:Reports|Reports]] | <!--<br />
-->[[:Category:Developers/Roadmap|Roadmap]] | <!--<br />
-->[[:Category:Translators/Categories|Translation]] | <!--<br />
-->[[:Category:Developers/Tutorials|Tutorials]] <!--<br />
--></div></div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Template:Developers/Categories&diff=78398Template:Developers/Categories2020-05-25T23:10:33Z<p>GulliblePangolin: </p>
<hr />
<div><noinclude><div style="float:left; width:100%;">{{Developers/box-header|''Categories''|Developers/Categories}}<br />
</noinclude><div style="text-align:center;"><!--<br />
-->[[:Category:Developers|Developers Categories]] : <!--<br />
-->[[:Category:Developers/Artwork|Artwork]] | <!-- <br />
-->[[:Category:Developers/General|General]] | <!--<br />
-->[[:Category:Developers/Packaging|Packaging]] | <!--<br />
-->[[:Category:Plugins|Plugins]] /[[:Category:Addons]] | <!--<br />
-->[[:Category:Developers/Reference|References]] | <!--<br />
-->[[:Category:Reports|Reports]] | <!--<br />
-->[[:Category:Developers/Roadmap|Roadmap]] | <!--<br />
-->[[:Category:Translators/Categories|Translation]] | <!--<br />
-->[[:Category:Developers/Tutorials|Tutorials]] <!--<br />
--></div></div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Portal:Developers&diff=78397Portal:Developers2020-05-25T23:08:47Z<p>GulliblePangolin: </p>
<hr />
<div>{| cellspacing="5" width="auto"<br />
|-<br />
| width="100%" colspan="3" valign="top" style="border: 1px solid #ababab; background: #fff; padding: 0" |<br />
{{Developers/box-header|<big>The Gramps Developers Portal</big>|Developers/Intro}}<br />
|-<br />
| width="100%" valign="top" style="border: 1px solid #ababab; background: #fff; padding: 0" |<br />
{{Developers/box-header|''Report System''|Developers/Write a Report}}<br />
|-<br />
| valign="top" colspan="3" style="border: 1px solid #ababab; background: #fff; padding: 0" |<br />
{{Developers/box-header|''Categories''|Developers/Categories}}<br />
|}<br />
{| cellspacing="5" width="auto"<br />
|-<br />
|<!-- valign="top" colspan="2" | {{#lst:Poll|polldevelpage}} --><br />
|}<br />
__NOTOC__<br />
<br />
[[Category:Portals|D]]<br />
[[Category:Community/General|G]]<br />
[[Category:Developers/General]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Building_Gramps_AIO_cx_freeze-based&diff=78396Building Gramps AIO cx freeze-based2020-05-25T23:04:48Z<p>GulliblePangolin: /* Get the tools */</p>
<hr />
<div>{{man warn|Gramps 4.2.8 and later.|Any comments and help (e.g. on wiki pages) are welcome.}}<br />
<br />
The '''Gramps''' "software bundle" for Windows or '''GrampsAIO''' is an all-in-one (a.k.a. '''"AIO"''') installation package of Gramps which includes all dependencies for the Windows platform.<br />
<br />
This tutorial describes how to generate a Windows AIO package from a development installation such as is created with [[Gramps for Windows with MSYS2]].<br />
<br />
It is intended for Windows users and does not attempt to describe how to do the same thing on Linux or a Mac.<br />
<br />
("AIO" means all-in-one, which means that everything you need to run Gramps is included in the one AIO file you download and then install -- all the related programs and library files which Gramps needs on Windows.)<br />
<br />
{{man note|Note|The first Gramps AIO package was created by an advanced Windows power-user named Josip. He is the one who evolved the AIO package and modified the AIO package over the years as Gramps has changed. Everything documented here initially done by him; this just documents some changes and tries to explain it for others. Any Gramps Windows user owes him a large debt of gratitude.}}<br />
<br />
{{man tip|Note|In this tutorial you will be creating a 32-bit AIO. The steps for creating a 64-bit version are quite similar, just a few editing changes to the files and scripts. }}<br />
<br />
==Prerequisites==<br />
You must have a development version of Gramps up and running. See [[Gramps for Windows with MSYS2]] which describes the process for a 64-bit installation. When following this process, you must change a few things for 32-bits.<br />
<br />
{{man note|Note|Pay close attention to the shell to use when running the various commands. Use <code>MSYS2 MSYS</code> for the <code>pacman</code> and <code>makepkg-mingw</code> steps and the <code>MSYS2 MINGW32/64</code> shell to run <code>python3 Gramps.py</code>.}}<br />
<br />
When the instructions say to use the <code>MSYS2 MINGW64</code> shell you should use <code>MSYS2 MINGW32</code> shell instead for 32-bit operation.<br />
<br />
Change the 'pacman' command install file prefixes from <code>mingw-w64-x86_64</code> to <code>mingw-w64-i686</code>.<br />
<br />
Because Josip does not have (as of this writing) some of the packages (gtk, db, bsddb3) that he built done for 32-bit we have to do them ourselves 'the hard way'.<br />
<br />
Change the <code>MINGW_INSTALLS=mingw64 makepkg-mingw –sLf</code> lines to <code>MINGW_INSTALLS=mingw32 makepkg-mingw -sLf</code>.<br />
<br />
=== Get the tools ===<br />
<br />
{{man note|Note|Josip uses a cx_Freeze with some changes he made to make the process a bit easier. I attempted to make similar changes, but we will have to build the utility. }}<br />
Download https://gramps-project.org/wiki/images/a/a3/Mingw-w64-python-cx_Freeze.zip [[:File:Mingw-w64-python-cx_Freeze.zip| (stored here)]] to a convenient location with your browser.<br />
<br />
I do my builds in the <code>c:\msys64\home\user\builds</code> directory, so we will make a new sub-directory for cx_Freeze there.<br />
<br />
I use 7-zip to extract to the <code>c:\msys64\home\user\builds\cx_Freeze</code> directory.<br />
<br />
<br />
{{man note|Note|Use <code>MSYS2 MSYS</code> shell.}}<br />
MINGW_INSTALLS=mingw32 makepkg-mingw -sLf<br />
pacman -U mingw-w64-i686-python3-cx_Freeze-5.0.2-1-any.pkg.tar.xz<br />
<br />
The patches included in the zip should fix up cx_Freeze for a bug where it tries to load an sqlite3.dll file, and to add properly optimized base files for Python startup (In the original version the 'optimize' functionality doesn't work).<br />
<br />
<br />
NSIS is a tool to build the actual installer. As of NSIS version 3.05 the standard nsis available from the MINGW archive works.<br />
pacman -S mingw-w64-i686-nsis<br />
<br />
If you have NSIS version 3.04, The version in the mingw system has a bug that makes displaying of the font files during the AIO install messed up. I've created a patch, so we need to build our own.<br />
Download https://gramps-project.org/wiki/index.php/File:Mingw-w64-nsis.zip [[:File:Mingw-w64-nsis.zip| (stored here)]] to a convenient location with your browser.<br />
<br />
Unzip and cd into the directory then:<br />
{{man note|Note|Use <code>MSYS2 MSYS</code> shell.}}<br />
MINGW_INSTALLS=mingw32 makepkg-mingw -sLf<br />
pacman -U mingw-w64-i686-nsis-3.0.4-1-any.pkg.tar.xz<br />
<br />
=== Get a reference AIO ===<br />
We also need the most recent version of Gramps AIO available. If it is for your branch, it is likely to have the closest scripts with minimal editing. Of course a newer version for a newer branch might have some changes in the scripts that deal with more recent dependencies. You may want to reference both in updating scripts for the new version. Get it installed so you can see the files from that installation.<br />
<br />
=== Install the old Gramps ===<br />
When you start the installer, it will ask you to select language and spell check files. Select all of them.<br />
It will then ask where you want it installed. You can install it where you want, as it is only a temporary location which you may delete afterward. But make a note of the folder since you will need to know it later. Also, it needs to be a new (empty) folder, not an already existing one.<br />
<br />
In this tutorial we'll say you tell the installer to put it into a new "<code>C:\Program Files (x86)\GrampsAIO32-5.1.0</code>" folder.<br />
<br />
Then double-click on the AIO executable to start the 5.1.0 installation. (If your Windows asks whether you will allow that program to change things on your computer, say yes of course.)<br />
<br />
You can put it anywhere you want but if you do, change the string "<code>C:\Program Files (x86)\GrampsAIO32-5.1.0</code>" in this tutorial to the actual name you used. But every time I use "<code>C:\Program Files (x86)\GrampsAIO32-5.1.0</code>" I mean the top of the tree where you installed the "old" AIO.<br />
<br />
After the installer is finished, the last window will offer you the opportunity to "Run" the Gramps you just installed, so you should un-click that box before you hit "Finish", since there is no need to run the old one.<br />
<br />
Similarly, you can delete the "GrampsAIO32 x.x.x" (or GrampsAIO64 one)" icon shortcut from your Desktop, since you won't be using it.<br />
<br />
=== Get Gramps installed in our development environment ===<br />
{{man note|Note|Use <code>MSYS2 MINGW32</code> shell.}}<br />
<br />
If you have not already done so as part of the prior steps, do the following:<br />
cd ~/grampsdev # my copy of git repo checked out with the branch you are building.<br />
<br />
python3 setup.py build<br />
<br />
To install preparatory to creating AIO do <br />
python3 setup.py install<br />
<br />
== Building the AIO ==<br />
Note: Gramps contains some spell checking files that are NOT installed by the previous 'pacman' installs. I found it easiest to copy them from the existing Gramps installation (where I installed all the language and spelling files during the AIO install).<br />
The originals were in the installation <code>/share/enchant/myspell</code> directory.<br />
I copied the whole 'myspell' directory above to my <code>c:\msys64\mingw32\share\enchant</code> directory so they could be found by the next step scripts. I used the Windows file explorer as that is easiest for me, but if you are familiar with the Linux <code>cp</code> command, you can do it from the MINGW32 shell.<br />
<br />
Before doing the AIO build, you may want to compare the existing <code>src/setup.py</code> and <code>src/grampsaio32.nsi</code> scripts with the latest ones available from other AIO installations. They change depending on the contents of the AIO and may point up other dependencies or changes. I use Notepad++ and its 'Compare' plugin for this, but feel free to use whatever tool you like.<br />
<br />
I use dir <code>~/aio</code> where my <code>setup.py</code>, <code>grampsX.py</code>, icons and nsis script is stored.<br />
<br />
cd ~<br />
cp -r "/c/Program Files (x86)/GrampsAIO32-5.1.0/src" aio<br />
<br />
=== Modifying the setup.py script ===<br />
The setup.py script should be located in <code>~/aio/setup.py</code>. Use you favorite editor to make sure following is right:<br />
* Python versions are correct; At the moment, Python3.6 is in use, however if your version is different, adjust the references to <code>python3.6</code> and <code>cpython-36m</code> and <code>python36</code> appropriately.<br />
* The 32/64 bit differences are correct; <code>gspawn-win64-helper</code> may need to change to <code>gspawn-win32-helper</code> or vice versa.<br />
* If you have added new dependencies, find the right place to put them into the script.<br />
<br />
Then use the following to create <code>~/aio/mingw32</code> with all files needed for bundle.<br />
=== Modifying the gramps.nsi script ===<br />
Open the <code>gramps.nsi</code> file with your favorite editor.<br />
<br />
Part of the contents should look something like the following:<br />
<pre><br />
!define APPNAME "GrampsAIO32"<br />
!define APPVERSION "5.1.0"<br />
!define APPBUILD "1"<br />
!define APPNAMEANDVERSION "${APPNAME} ${APPVERSION}"<br />
!define APP_PUBLISHER "The Gramps project"<br />
!define APP_WEB_SITE "http://gramps-project.org"<br />
BrandingText "Version ${APPVERSION}-${APPBUILD} -- a new maintenance release"<br />
</pre><br />
<br />
{{man note|Make sure your editor works|One user reported unicode problems with Notepad and then downloaded [https://notepad-plus-plus.org/ Notepad++].}}<br />
<br />
===== Increase the version number =====<br />
Change the '''APPVERSION''' line from "5.1.0" to "5.1.1" instead (or higher if making a newer version).<br />
<br />
===== If needed update APPNAME and APPBUILD =====<br />
Possibly APPNAME and APPBUILD will need changing too, depending on what you are trying to do. Generally the APPBUILD gets incremented if a second AIO release is made from the same version (because of a building issue.<br />
<br />
{{man note|If you are a power user|and have downloaded something other than a tar.gz file, see [[GrampsAIO-4_package_updating#Appendix_A|Appendix A]] to change APPBUILD.}}<br />
<br />
If necessary, change the BrandingText line to have the name of the new Gramps release instead of the old release name. Usually only necessary for major version changes.<br />
<br />
Then save that gramps.nsi file.<br />
<br />
=== Run the scripts ===<br />
python3 setup.py build_exe --no-compress<br />
<br />
Then I pass nsis script from ~/aio/mingw32/src to nsis.<br />
<br />
makensis ~/aio/mingw32/src/grampsaio32.nsi<br />
<br />
Note that after the compilation, the resulting files will be compressed.<br />
<br />
{{man warn|Please be patient|The the last part of the setup.py script and the NSIS package compression will probably take a while<br>'''-- OVER FIVE MINUTES FOR ME --'''}}<br />
<br />
{{man note|Experimenting with NSIS compression|See [[Building Gramps AIO#Appendix_B|Appendix B]] for power-user details, at this stage.}}<br />
<br />
The result is in <code>C:\msys64\home\user\aio\mingw32\src\GrampsAIO-5.1.1-1_win32.exe</code>.<br />
<br />
{{man warn|If you do this more than once, make sure to delete the result file, or it will get encoded into the next AIO. }}<br />
<br />
== Debugging ==<br />
I had several issues in this process. First of all, the mingw repositories are "rolling release", so every time you do a <code>pacman –Syuu</code> you will have different packages and potentially new issues.<br />
<br />
Take care to make sure that you don't overwrite any of the 'static' Gramps dependencies (gtk 3.18.9, bsddb 6.1.0, db 6.0.30 at the time of this writing) with newer versions, and if you do, use <code>pacman -U file.tar.xz</code> to revert them. Get this right FIRST, because if you build anything based on one of the static dependencies, it may end up not working on a newer version. If you do build something out of order, you may end up with mysterious import failures with messages that don't tell you what is really wrong. And it's really hard to debug the installed AIO, as it doesn't look like a typical Python process to the usual debuggers. Experience speaking.<br />
<br />
You may have to build one or more dependencies "the hard way"; that is download the PKGBUILD and any patches from a suitable source <code>https://github.com/Alexpux/MINGW-packages/trunk/mingw-w64-osmgpsmap-git</code> for example, and fix it up for newer versions and build it. See <code>https://github.com/msys2/msys2/wiki/Creating-packages</code> for help here. Or even download source code and compile yourself.<br />
<br />
I used the old DOS <code>tree /F /A > aionew.txt</code> command to make filename dumps from both the new AIO and a recent older one that was freshly installed in an empty directory. This ensures that there are no '.pyc' files to confuse the issue. Then I did a difference compare (using Notepad++) of the two to see what files are different. Any missing files in your new AIO are suspect (unless you did this deliberately).<br />
<br />
<br />
=== Appendix A ===<br />
==== Indicating newer APPBUILD's ====<br />
If you are a power user, you might have downloaded or used git to checkout the latest code in the grampsxx branch:<br />
<br />
https://codeload.github.com/gramps-project/gramps/zip/maintenance/gramps51<br />
<br />
but in any case, if you have downloaded something other than a gramps-release tar.gz (or .zip) file, say this in your top directory <code>~/grampsdev</code> (assuming you have installed Git for Windows):<br />
<br />
git rev-list --count HEAD<br />
<br />
and then<br />
<br />
git rev-parse --short HEAD<br />
<br />
and then put an "r" in front of the first string, followed by a hyphen ("-") and the second string, and then use the resulting combined string as your APPBUILD in the <code>gramps.nsi</code> file, for clarity.<br />
<br />
So for example your APPBUILD line might look like this:<br />
<br />
!define APPBUILD "r23381-25018d6"<br />
<br />
Then continue with the [[GrampsAIO-4_package_updating#Increase_the_version_number|NSIS package building]]<br />
<br />
==== Developers uploading to Sourceforge ====<br />
<br />
If you are a developer and plan to upload it to SourceForge and it is an AIO of (a forthcoming) "master" put it into:<br />
<br />
http://sourceforge.net/projects/gramps/files/Unstable<br />
<br />
but if it is an AIO for a maintenance branch, make a Snapshots folder in that branch and put it there, e.g.:<br />
<br />
http://sourceforge.net/projects/gramps/files/Stable/5.1.1/Snapshots<br />
<br />
so then the APPBUILD numbers will uniquely define that AIO.<br />
<br />
But note that the NSIS-generated filename will say (for instance) "5.1.2" even though it is really a "5.1.1" with bugs fixed, which is why it belongs in 5.1.1/Snapshots.<br />
<br />
Also see [[What to do for a release]]<br />
<br />
=== Appendix B ===<br />
====Experimenting with NSIS compression====<br />
If you are a power user and are experimenting with slight changes to the gramps.nsi script, you can drastically shorten the time needed to have NSIS generate an AIO package by commenting out these two lines (with a semicolon, a ";"):<br />
<br />
SetCompressor /SOLID /FINAL LZMA<br />
SetCompressorDictSize 128<br />
<br />
But if you are building an AIO which will be released to the public (put onto the official gramps files repo), you need to be '''very sure''' to uncomment '''both''' those lines '''first'''.<br />
<br />
==See also==<br />
* [[All In One Gramps Software Bundle for Windows]] for the Gramps 3.4.x and earlier series<br />
* [[Gramps for Windows with MSYS2]]<br />
* [[GrampsAIO cx freeze-based]]<br />
<br />
[[Category:Documentation]]<br />
[[Category:Developers/General]]<br />
[[Category:GEPS|W]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Building_Gramps_AIO_cx_freeze-based&diff=78395Building Gramps AIO cx freeze-based2020-05-25T23:00:58Z<p>GulliblePangolin: </p>
<hr />
<div>{{man warn|Gramps 4.2.8 and later.|Any comments and help (e.g. on wiki pages) are welcome.}}<br />
<br />
The '''Gramps''' "software bundle" for Windows or '''GrampsAIO''' is an all-in-one (a.k.a. '''"AIO"''') installation package of Gramps which includes all dependencies for the Windows platform.<br />
<br />
This tutorial describes how to generate a Windows AIO package from a development installation such as is created with [[Gramps for Windows with MSYS2]].<br />
<br />
It is intended for Windows users and does not attempt to describe how to do the same thing on Linux or a Mac.<br />
<br />
("AIO" means all-in-one, which means that everything you need to run Gramps is included in the one AIO file you download and then install -- all the related programs and library files which Gramps needs on Windows.)<br />
<br />
{{man note|Note|The first Gramps AIO package was created by an advanced Windows power-user named Josip. He is the one who evolved the AIO package and modified the AIO package over the years as Gramps has changed. Everything documented here initially done by him; this just documents some changes and tries to explain it for others. Any Gramps Windows user owes him a large debt of gratitude.}}<br />
<br />
{{man tip|Note|In this tutorial you will be creating a 32-bit AIO. The steps for creating a 64-bit version are quite similar, just a few editing changes to the files and scripts. }}<br />
<br />
==Prerequisites==<br />
You must have a development version of Gramps up and running. See [[Gramps for Windows with MSYS2]] which describes the process for a 64-bit installation. When following this process, you must change a few things for 32-bits.<br />
<br />
{{man note|Note|Pay close attention to the shell to use when running the various commands. Use <code>MSYS2 MSYS</code> for the <code>pacman</code> and <code>makepkg-mingw</code> steps and the <code>MSYS2 MINGW32/64</code> shell to run <code>python3 Gramps.py</code>.}}<br />
<br />
When the instructions say to use the <code>MSYS2 MINGW64</code> shell you should use <code>MSYS2 MINGW32</code> shell instead for 32-bit operation.<br />
<br />
Change the 'pacman' command install file prefixes from <code>mingw-w64-x86_64</code> to <code>mingw-w64-i686</code>.<br />
<br />
Because Josip does not have (as of this writing) some of the packages (gtk, db, bsddb3) that he built done for 32-bit we have to do them ourselves 'the hard way'.<br />
<br />
Change the <code>MINGW_INSTALLS=mingw64 makepkg-mingw –sLf</code> lines to <code>MINGW_INSTALLS=mingw32 makepkg-mingw -sLf</code>.<br />
<br />
=== Get the tools ===<br />
<br />
{{man note|Note|Josip uses a cx_Freeze with some changes he made to make the process a bit easier. I attempted to make similar changes, but we will have to build the utility. }}<br />
Download https://gramps-project.org/wiki/images/a/a3/Mingw-w64-python-cx_Freeze.zip [[:File:Mingw-w64-python-cx_Freeze.zip| (stored here)]] to a convenient location with your browser.<br />
<br />
I do my builds in the <code>c:\msys64\home\user\builds</code> directory, so we will make a new sub-directory for cx_Freeze there.<br />
<br />
I use 7-zip to extract to the <code>c:\msys64\home\user\builds\cx_Freeze</code> directory.<br />
<br />
<br />
{{man note|Note|Use <code>MSYS2 MSYS</code> shell.}}<br />
MINGW_INSTALLS=mingw32 makepkg-mingw -sLf<br />
pacman -U mingw-w64-i686-python3-cx_Freeze-5.0.2-1-any.pkg.tar.xz<br />
<br />
The patches included in the zip should fix up cx_Freeze for a bug where it tries to load an sqlite3.dll file, and to add properly optimized base files for Python startup (In the original version the 'optimize' functionality doesn't work).<br />
<br />
<br />
NSIS is a tool to build the actual installer. As of NSIS version 3.05 the standard nsis available from the MINGW archive works.<br />
pacman -S mingw-w64-i686-nsis<br />
<br />
If you have version 3.04, The version in the mingw system has a bug that makes displaying of the font files during the AIO install messed up. I've created a patch, so we need to build our own.<br />
Download https://gramps-project.org/wiki/index.php/File:Mingw-w64-nsis.zip [[:File:Mingw-w64-nsis.zip| (stored here)]] to a convenient location with your browser.<br />
<br />
Unzip and cd into the directory then:<br />
{{man note|Note|Use <code>MSYS2 MSYS</code> shell.}}<br />
MINGW_INSTALLS=mingw32 makepkg-mingw -sLf<br />
pacman -U mingw-w64-i686-nsis-3.0.4-1-any.pkg.tar.xz<br />
<br />
=== Get a reference AIO ===<br />
We also need the most recent version of Gramps AIO available. If it is for your branch, it is likely to have the closest scripts with minimal editing. Of course a newer version for a newer branch might have some changes in the scripts that deal with more recent dependencies. You may want to reference both in updating scripts for the new version. Get it installed so you can see the files from that installation.<br />
<br />
=== Install the old Gramps ===<br />
When you start the installer, it will ask you to select language and spell check files. Select all of them.<br />
It will then ask where you want it installed. You can install it where you want, as it is only a temporary location which you may delete afterward. But make a note of the folder since you will need to know it later. Also, it needs to be a new (empty) folder, not an already existing one.<br />
<br />
In this tutorial we'll say you tell the installer to put it into a new "<code>C:\Program Files (x86)\GrampsAIO32-5.1.0</code>" folder.<br />
<br />
Then double-click on the AIO executable to start the 5.1.0 installation. (If your Windows asks whether you will allow that program to change things on your computer, say yes of course.)<br />
<br />
You can put it anywhere you want but if you do, change the string "<code>C:\Program Files (x86)\GrampsAIO32-5.1.0</code>" in this tutorial to the actual name you used. But every time I use "<code>C:\Program Files (x86)\GrampsAIO32-5.1.0</code>" I mean the top of the tree where you installed the "old" AIO.<br />
<br />
After the installer is finished, the last window will offer you the opportunity to "Run" the Gramps you just installed, so you should un-click that box before you hit "Finish", since there is no need to run the old one.<br />
<br />
Similarly, you can delete the "GrampsAIO32 x.x.x" (or GrampsAIO64 one)" icon shortcut from your Desktop, since you won't be using it.<br />
<br />
=== Get Gramps installed in our development environment ===<br />
{{man note|Note|Use <code>MSYS2 MINGW32</code> shell.}}<br />
<br />
If you have not already done so as part of the prior steps, do the following:<br />
cd ~/grampsdev # my copy of git repo checked out with the branch you are building.<br />
<br />
python3 setup.py build<br />
<br />
To install preparatory to creating AIO do <br />
python3 setup.py install<br />
<br />
== Building the AIO ==<br />
Note: Gramps contains some spell checking files that are NOT installed by the previous 'pacman' installs. I found it easiest to copy them from the existing Gramps installation (where I installed all the language and spelling files during the AIO install).<br />
The originals were in the installation <code>/share/enchant/myspell</code> directory.<br />
I copied the whole 'myspell' directory above to my <code>c:\msys64\mingw32\share\enchant</code> directory so they could be found by the next step scripts. I used the Windows file explorer as that is easiest for me, but if you are familiar with the Linux <code>cp</code> command, you can do it from the MINGW32 shell.<br />
<br />
Before doing the AIO build, you may want to compare the existing <code>src/setup.py</code> and <code>src/grampsaio32.nsi</code> scripts with the latest ones available from other AIO installations. They change depending on the contents of the AIO and may point up other dependencies or changes. I use Notepad++ and its 'Compare' plugin for this, but feel free to use whatever tool you like.<br />
<br />
I use dir <code>~/aio</code> where my <code>setup.py</code>, <code>grampsX.py</code>, icons and nsis script is stored.<br />
<br />
cd ~<br />
cp -r "/c/Program Files (x86)/GrampsAIO32-5.1.0/src" aio<br />
<br />
=== Modifying the setup.py script ===<br />
The setup.py script should be located in <code>~/aio/setup.py</code>. Use you favorite editor to make sure following is right:<br />
* Python versions are correct; At the moment, Python3.6 is in use, however if your version is different, adjust the references to <code>python3.6</code> and <code>cpython-36m</code> and <code>python36</code> appropriately.<br />
* The 32/64 bit differences are correct; <code>gspawn-win64-helper</code> may need to change to <code>gspawn-win32-helper</code> or vice versa.<br />
* If you have added new dependencies, find the right place to put them into the script.<br />
<br />
Then use the following to create <code>~/aio/mingw32</code> with all files needed for bundle.<br />
=== Modifying the gramps.nsi script ===<br />
Open the <code>gramps.nsi</code> file with your favorite editor.<br />
<br />
Part of the contents should look something like the following:<br />
<pre><br />
!define APPNAME "GrampsAIO32"<br />
!define APPVERSION "5.1.0"<br />
!define APPBUILD "1"<br />
!define APPNAMEANDVERSION "${APPNAME} ${APPVERSION}"<br />
!define APP_PUBLISHER "The Gramps project"<br />
!define APP_WEB_SITE "http://gramps-project.org"<br />
BrandingText "Version ${APPVERSION}-${APPBUILD} -- a new maintenance release"<br />
</pre><br />
<br />
{{man note|Make sure your editor works|One user reported unicode problems with Notepad and then downloaded [https://notepad-plus-plus.org/ Notepad++].}}<br />
<br />
===== Increase the version number =====<br />
Change the '''APPVERSION''' line from "5.1.0" to "5.1.1" instead (or higher if making a newer version).<br />
<br />
===== If needed update APPNAME and APPBUILD =====<br />
Possibly APPNAME and APPBUILD will need changing too, depending on what you are trying to do. Generally the APPBUILD gets incremented if a second AIO release is made from the same version (because of a building issue.<br />
<br />
{{man note|If you are a power user|and have downloaded something other than a tar.gz file, see [[GrampsAIO-4_package_updating#Appendix_A|Appendix A]] to change APPBUILD.}}<br />
<br />
If necessary, change the BrandingText line to have the name of the new Gramps release instead of the old release name. Usually only necessary for major version changes.<br />
<br />
Then save that gramps.nsi file.<br />
<br />
=== Run the scripts ===<br />
python3 setup.py build_exe --no-compress<br />
<br />
Then I pass nsis script from ~/aio/mingw32/src to nsis.<br />
<br />
makensis ~/aio/mingw32/src/grampsaio32.nsi<br />
<br />
Note that after the compilation, the resulting files will be compressed.<br />
<br />
{{man warn|Please be patient|The the last part of the setup.py script and the NSIS package compression will probably take a while<br>'''-- OVER FIVE MINUTES FOR ME --'''}}<br />
<br />
{{man note|Experimenting with NSIS compression|See [[Building Gramps AIO#Appendix_B|Appendix B]] for power-user details, at this stage.}}<br />
<br />
The result is in <code>C:\msys64\home\user\aio\mingw32\src\GrampsAIO-5.1.1-1_win32.exe</code>.<br />
<br />
{{man warn|If you do this more than once, make sure to delete the result file, or it will get encoded into the next AIO. }}<br />
<br />
== Debugging ==<br />
I had several issues in this process. First of all, the mingw repositories are "rolling release", so every time you do a <code>pacman –Syuu</code> you will have different packages and potentially new issues.<br />
<br />
Take care to make sure that you don't overwrite any of the 'static' Gramps dependencies (gtk 3.18.9, bsddb 6.1.0, db 6.0.30 at the time of this writing) with newer versions, and if you do, use <code>pacman -U file.tar.xz</code> to revert them. Get this right FIRST, because if you build anything based on one of the static dependencies, it may end up not working on a newer version. If you do build something out of order, you may end up with mysterious import failures with messages that don't tell you what is really wrong. And it's really hard to debug the installed AIO, as it doesn't look like a typical Python process to the usual debuggers. Experience speaking.<br />
<br />
You may have to build one or more dependencies "the hard way"; that is download the PKGBUILD and any patches from a suitable source <code>https://github.com/Alexpux/MINGW-packages/trunk/mingw-w64-osmgpsmap-git</code> for example, and fix it up for newer versions and build it. See <code>https://github.com/msys2/msys2/wiki/Creating-packages</code> for help here. Or even download source code and compile yourself.<br />
<br />
I used the old DOS <code>tree /F /A > aionew.txt</code> command to make filename dumps from both the new AIO and a recent older one that was freshly installed in an empty directory. This ensures that there are no '.pyc' files to confuse the issue. Then I did a difference compare (using Notepad++) of the two to see what files are different. Any missing files in your new AIO are suspect (unless you did this deliberately).<br />
<br />
<br />
=== Appendix A ===<br />
==== Indicating newer APPBUILD's ====<br />
If you are a power user, you might have downloaded or used git to checkout the latest code in the grampsxx branch:<br />
<br />
https://codeload.github.com/gramps-project/gramps/zip/maintenance/gramps51<br />
<br />
but in any case, if you have downloaded something other than a gramps-release tar.gz (or .zip) file, say this in your top directory <code>~/grampsdev</code> (assuming you have installed Git for Windows):<br />
<br />
git rev-list --count HEAD<br />
<br />
and then<br />
<br />
git rev-parse --short HEAD<br />
<br />
and then put an "r" in front of the first string, followed by a hyphen ("-") and the second string, and then use the resulting combined string as your APPBUILD in the <code>gramps.nsi</code> file, for clarity.<br />
<br />
So for example your APPBUILD line might look like this:<br />
<br />
!define APPBUILD "r23381-25018d6"<br />
<br />
Then continue with the [[GrampsAIO-4_package_updating#Increase_the_version_number|NSIS package building]]<br />
<br />
==== Developers uploading to Sourceforge ====<br />
<br />
If you are a developer and plan to upload it to SourceForge and it is an AIO of (a forthcoming) "master" put it into:<br />
<br />
http://sourceforge.net/projects/gramps/files/Unstable<br />
<br />
but if it is an AIO for a maintenance branch, make a Snapshots folder in that branch and put it there, e.g.:<br />
<br />
http://sourceforge.net/projects/gramps/files/Stable/5.1.1/Snapshots<br />
<br />
so then the APPBUILD numbers will uniquely define that AIO.<br />
<br />
But note that the NSIS-generated filename will say (for instance) "5.1.2" even though it is really a "5.1.1" with bugs fixed, which is why it belongs in 5.1.1/Snapshots.<br />
<br />
Also see [[What to do for a release]]<br />
<br />
=== Appendix B ===<br />
====Experimenting with NSIS compression====<br />
If you are a power user and are experimenting with slight changes to the gramps.nsi script, you can drastically shorten the time needed to have NSIS generate an AIO package by commenting out these two lines (with a semicolon, a ";"):<br />
<br />
SetCompressor /SOLID /FINAL LZMA<br />
SetCompressorDictSize 128<br />
<br />
But if you are building an AIO which will be released to the public (put onto the official gramps files repo), you need to be '''very sure''' to uncomment '''both''' those lines '''first'''.<br />
<br />
==See also==<br />
* [[All In One Gramps Software Bundle for Windows]] for the Gramps 3.4.x and earlier series<br />
* [[Gramps for Windows with MSYS2]]<br />
* [[GrampsAIO cx freeze-based]]<br />
<br />
[[Category:Documentation]]<br />
[[Category:Developers/General]]<br />
[[Category:GEPS|W]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Building_Gramps_AIO_cx_freeze-based&diff=78394Building Gramps AIO cx freeze-based2020-05-25T22:59:57Z<p>GulliblePangolin: </p>
<hr />
<div>{{man warn|Gramps 4.2.8 and later.|Any comments and help (e.g. on wiki pages) are welcome.}}<br />
<br />
The '''Gramps''' "software bundle" for Windows or '''GrampsAIO''' is an all-in-one (a.k.a. '''"AIO"''') installation package of Gramps which includes all dependencies for the Windows platform.<br />
<br />
This tutorial describes how to generate a Windows AIO package from a development installation such as is created with [[Gramps for Windows with MSYS2]].<br />
<br />
It is intended for Windows users and does not attempt to describe how to do the same thing on Linux or a Mac.<br />
<br />
("AIO" means all-in-one, which means that everything you need to run Gramps is included in the one AIO file you download and then install -- all the related programs and library files which Gramps needs on Windows.)<br />
<br />
{{man note|Note|The first Gramps AIO package was created by an advanced Windows power-user named Josip. He is the one who evolved the AIO package and modified the AIO package over the years as Gramps has changed. Everything documented here initially done by him; this just documents some changes and tries to explain it for others. Any Gramps Windows user owes him a large debt of gratitude.}}<br />
<br />
{{man tip|Note|In this tutorial I will be creating a 32-bit AIO. The steps for creating a 64-bit version are quite similar, just a few editing changes to the files and scripts. }}<br />
<br />
==Prerequisites==<br />
You must have a development version of Gramps up and running. See [[Gramps for Windows with MSYS2]] which describes the process for a 64-bit installation. When following this process, you must change a few things for 32-bits.<br />
<br />
{{man note|Note|Pay close attention to the shell to use when running the various commands. Use <code>MSYS2 MSYS</code> for the <code>pacman</code> and <code>makepkg-mingw</code> steps and the <code>MSYS2 MINGW32/64</code> shell to run <code>python3 Gramps.py</code>.}}<br />
<br />
When the instructions say to use the <code>MSYS2 MINGW64</code> shell you should use <code>MSYS2 MINGW32</code> shell instead for 32-bit operation.<br />
<br />
Change the 'pacman' command install file prefixes from <code>mingw-w64-x86_64</code> to <code>mingw-w64-i686</code>.<br />
<br />
Because Josip does not have (as of this writing) some of the packages (gtk, db, bsddb3) that he built done for 32-bit we have to do them ourselves 'the hard way'.<br />
<br />
Change the <code>MINGW_INSTALLS=mingw64 makepkg-mingw –sLf</code> lines to <code>MINGW_INSTALLS=mingw32 makepkg-mingw -sLf</code>.<br />
<br />
=== Get the tools ===<br />
<br />
{{man note|Note|Josip uses a cx_Freeze with some changes he made to make the process a bit easier. I attempted to make similar changes, but we will have to build the utility. }}<br />
Download https://gramps-project.org/wiki/images/a/a3/Mingw-w64-python-cx_Freeze.zip [[:File:Mingw-w64-python-cx_Freeze.zip| (stored here)]] to a convenient location with your browser.<br />
<br />
I do my builds in the <code>c:\msys64\home\user\builds</code> directory, so we will make a new sub-directory for cx_Freeze there.<br />
<br />
I use 7-zip to extract to the <code>c:\msys64\home\user\builds\cx_Freeze</code> directory.<br />
<br />
<br />
{{man note|Note|Use <code>MSYS2 MSYS</code> shell.}}<br />
MINGW_INSTALLS=mingw32 makepkg-mingw -sLf<br />
pacman -U mingw-w64-i686-python3-cx_Freeze-5.0.2-1-any.pkg.tar.xz<br />
<br />
The patches included in the zip should fix up cx_Freeze for a bug where it tries to load an sqlite3.dll file, and to add properly optimized base files for Python startup (In the original version the 'optimize' functionality doesn't work).<br />
<br />
<br />
NSIS is a tool to build the actual installer. As of NSIS version 3.05 the standard nsis available from the MINGW archive works.<br />
pacman -S mingw-w64-i686-nsis<br />
<br />
If you have version 3.04, The version in the mingw system has a bug that makes displaying of the font files during the AIO install messed up. I've created a patch, so we need to build our own.<br />
Download https://gramps-project.org/wiki/index.php/File:Mingw-w64-nsis.zip [[:File:Mingw-w64-nsis.zip| (stored here)]] to a convenient location with your browser.<br />
<br />
Unzip and cd into the directory then:<br />
{{man note|Note|Use <code>MSYS2 MSYS</code> shell.}}<br />
MINGW_INSTALLS=mingw32 makepkg-mingw -sLf<br />
pacman -U mingw-w64-i686-nsis-3.0.4-1-any.pkg.tar.xz<br />
<br />
=== Get a reference AIO ===<br />
We also need the most recent version of Gramps AIO available. If it is for your branch, it is likely to have the closest scripts with minimal editing. Of course a newer version for a newer branch might have some changes in the scripts that deal with more recent dependencies. You may want to reference both in updating scripts for the new version. Get it installed so you can see the files from that installation.<br />
<br />
=== Install the old Gramps ===<br />
When you start the installer, it will ask you to select language and spell check files. Select all of them.<br />
It will then ask where you want it installed. You can install it where you want, as it is only a temporary location which you may delete afterward. But make a note of the folder since you will need to know it later. Also, it needs to be a new (empty) folder, not an already existing one.<br />
<br />
In this tutorial we'll say you tell the installer to put it into a new "<code>C:\Program Files (x86)\GrampsAIO32-5.1.0</code>" folder.<br />
<br />
Then double-click on the AIO executable to start the 5.1.0 installation. (If your Windows asks whether you will allow that program to change things on your computer, say yes of course.)<br />
<br />
You can put it anywhere you want but if you do, change the string "<code>C:\Program Files (x86)\GrampsAIO32-5.1.0</code>" in this tutorial to the actual name you used. But every time I use "<code>C:\Program Files (x86)\GrampsAIO32-5.1.0</code>" I mean the top of the tree where you installed the "old" AIO.<br />
<br />
After the installer is finished, the last window will offer you the opportunity to "Run" the Gramps you just installed, so you should un-click that box before you hit "Finish", since there is no need to run the old one.<br />
<br />
Similarly, you can delete the "GrampsAIO32 x.x.x" (or GrampsAIO64 one)" icon shortcut from your Desktop, since you won't be using it.<br />
<br />
=== Get Gramps installed in our development environment ===<br />
{{man note|Note|Use <code>MSYS2 MINGW32</code> shell.}}<br />
<br />
If you have not already done so as part of the prior steps, do the following:<br />
cd ~/grampsdev # my copy of git repo checked out with the branch you are building.<br />
<br />
python3 setup.py build<br />
<br />
To install preparatory to creating AIO do <br />
python3 setup.py install<br />
<br />
== Building the AIO ==<br />
Note: Gramps contains some spell checking files that are NOT installed by the previous 'pacman' installs. I found it easiest to copy them from the existing Gramps installation (where I installed all the language and spelling files during the AIO install).<br />
The originals were in the installation <code>/share/enchant/myspell</code> directory.<br />
I copied the whole 'myspell' directory above to my <code>c:\msys64\mingw32\share\enchant</code> directory so they could be found by the next step scripts. I used the Windows file explorer as that is easiest for me, but if you are familiar with the Linux <code>cp</code> command, you can do it from the MINGW32 shell.<br />
<br />
Before doing the AIO build, you may want to compare the existing <code>src/setup.py</code> and <code>src/grampsaio32.nsi</code> scripts with the latest ones available from other AIO installations. They change depending on the contents of the AIO and may point up other dependencies or changes. I use Notepad++ and its 'Compare' plugin for this, but feel free to use whatever tool you like.<br />
<br />
I use dir <code>~/aio</code> where my <code>setup.py</code>, <code>grampsX.py</code>, icons and nsis script is stored.<br />
<br />
cd ~<br />
cp -r "/c/Program Files (x86)/GrampsAIO32-5.1.0/src" aio<br />
<br />
=== Modifying the setup.py script ===<br />
The setup.py script should be located in <code>~/aio/setup.py</code>. Use you favorite editor to make sure following is right:<br />
* Python versions are correct; At the moment, Python3.6 is in use, however if your version is different, adjust the references to <code>python3.6</code> and <code>cpython-36m</code> and <code>python36</code> appropriately.<br />
* The 32/64 bit differences are correct; <code>gspawn-win64-helper</code> may need to change to <code>gspawn-win32-helper</code> or vice versa.<br />
* If you have added new dependencies, find the right place to put them into the script.<br />
<br />
Then use the following to create <code>~/aio/mingw32</code> with all files needed for bundle.<br />
=== Modifying the gramps.nsi script ===<br />
Open the <code>gramps.nsi</code> file with your favorite editor.<br />
<br />
Part of the contents should look something like the following:<br />
<pre><br />
!define APPNAME "GrampsAIO32"<br />
!define APPVERSION "5.1.0"<br />
!define APPBUILD "1"<br />
!define APPNAMEANDVERSION "${APPNAME} ${APPVERSION}"<br />
!define APP_PUBLISHER "The Gramps project"<br />
!define APP_WEB_SITE "http://gramps-project.org"<br />
BrandingText "Version ${APPVERSION}-${APPBUILD} -- a new maintenance release"<br />
</pre><br />
<br />
{{man note|Make sure your editor works|One user reported unicode problems with Notepad and then downloaded [https://notepad-plus-plus.org/ Notepad++].}}<br />
<br />
===== Increase the version number =====<br />
Change the '''APPVERSION''' line from "5.1.0" to "5.1.1" instead (or higher if making a newer version).<br />
<br />
===== If needed update APPNAME and APPBUILD =====<br />
Possibly APPNAME and APPBUILD will need changing too, depending on what you are trying to do. Generally the APPBUILD gets incremented if a second AIO release is made from the same version (because of a building issue.<br />
<br />
{{man note|If you are a power user|and have downloaded something other than a tar.gz file, see [[GrampsAIO-4_package_updating#Appendix_A|Appendix A]] to change APPBUILD.}}<br />
<br />
If necessary, change the BrandingText line to have the name of the new Gramps release instead of the old release name. Usually only necessary for major version changes.<br />
<br />
Then save that gramps.nsi file.<br />
<br />
=== Run the scripts ===<br />
python3 setup.py build_exe --no-compress<br />
<br />
Then I pass nsis script from ~/aio/mingw32/src to nsis.<br />
<br />
makensis ~/aio/mingw32/src/grampsaio32.nsi<br />
<br />
Note that after the compilation, the resulting files will be compressed.<br />
<br />
{{man warn|Please be patient|The the last part of the setup.py script and the NSIS package compression will probably take a while<br>'''-- OVER FIVE MINUTES FOR ME --'''}}<br />
<br />
{{man note|Experimenting with NSIS compression|See [[Building Gramps AIO#Appendix_B|Appendix B]] for power-user details, at this stage.}}<br />
<br />
The result is in <code>C:\msys64\home\user\aio\mingw32\src\GrampsAIO-5.1.1-1_win32.exe</code>.<br />
<br />
{{man warn|If you do this more than once, make sure to delete the result file, or it will get encoded into the next AIO. }}<br />
<br />
== Debugging ==<br />
I had several issues in this process. First of all, the mingw repositories are "rolling release", so every time you do a <code>pacman –Syuu</code> you will have different packages and potentially new issues.<br />
<br />
Take care to make sure that you don't overwrite any of the 'static' Gramps dependencies (gtk 3.18.9, bsddb 6.1.0, db 6.0.30 at the time of this writing) with newer versions, and if you do, use <code>pacman -U file.tar.xz</code> to revert them. Get this right FIRST, because if you build anything based on one of the static dependencies, it may end up not working on a newer version. If you do build something out of order, you may end up with mysterious import failures with messages that don't tell you what is really wrong. And it's really hard to debug the installed AIO, as it doesn't look like a typical Python process to the usual debuggers. Experience speaking.<br />
<br />
You may have to build one or more dependencies "the hard way"; that is download the PKGBUILD and any patches from a suitable source <code>https://github.com/Alexpux/MINGW-packages/trunk/mingw-w64-osmgpsmap-git</code> for example, and fix it up for newer versions and build it. See <code>https://github.com/msys2/msys2/wiki/Creating-packages</code> for help here. Or even download source code and compile yourself.<br />
<br />
I used the old DOS <code>tree /F /A > aionew.txt</code> command to make filename dumps from both the new AIO and a recent older one that was freshly installed in an empty directory. This ensures that there are no '.pyc' files to confuse the issue. Then I did a difference compare (using Notepad++) of the two to see what files are different. Any missing files in your new AIO are suspect (unless you did this deliberately).<br />
<br />
<br />
=== Appendix A ===<br />
==== Indicating newer APPBUILD's ====<br />
If you are a power user, you might have downloaded or used git to checkout the latest code in the grampsxx branch:<br />
<br />
https://codeload.github.com/gramps-project/gramps/zip/maintenance/gramps51<br />
<br />
but in any case, if you have downloaded something other than a gramps-release tar.gz (or .zip) file, say this in your top directory <code>~/grampsdev</code> (assuming you have installed Git for Windows):<br />
<br />
git rev-list --count HEAD<br />
<br />
and then<br />
<br />
git rev-parse --short HEAD<br />
<br />
and then put an "r" in front of the first string, followed by a hyphen ("-") and the second string, and then use the resulting combined string as your APPBUILD in the <code>gramps.nsi</code> file, for clarity.<br />
<br />
So for example your APPBUILD line might look like this:<br />
<br />
!define APPBUILD "r23381-25018d6"<br />
<br />
Then continue with the [[GrampsAIO-4_package_updating#Increase_the_version_number|NSIS package building]]<br />
<br />
==== Developers uploading to Sourceforge ====<br />
<br />
If you are a developer and plan to upload it to SourceForge and it is an AIO of (a forthcoming) "master" put it into:<br />
<br />
http://sourceforge.net/projects/gramps/files/Unstable<br />
<br />
but if it is an AIO for a maintenance branch, make a Snapshots folder in that branch and put it there, e.g.:<br />
<br />
http://sourceforge.net/projects/gramps/files/Stable/5.1.1/Snapshots<br />
<br />
so then the APPBUILD numbers will uniquely define that AIO.<br />
<br />
But note that the NSIS-generated filename will say (for instance) "5.1.2" even though it is really a "5.1.1" with bugs fixed, which is why it belongs in 5.1.1/Snapshots.<br />
<br />
Also see [[What to do for a release]]<br />
<br />
=== Appendix B ===<br />
====Experimenting with NSIS compression====<br />
If you are a power user and are experimenting with slight changes to the gramps.nsi script, you can drastically shorten the time needed to have NSIS generate an AIO package by commenting out these two lines (with a semicolon, a ";"):<br />
<br />
SetCompressor /SOLID /FINAL LZMA<br />
SetCompressorDictSize 128<br />
<br />
But if you are building an AIO which will be released to the public (put onto the official gramps files repo), you need to be '''very sure''' to uncomment '''both''' those lines '''first'''.<br />
<br />
==See also==<br />
* [[All In One Gramps Software Bundle for Windows]] for the Gramps 3.4.x and earlier series<br />
* [[Gramps for Windows with MSYS2]]<br />
* [[GrampsAIO cx freeze-based]]<br />
<br />
[[Category:Documentation]]<br />
[[Category:Developers/General]]<br />
[[Category:GEPS|W]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_Keybindings&diff=78393Gramps 5.1 Wiki Manual - Keybindings2020-05-25T22:56:24Z<p>GulliblePangolin: /* Handy Shortcuts */</p>
<hr />
<div>{{man index|Gramps 5.1 Wiki Manual - FAQ|Gramps 5.1 Wiki Manual - Command Line|5.1}}<br />
{{languages|Gramps_5.1_Wiki_Manual_-_Keybindings}}<br />
{{#vardefine:chapter|B}}<br />
{{#vardefine:figure|0}}<br />
This appendix lists keybindings (also known as ''Keyboard shortcuts'' or ''hotkeys'') that can be used in the Gramps dialogs as an alternative to using the mouse.<br />
<br />
Some keybindings require the user to press a single key or a sequence of keys one after the other. Other keybindings require pressing and holding several keys simultaneously. <br />
== List Views ==<br />
=== Common keybindings ===<br />
<br />
{{man tip|Keyboards are not all the same!|<br />
Keybindings may depend on the keyboard layout (localization) and on your computer&rsquo;s Operating System.{{-}}<br />
[[File:windows_180x160.png|128px]] [[File:macos_200x200.png|128px]] [[File:Linux_220x261.png|128px]] [[File:Bsd daemon.png|128px]]}}<br />
The following keybindings are available in all category [[Gramps_Glossary#view|views]].<br />
{|{{prettytable}}<br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME <br />
|-<!--- ############ WARNING once an id="x" number has been assigned do not change as referenced else where in UserManual --><br />
|<!-- Action/Function --> id="1" | [[Gramps_5.1_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|Manage family trees]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|O}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|O}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|O}}<br />
|-<br />
|<!-- Action/Function --> id="2" | [[Gramps_5.1_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Import family tree]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|I}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|I}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|I}}<br />
|-<br />
|<!-- Action/Function --> id="3" | [[Gramps_5.1_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|Export family tree]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|E}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|E}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|E}}<br />
|-<br />
|<!-- Action/Function --> id="4" | Changes to the next [[Gramps_5.1_Wiki_Manual_-_Main_Window#Switching_Categories|Category]].<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|N}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|N}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|N}}<br />
|-<br />
|<!-- Action/Function --> id="5" |Changes to the previous [[Gramps_5.1_Wiki_Manual_-_Main_Window#Switching_Categories|Category]].<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|P}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|P}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|P}}<br />
|-<br />
|<!-- Action/Function --> id="45" |Change [[Gramps_5.1_Wiki_Manual_-_Main_Window#Switching_Categories|Category]]<br>to Category number 0/1/2/../9<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|1}}<br>{{Man key press|Ctrl|2}}<br>{{Man key press|Ctrl|3}} ...<br />
|<!-- Mac OS --> |{{Man key press|Cmd|1}}<br>{{Man key press|Cmd|2}}<br>{{Man key press|Cmd|3}}..<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|1}}<br>{{Man key press|Ctrl|2}}<br>{{Man key press|Ctrl|3}}..<br />
|-<br />
|<!-- Action/Function --> id="6" |Within the Category changes the [[Gramps_5.1_Wiki_Manual_-_Main_Window#Switching_Views|view]]<br>to view mode number 0/1/2/../9<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Alt|1}}<br>{{Man key press|Ctrl|Alt|2}}<br>{{Man key press|Ctrl|Alt|3}} ...<br />
|<!-- Mac OS --> |{{Man key press|Cmd|Opt|1}}<br>{{Man key press|Cmd|Opt|2}}<br>{{Man key press|Cmd|Opt|3}}..<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Alt|1}}<br>{{Man key press|Ctrl|Alt|2}}<br>{{Man key press|Ctrl|Alt|3}}..<br />
|-<br />
|<!-- Action/Function --> id="8" |[[Gramps_5.1_Wiki_Manual_-_Navigation#Using_the_Clipboard|Open the Clipboard]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|B}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|B}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|B}}<br />
|-<br />
|<!-- Action/Function --> id="9" |Add the selected item as a [[Gramps_5.1_Wiki_Manual_-_Navigation#Bookmarks|bookmark]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|D}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|D}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|D}}<br />
|-<br />
|<!-- Action/Function --> id="10" |[[Gramps_5.1_Wiki_Manual_-_Navigation#Bookmarks|Organize the bookmarks]]<br />
|<!-- Microsoft Windows --> |{{Man key press|Shift|Ctrl|D}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|D}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Shift|Ctrl|D}}<br />
|-<br />
|<!-- Action/Function --> id="11" |Open the {{man label|[[Gramps_5.1_Wiki_Manual_-_Navigation#Edit|Undo History]]}} dialog<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|H}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|H}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|H}}<br />
|-<br />
|<!-- Action/Function --> id="12" |Jump to an Gramps ID<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|J}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|J}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|J}}<br />
|-<br />
|<!-- Action/Function --> id="13" |Move to previous item in history<br />
|<!-- Microsoft Windows --> |{{Man key press|Alt|Left}} (Left arrow)<br />
|<!-- Mac OS --> |{{Man key press|Ctrl|Opt|Left}} (Left arrow)<br />
|<!-- KDE/GNOME --> |{{Man key press|Alt|Left}} (Left arrow)<br />
|-<br />
|<!-- Action/Function --> id="14" |Move to next item in history<br />
|<!-- Microsoft Windows --> |{{Man key press|Alt|Right}} (Right arrow)<br />
|<!-- Mac OS --> |{{Man key press|Ctrl|Opt|Right}} (Right arrow)<br />
|<!-- KDE/GNOME --> |{{Man key press|Alt|Right}} (Right arrow)<br />
|-<br />
|<!-- Action/Function --> id="15" |Go to the '''[[Gramps_5.1_Wiki_Manual_-_Settings#Setting_Home_person|Home Person]]'''<br />
|<!-- Microsoft Windows --> |{{Man key press|Alt|Home}}<br />
|<!-- Mac OS --> |<br />
|<!-- KDE/GNOME --> |{{Man key press|Alt|Home}}<br />
|-<br />
|<!-- Action/Function --> id="16" |Same action as the [[File:Gramps-config.png|20px]] Configure active view button<br />
|<!-- Microsoft Windows --> |{{Man key press|Shift|Ctrl|C}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|C}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Shift|Ctrl|C}}<br />
|-<br />
|<!-- Action/Function --> id="7" |Toggle the left gramplet sidebar ([[Gramps_5.1_Wiki_Manual_-_Main_Window#Navigator|Navigator]] panel)<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|M}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|M}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|M}}<br />
|-<br />
|<!-- Action/Function --> id="17" |Toggle the right gramplet sidebar ([[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]])<br />
|<!-- Microsoft Windows --> |{{Man key press|Shift|Ctrl|R}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|R}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Shift|Ctrl|R}}<br />
|-<br />
|<!-- Action/Function --> id="18" |Toggle the bottom gramplet sidebar ([[Gramps_5.1_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]])<br />
|<!-- Microsoft Windows --> |{{Man key press|Shift|Ctrl|B}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|B}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Shift|Ctrl|B}}<br />
|-<br />
|<!-- Action/Function --> id="19" |Undo<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Z}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|Z}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Z}}<br />
|-<br />
|<!-- Action/Function --> id="20" |Do again<br />
|<!-- Microsoft Windows --> |{{Man key press|Shift|Ctrl|Z}}<br />
|<!-- Mac OS --> |{{Man key press|Shift|Cmd|Z}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Shift|Ctrl|Z}}<br />
|-<br />
|<!-- Action/Function --> id="21" |Quit Gramps<br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Q}}<br />
|<!-- Mac OS --> |{{Man key press|Cmd|Q}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Q}}<br />
|-<br />
|<!-- Action/Function --> id="xx" | [[Gramps_5.1_Wiki_Manual_-_Navigation#Add|Add/Create]] a new object (Opens the related Editor)<br>Person<br>Family<br>Event<br>Place<br>Source<br>Citation<br>Repository<br>Media<br>Note<br />
|<!-- Microsoft Windows --> |<br>{{Man key press|Shift|Alt|P}}<br>{{Man key press|Shift|Alt|F}}<br>{{Man key press|Shift|Alt|E}}<br>{{Man key press|Shift|Alt|L}}<br>{{Man key press|Shift|Alt|S}}<br>{{Man key press|Shift|Alt|C}}<br>{{Man key press|Shift|Alt|R}}<br>{{Man key press|Shift|Alt|M}}<br>{{Man key press|Shift|Alt|N}}<br />
|<!-- Mac OS --> |<br>{{Man key press|Shift|Ctrl|Opt|P}}<br>{{Man key press|Shift|Ctrl|Opt|F}}<br>{{Man key press|Shift|Ctrl|Opt|E}}<br>{{Man key press|Shift|Ctrl|Opt|L}}<br>{{Man key press|Shift|Ctrl|Opt|S}}<br>{{Man key press|Shift|Ctrl|Opt|C}}<br>{{Man key press|Shift|Ctrl|Opt|R}}<br>{{Man key press|Shift|Ctrl|Opt|M}}<br>{{Man key press|Shift|Ctrl|Opt|N}}<br />
|<!-- KDE/GNOME --> |<br>{{Man key press|Shift|Alt|P}}<br>{{Man key press|Shift|Alt|F}}<br>{{Man key press|Shift|Alt|E}}<br>{{Man key press|Shift|Alt|L}}<br>{{Man key press|Shift|Alt|S}}<br>{{Man key press|Shift|Alt|C}}<br>{{Man key press|Shift|Alt|R}}<br>{{Man key press|Shift|Alt|M}}<br>{{Man key press|Shift|Alt|N}}<br />
|}<br />
<br />
=== All List Views bindings ===<br />
<br />
The following bindings are available in all list views: People, Families, Events, Places, Sources, Citations, Repositories, Media and Notes View.<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME<br />
!Note<br />
|-<br />
|<!-- Action/Function --> id="22" |Edits the selected list item <br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Enter}}<br />
|<!-- Mac OS --> |<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Enter}}<br />
|<!-- Note --> |<br />
|- <br />
|<!-- Action/Function --> id="23" |Adds a new item to the database <br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Insert}}<br />
|<!-- Mac OS --> |<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Insert}}<br />
|<!-- Note --> |<br />
|- <br />
|<!-- Action/Function --> id="24" |Deletes the selected list item <br />
|<!-- Microsoft Windows --> |{{Man key press|Ctrl|Delete}}<br />
|<!-- Mac OS --> |<br />
|<!-- KDE/GNOME --> |{{Man key press|Ctrl|Delete}}<br />
|<!-- Note --> |<br />
|-<br />
|<!-- Action/Function --> id="46" |Activate the {{man button|Find}} field<br />
|!-- Microsoft Windows --> |{{Man key press|Ctrl|F}}<br />
|!-- Mac OS --> |{{Man key press|Cmd|F}}<br />
|!-- KDE/GNOME --> |{{Man key press|Ctrl|F}}<br />
|<!-- Note --> | List view interactive search ahead / Quick search<br />
|}<br />
<br />
=== People View bindings ===<br />
<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME<br />
|- <br />
|<!-- Action/Function --> id="25" |Expands and hides entries of the selected surname in Group mode<br />
|<!-- Microsoft Windows --> |{{Man key press|Enter}}<br />
|<!-- Mac OS --> |{{Man key press|Enter}}<br />
|<!-- KDE/GNOME --> |{{Man key press|Enter}}<br />
|}<br />
<br />
==Editors==<br />
<br />
=== Editor Tab bindings ===<br />
These bindings work on the tab pages of the editors (so not on the labels of the tabs!, press tab on label to move to tabpage content).<br />
<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME<br />
|- <br />
|<!-- Action/Function --> id="26" |Same action as the {{icon|Stock_edit}} button when that button is present<br />
|{{Man key press|Enter}}<br />
|{{Man key press|Enter}}<br />
|{{Man key press|Enter}}<br />
|- <br />
|<!-- Action/Function --> id="27" |Same action as the {{icon|Stock_add}} button when that button is present<br />
|{{Man key press|Insert}}<br />
|<br />
|{{Man key press|Insert}}<br />
|- <br />
|<!-- Action/Function --> id="28" |Same action as the {{icon|Stock_remove}} button when that button is present<br />
|{{Man key press|Delete}}<br />
|<br />
|{{Man key press|Delete}}<br />
|- <br />
|<!-- Action/Function --> id="29" |Same action as the {{man button|Share}} button when that button is present<br />
|{{Man key press|Ctrl|O}}<br />
|{{Man key press|Cmd|O}}<br />
|{{Man key press|Ctrl|O}}<br />
|- <br />
|<!-- Action/Function --> id="30" |Change tabpage to the tabpage to the left<br />
|{{Man key press|Alt|Left}} (Left arrow)<br />
|{{Man key press|Ctrl|Alt|Left}} (Left arrow)<br />
|{{Man key press|Alt|Left}} (Left arrow)<br />
|- <br />
|<!-- Action/Function --> id="31" |Change tabpage to the tabpage to the right<br />
|{{Man key press|Alt|Right}} (Right arrow)<br />
|{{Man key press|Ctlr|Alt|Right}} (Right arrow)<br />
|{{Man key press|Alt|Right}} (Right arrow)<br />
|}<br />
<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Mouse Key<br />
|- <br />
|<!-- Action/Function --> id="32" |Call up [https://en.wikipedia.org/wiki/Context_menu context menu] popup<br />
!Right-click<br />
|- <br />
|<!-- Action/Function --> id="33" |Same action as the {{icon|Stock_edit}} {{man button|Edit}} button when that button is present<br />
!Double-click<br />
|- <br />
|<!-- Action/Function --> id="34" |Common action that is not the same as {{icon|Stock_edit}} {{man button|Edit}} button. Eg: on Family Editor Child tab, edit child<br />
!Middle-click<br />
|}<br />
<br />
=== Editor bindings ===<br />
These bindings work on Editors by activating focus or by changing state of toggle buttons ([[Accessibility]]).<br />
<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME<br />
|- <br />
|<!-- Action/Function --> id="35" |Change the privacy status.<br />
|{{Man key press|Ctrl|P}}<br />
|{{Man key press|Cmd|P}}<br />
|{{Man key press|Ctrl|P}}<br />
|- <br />
|<!-- Action/Function --> id="36" |Call the Date editor (if present).<br />
|{{Man key press|Ctrl|D}}<br />
|{{Man key press|Cmd|D}}<br />
|{{Man key press|Ctrl|D}}<br />
|- <br />
|<!-- Action/Function --> id="37" |Activate the {{icon|Stock_add}} {{man button|Add}} button (if present).<br />
|{{Man key press|Ctrl|A}}<br />
|{{Man key press|Cmd|A}}<br />
|{{Man key press|Ctrl|A}}<br />
|- <br />
|<!-- Action/Function --> id="38" |Activate the {{icon|Stock_edit}} {{man button|Edit}} button (if present).<br />
|{{Man key press|Ctrl|E}}<br />
|{{Man key press|Cmd|E}}<br />
|{{Man key press|Ctrl|E}}<br />
|- <br />
|<!-- Action/Function --> id="39" |Activate the {{man button|Select}} button (if present).<br />
|{{Man key press|Ctrl|S}}<br />
|{{Man key press|Cmd|S}}<br />
|{{Man key press|Ctrl|S}}<br />
|- <br />
|<!-- Action/Function --> id="40" |Activate the {{man button|Father}} button (if present).<br />
|{{Man key press|Ctrl|F}}<br />
|{{Man key press|Cmd|F}}<br />
|{{Man key press|Ctrl|F}}<br />
|- <br />
|<!-- Action/Function --> id="41" |Activate the {{man button|Mother}} button (if present).<br />
|{{Man key press|Ctrl|M}}<br />
|{{Man key press|Cmd|M}}<br />
|{{Man key press|Ctrl|M}}<br />
|}<br />
<br />
==Handy Shortcuts==<br />
<br />
{|{{prettytable}} <br />
!Action/Function<br />
!Microsoft Windows<br />
!Mac OS<br />
!KDE/GNOME <br />
!Note<br />
|-<br />
|<!-- Action/Function --> id="42" |Full screen<br />
|{{man key press|F11}}<br />
|<br />
|{{man key press|F11}}<br />
|Maximises Gramps to use the Full screen<br />
|-<br />
|<!-- Action/Function --> id="43" |Show this user manual<br />
|{{man key press|F1}}<br />
|{{man key press|F1}}<br />
|{{man key press|F1}}<br />
|<br />
|-<br />
|<!-- Action/Function --> id="44" |Select the {{man button|OK}} button<br />
|{{man key press|Alt}}+{{man key press|O}}<br />
|<br />
|<br />
|Handy for use with low resolution screens<br />
|-<br />
|<!-- Action/Function --> id="45" |Select the {{man button|Cancel}} button<br />
|{{man key press|Esc}}<br />
|<br />
|<br />
|Handy for use with low resolution screens<br />
|}<br />
<br />
== See also ==<br />
* [http://en.wikipedia.org/wiki/Table_of_keyboard_shortcuts Table of keyboard shortcuts] - for major operating systems.<br />
<br />
{{-}}<br />
{{man index|Gramps 5.1 Wiki Manual - FAQ|Gramps 5.1 Wiki Manual - Command Line|5.1}}<br />
{{languages|Gramps_5.1_Wiki_Manual_-_Keybindings}}<br />
{{grampsmanualcopyright}}<br />
<br />
[[Category:Documentation]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Addon:HtmlView&diff=78374Addon:HtmlView2020-05-25T09:27:25Z<p>GulliblePangolin: /* Prerequisites */</p>
<hr />
<div>{{Third-party plugin}}<br />
{{man tip|History|The HtmlView Addon was previously part of the Gramps core plugins know as the [[Gramps_4.1_Wiki_Manual_-_Categories#Web_Category|Web Category]] from Version 3.2 to Version 4.1 and was hidden by default. This addons was created for use by the original geography views in gramps 3.x.}}<br />
<br />
[[File:Html View category.png|thumb|right|450px|Html View]]<br />
<br />
The Html View ({{man label|Web}} Category) allows you to browse web pages from within Gramps.<br />
<br />
Simply type the web address, and the page will be displayed in the normal way.<br />
<br />
==Prerequisites==<br />
In order to use the ''Html View'':<br />
* You must ensure that the [https://webkitgtk.org/ webkit] version 3.0 module is installed<br />
<br />
<code>gir-webkit</code><br />
<br />
Ubuntu 16.04 & 18.04 only:<br />
<br />
<code>gir1.2-webkit-3.0</code><br />
<br />
<!--(On Ubuntu install <code>gir1.2-webkit-2-4.0</code>) (which is webkit2 version 4.0 ) does not work! actually requires the older gir1.2-webkit-3.0 which is "webkit 1 version 3.0" and is not available on Ubuntu 20.04 ( https://pkgs.org/download/gir1.2-webkit-3.0 )<br />
<br />
If you install the newer <code>gir1.2-webkit-2-4.0</code> and change the code lines to<br />
<br />
gi.require_version('WebKit2', '4.0')<br />
from gi.repository import WebKit2 as webkit<br />
<br />
the category shows but you get the following error<br />
<br />
Traceback (most recent call last):<br />
File "/usr/lib/python3/dist-packages/gramps/gui/viewmanager.py", line 817, in __create_page<br />
page_display = page.get_display()<br />
File "/usr/lib/python3/dist-packages/gramps/gui/views/pageview.py", line 421, in get_display<br />
self.top = self.build_interface()<br />
File "/usr/lib/python3/dist-packages/gramps/gui/views/pageview.py", line 163, in build_interface<br />
self.widget = self.build_widget()<br />
File "/home/me/.gramps/gramps51/plugins/HtmlView/htmlview.py", line 350, in build_widget<br />
self.renderer = RendererWebkit()<br />
File "/home/me/.gramps/gramps51/plugins/HtmlView/htmlview.py", line 267, in __init__<br />
self.frame = self.window.get_main_frame()<br />
AttributeError: 'WebView' object has no attribute 'get_main_frame'<br />
--><br />
<br />
Once installed the new {{man label|Web}} Category will appear in the navigator.<br />
<br />
{{-}}<br />
<br />
==History==<br />
[[File:Geoview4.png|right|450px|thumb|The original Geoview using the HTML View backend]]<br />
* [https://gramps-project.org/blog/2008/12/gramps-is-not-a-web-browser-yes/ Gramps is not a web browser …. yes?], December 10th, 2008, by Benny (originally supported two backends WebKit or Mozilla ( gtkmozembed ).)<br />
* [http://gramps.1791082.n4.nabble.com/HTML-view-td4669792.html HTML view] 2015,''...This module was linked to the old geography view before 3.3...I'll move it into the third-party addons repository..''<br />
<br />
* [https://gramps-project.org/bugs/view.php?id=8023 8023] HTML view fails to load<br />
* [https://gramps-project.org/bugs/view.php?id=11628 11628] ''..This addon is not any more supported...It will never work on windows because dependencies are too heavy ( the size of the package)...It can work only on linux if you install the prerequisite packages....This addons was created for the geography views in gramps 3.x...''<br />
* [[GEPS_029:_GTK3-GObject_introspection_Conversion#WebKit_for_Htmlrenderer]] - The htmlview requires WebKit. Introspection bindings for this is available, in Ubuntu package gir1.2-webkit-3.0<br />
* [[Linux:Build_from_source#Linux_package_requirements]] - python-webkit python-gtkmozembed (WebKitgtk pywebkitgtk) Required for the HTML view <br />
* Code on Github [https://github.com/gramps-project/addons-source/tree/master/HtmlView addons-source/tree/master/HtmlView] the comments mention:<br />
** Html Renderer - Can use the Webkit or Gecko ( Mozilla ) library<br />
** We use firstly webkit if it is present. If not, we use gtkmozembed.<br />
<br />
[[Category:Plugins]]<br />
[[Category:Developers/General]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Addon:HtmlView&diff=78373Addon:HtmlView2020-05-25T09:27:00Z<p>GulliblePangolin: /* Prerequisites */</p>
<hr />
<div>{{Third-party plugin}}<br />
{{man tip|History|The HtmlView Addon was previously part of the Gramps core plugins know as the [[Gramps_4.1_Wiki_Manual_-_Categories#Web_Category|Web Category]] from Version 3.2 to Version 4.1 and was hidden by default. This addons was created for use by the original geography views in gramps 3.x.}}<br />
<br />
[[File:Html View category.png|thumb|right|450px|Html View]]<br />
<br />
The Html View ({{man label|Web}} Category) allows you to browse web pages from within Gramps.<br />
<br />
Simply type the web address, and the page will be displayed in the normal way.<br />
<br />
==Prerequisites==<br />
In order to use the ''Html View'':<br />
* You must ensure that the [https://webkitgtk.org/ webkit] version 3.0 module is installed<br />
<br />
<code>gir-webkit</code><br />
<br />
Ubuntu 16.04 & 18.04 only:<br />
<br />
<code>gir1.2-webkit-3.0</code><br />
<br />
<!--(On Ubuntu install <code>gir1.2-webkit-2-4.0</code>) (which is webkit2 version 4.0 ) does not work! actually requires the older gir1.2-webkit-3.0 which is "webkit 1 version 3.0" and is not available on Ubuntu 20.04 ( https://pkgs.org/download/gir1.2-webkit-3.0 )<br />
<br />
If you install the newer <code>gir1.2-webkit-2-4.0</code> and change the code lines to<br />
<br />
gi.require_version('WebKit2', '4.0')<br />
from gi.repository import WebKit2 as webkit<br />
<br />
the category shows but you get the following error<br />
<br />
Traceback (most recent call last):<br />
File "/usr/lib/python3/dist-packages/gramps/gui/viewmanager.py", line 817, in __create_page<br />
page_display = page.get_display()<br />
File "/usr/lib/python3/dist-packages/gramps/gui/views/pageview.py", line 421, in get_display<br />
self.top = self.build_interface()<br />
File "/usr/lib/python3/dist-packages/gramps/gui/views/pageview.py", line 163, in build_interface<br />
self.widget = self.build_widget()<br />
File "/home/me/.gramps/gramps51/plugins/HtmlView/htmlview.py", line 350, in build_widget<br />
self.renderer = RendererWebkit()<br />
File "/home/me/.gramps/gramps51/plugins/HtmlView/htmlview.py", line 267, in __init__<br />
self.frame = self.window.get_main_frame()<br />
AttributeError: 'WebView' object has no attribute 'get_main_frame'<br />
--><br />
<br />
Once installed the new {{man label|Web}} Category will appear the navigator.<br />
<br />
{{-}}<br />
<br />
==History==<br />
[[File:Geoview4.png|right|450px|thumb|The original Geoview using the HTML View backend]]<br />
* [https://gramps-project.org/blog/2008/12/gramps-is-not-a-web-browser-yes/ Gramps is not a web browser …. yes?], December 10th, 2008, by Benny (originally supported two backends WebKit or Mozilla ( gtkmozembed ).)<br />
* [http://gramps.1791082.n4.nabble.com/HTML-view-td4669792.html HTML view] 2015,''...This module was linked to the old geography view before 3.3...I'll move it into the third-party addons repository..''<br />
<br />
* [https://gramps-project.org/bugs/view.php?id=8023 8023] HTML view fails to load<br />
* [https://gramps-project.org/bugs/view.php?id=11628 11628] ''..This addon is not any more supported...It will never work on windows because dependencies are too heavy ( the size of the package)...It can work only on linux if you install the prerequisite packages....This addons was created for the geography views in gramps 3.x...''<br />
* [[GEPS_029:_GTK3-GObject_introspection_Conversion#WebKit_for_Htmlrenderer]] - The htmlview requires WebKit. Introspection bindings for this is available, in Ubuntu package gir1.2-webkit-3.0<br />
* [[Linux:Build_from_source#Linux_package_requirements]] - python-webkit python-gtkmozembed (WebKitgtk pywebkitgtk) Required for the HTML view <br />
* Code on Github [https://github.com/gramps-project/addons-source/tree/master/HtmlView addons-source/tree/master/HtmlView] the comments mention:<br />
** Html Renderer - Can use the Webkit or Gecko ( Mozilla ) library<br />
** We use firstly webkit if it is present. If not, we use gtkmozembed.<br />
<br />
[[Category:Plugins]]<br />
[[Category:Developers/General]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Addon:HtmlView&diff=78372Addon:HtmlView2020-05-25T09:26:02Z<p>GulliblePangolin: /* Prerequisites */</p>
<hr />
<div>{{Third-party plugin}}<br />
{{man tip|History|The HtmlView Addon was previously part of the Gramps core plugins know as the [[Gramps_4.1_Wiki_Manual_-_Categories#Web_Category|Web Category]] from Version 3.2 to Version 4.1 and was hidden by default. This addons was created for use by the original geography views in gramps 3.x.}}<br />
<br />
[[File:Html View category.png|thumb|right|450px|Html View]]<br />
<br />
The Html View ({{man label|Web}} Category) allows you to browse web pages from within Gramps.<br />
<br />
Simply type the web address, and the page will be displayed in the normal way.<br />
<br />
==Prerequisites==<br />
In order to use the ''Html View'':<br />
* You must ensure that the [https://webkitgtk.org/ webkit] version 3.0 module is installed<br />
<br />
<code>gir-webkit</code><br />
<br />
Ubuntu 16.04 & 18.04 only:<br />
<br />
<code>gir1.2-webkit-3.0</code><br />
<br />
<!--(On Ubuntu install <code>gir1.2-webkit-2-4.0</code>) (which is webkit2 version 4.0 ) does not work! actually requires the older gir1.2-webkit-3.0 which is "webkit 1 version 3.0" and is not available on Ubuntu 20.04 ( https://pkgs.org/download/gir1.2-webkit-3.0 )<br />
<br />
If you install the newer <code>gir1.2-webkit-2-4.0</code> and change the code lines to<br />
<br />
gi.require_version('WebKit2', '4.0')<br />
from gi.repository import WebKit2 as webkit<br />
<br />
the category shows but you get the following error<br />
<br />
Traceback (most recent call last):<br />
File "/usr/lib/python3/dist-packages/gramps/gui/viewmanager.py", line 817, in __create_page<br />
page_display = page.get_display()<br />
File "/usr/lib/python3/dist-packages/gramps/gui/views/pageview.py", line 421, in get_display<br />
self.top = self.build_interface()<br />
File "/usr/lib/python3/dist-packages/gramps/gui/views/pageview.py", line 163, in build_interface<br />
self.widget = self.build_widget()<br />
File "/home/me/.gramps/gramps51/plugins/HtmlView/htmlview.py", line 350, in build_widget<br />
self.renderer = RendererWebkit()<br />
File "/home/me/.gramps/gramps51/plugins/HtmlView/htmlview.py", line 267, in __init__<br />
self.frame = self.window.get_main_frame()<br />
AttributeError: 'WebView' object has no attribute 'get_main_frame'<br />
--><br />
<br />
* When you have done this, the new {{man label|Web}} Category will appear the navigator.<br />
<br />
{{-}}<br />
<br />
==History==<br />
[[File:Geoview4.png|right|450px|thumb|The original Geoview using the HTML View backend]]<br />
* [https://gramps-project.org/blog/2008/12/gramps-is-not-a-web-browser-yes/ Gramps is not a web browser …. yes?], December 10th, 2008, by Benny (originally supported two backends WebKit or Mozilla ( gtkmozembed ).)<br />
* [http://gramps.1791082.n4.nabble.com/HTML-view-td4669792.html HTML view] 2015,''...This module was linked to the old geography view before 3.3...I'll move it into the third-party addons repository..''<br />
<br />
* [https://gramps-project.org/bugs/view.php?id=8023 8023] HTML view fails to load<br />
* [https://gramps-project.org/bugs/view.php?id=11628 11628] ''..This addon is not any more supported...It will never work on windows because dependencies are too heavy ( the size of the package)...It can work only on linux if you install the prerequisite packages....This addons was created for the geography views in gramps 3.x...''<br />
* [[GEPS_029:_GTK3-GObject_introspection_Conversion#WebKit_for_Htmlrenderer]] - The htmlview requires WebKit. Introspection bindings for this is available, in Ubuntu package gir1.2-webkit-3.0<br />
* [[Linux:Build_from_source#Linux_package_requirements]] - python-webkit python-gtkmozembed (WebKitgtk pywebkitgtk) Required for the HTML view <br />
* Code on Github [https://github.com/gramps-project/addons-source/tree/master/HtmlView addons-source/tree/master/HtmlView] the comments mention:<br />
** Html Renderer - Can use the Webkit or Gecko ( Mozilla ) library<br />
** We use firstly webkit if it is present. If not, we use gtkmozembed.<br />
<br />
[[Category:Plugins]]<br />
[[Category:Developers/General]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Addon:HtmlView&diff=78371Addon:HtmlView2020-05-25T09:25:36Z<p>GulliblePangolin: /* Prerequisites */</p>
<hr />
<div>{{Third-party plugin}}<br />
{{man tip|History|The HtmlView Addon was previously part of the Gramps core plugins know as the [[Gramps_4.1_Wiki_Manual_-_Categories#Web_Category|Web Category]] from Version 3.2 to Version 4.1 and was hidden by default. This addons was created for use by the original geography views in gramps 3.x.}}<br />
<br />
[[File:Html View category.png|thumb|right|450px|Html View]]<br />
<br />
The Html View ({{man label|Web}} Category) allows you to browse web pages from within Gramps.<br />
<br />
Simply type the web address, and the page will be displayed in the normal way.<br />
<br />
==Prerequisites==<br />
In order to use the ''Html View'':<br />
* You must ensure that the [https://webkitgtk.org/ webkit] version 3.0 module is installed<br />
<br />
<code>gir-webkit</code><br />
<br />
Ubuntu 16.04 & 18.04 only:<br />
<code>gir1.2-webkit-3.0</code><br />
<br />
<!--(On Ubuntu install <code>gir1.2-webkit-2-4.0</code>) (which is webkit2 version 4.0 ) does not work! actually requires the older gir1.2-webkit-3.0 which is "webkit 1 version 3.0" and is not available on Ubuntu 20.04 ( https://pkgs.org/download/gir1.2-webkit-3.0 )<br />
<br />
If you install the newer <code>gir1.2-webkit-2-4.0</code> and change the code lines to<br />
<br />
gi.require_version('WebKit2', '4.0')<br />
from gi.repository import WebKit2 as webkit<br />
<br />
the category shows but you get the following error<br />
<br />
Traceback (most recent call last):<br />
File "/usr/lib/python3/dist-packages/gramps/gui/viewmanager.py", line 817, in __create_page<br />
page_display = page.get_display()<br />
File "/usr/lib/python3/dist-packages/gramps/gui/views/pageview.py", line 421, in get_display<br />
self.top = self.build_interface()<br />
File "/usr/lib/python3/dist-packages/gramps/gui/views/pageview.py", line 163, in build_interface<br />
self.widget = self.build_widget()<br />
File "/home/me/.gramps/gramps51/plugins/HtmlView/htmlview.py", line 350, in build_widget<br />
self.renderer = RendererWebkit()<br />
File "/home/me/.gramps/gramps51/plugins/HtmlView/htmlview.py", line 267, in __init__<br />
self.frame = self.window.get_main_frame()<br />
AttributeError: 'WebView' object has no attribute 'get_main_frame'<br />
--><br />
<br />
* When you have done this, the new {{man label|Web}} Category will appear the navigator.<br />
<br />
{{-}}<br />
<br />
==History==<br />
[[File:Geoview4.png|right|450px|thumb|The original Geoview using the HTML View backend]]<br />
* [https://gramps-project.org/blog/2008/12/gramps-is-not-a-web-browser-yes/ Gramps is not a web browser …. yes?], December 10th, 2008, by Benny (originally supported two backends WebKit or Mozilla ( gtkmozembed ).)<br />
* [http://gramps.1791082.n4.nabble.com/HTML-view-td4669792.html HTML view] 2015,''...This module was linked to the old geography view before 3.3...I'll move it into the third-party addons repository..''<br />
<br />
* [https://gramps-project.org/bugs/view.php?id=8023 8023] HTML view fails to load<br />
* [https://gramps-project.org/bugs/view.php?id=11628 11628] ''..This addon is not any more supported...It will never work on windows because dependencies are too heavy ( the size of the package)...It can work only on linux if you install the prerequisite packages....This addons was created for the geography views in gramps 3.x...''<br />
* [[GEPS_029:_GTK3-GObject_introspection_Conversion#WebKit_for_Htmlrenderer]] - The htmlview requires WebKit. Introspection bindings for this is available, in Ubuntu package gir1.2-webkit-3.0<br />
* [[Linux:Build_from_source#Linux_package_requirements]] - python-webkit python-gtkmozembed (WebKitgtk pywebkitgtk) Required for the HTML view <br />
* Code on Github [https://github.com/gramps-project/addons-source/tree/master/HtmlView addons-source/tree/master/HtmlView] the comments mention:<br />
** Html Renderer - Can use the Webkit or Gecko ( Mozilla ) library<br />
** We use firstly webkit if it is present. If not, we use gtkmozembed.<br />
<br />
[[Category:Plugins]]<br />
[[Category:Developers/General]]</div>GulliblePangolinhttps://www.gramps-project.org/wiki/index.php?title=Addon:HtmlView&diff=78370Addon:HtmlView2020-05-25T09:22:27Z<p>GulliblePangolin: /* History */ Gioto thanks for the detective work</p>
<hr />
<div>{{Third-party plugin}}<br />
{{man tip|History|The HtmlView Addon was previously part of the Gramps core plugins know as the [[Gramps_4.1_Wiki_Manual_-_Categories#Web_Category|Web Category]] from Version 3.2 to Version 4.1 and was hidden by default. This addons was created for use by the original geography views in gramps 3.x.}}<br />
<br />
[[File:Html View category.png|thumb|right|450px|Html View]]<br />
<br />
The Html View ({{man label|Web}} Category) allows you to browse web pages from within Gramps.<br />
<br />
Simply type the web address, and the page will be displayed in the normal way.<br />
<br />
==Prerequisites==<br />
In order to use the ''Html View'':<br />
* You must ensure that the [https://webkitgtk.org/ webkit] version 3.0 module is installed<br />
<br />
<code>gir-webkit</code><br />
<br />
<!--(On Ubuntu install <code>gir1.2-webkit-2-4.0</code>) (which is webkit2 version 4.0 ) does not work! actually requires the older gir1.2-webkit-3.0 which is "webkit 1 version 3.0" and is not available on Ubuntu 20.04 ( https://pkgs.org/download/gir1.2-webkit-3.0 )<br />
<br />
If you install the newer <code>gir1.2-webkit-2-4.0</code> and change the code lines to<br />
<br />
gi.require_version('WebKit2', '4.0')<br />
from gi.repository import WebKit2 as webkit<br />
<br />
the category shows but you get the following error<br />
<br />
Traceback (most recent call last):<br />
File "/usr/lib/python3/dist-packages/gramps/gui/viewmanager.py", line 817, in __create_page<br />
page_display = page.get_display()<br />
File "/usr/lib/python3/dist-packages/gramps/gui/views/pageview.py", line 421, in get_display<br />
self.top = self.build_interface()<br />
File "/usr/lib/python3/dist-packages/gramps/gui/views/pageview.py", line 163, in build_interface<br />
self.widget = self.build_widget()<br />
File "/home/me/.gramps/gramps51/plugins/HtmlView/htmlview.py", line 350, in build_widget<br />
self.renderer = RendererWebkit()<br />
File "/home/me/.gramps/gramps51/plugins/HtmlView/htmlview.py", line 267, in __init__<br />
self.frame = self.window.get_main_frame()<br />
AttributeError: 'WebView' object has no attribute 'get_main_frame'<br />
--><br />
<br />
* When you have done this, the new {{man label|Web}} Category will appear the navigator.<br />
<br />
{{-}}<br />
<br />
==History==<br />
[[File:Geoview4.png|right|450px|thumb|The original Geoview using the HTML View backend]]<br />
* [https://gramps-project.org/blog/2008/12/gramps-is-not-a-web-browser-yes/ Gramps is not a web browser …. yes?], December 10th, 2008, by Benny (originally supported two backends WebKit or Mozilla ( gtkmozembed ).)<br />
* [http://gramps.1791082.n4.nabble.com/HTML-view-td4669792.html HTML view] 2015,''...This module was linked to the old geography view before 3.3...I'll move it into the third-party addons repository..''<br />
<br />
* [https://gramps-project.org/bugs/view.php?id=8023 8023] HTML view fails to load<br />
* [https://gramps-project.org/bugs/view.php?id=11628 11628] ''..This addon is not any more supported...It will never work on windows because dependencies are too heavy ( the size of the package)...It can work only on linux if you install the prerequisite packages....This addons was created for the geography views in gramps 3.x...''<br />
* [[GEPS_029:_GTK3-GObject_introspection_Conversion#WebKit_for_Htmlrenderer]] - The htmlview requires WebKit. Introspection bindings for this is available, in Ubuntu package gir1.2-webkit-3.0<br />
* [[Linux:Build_from_source#Linux_package_requirements]] - python-webkit python-gtkmozembed (WebKitgtk pywebkitgtk) Required for the HTML view <br />
* Code on Github [https://github.com/gramps-project/addons-source/tree/master/HtmlView addons-source/tree/master/HtmlView] the comments mention:<br />
** Html Renderer - Can use the Webkit or Gecko ( Mozilla ) library<br />
** We use firstly webkit if it is present. If not, we use gtkmozembed.<br />
<br />
[[Category:Plugins]]<br />
[[Category:Developers/General]]</div>GulliblePangolin