Changes

== How the developer uses it Why DenominoViso was developed ==

Some examples If your tree of how I use a page created by DenominoViso.# I am primarily looking for information on ancestors. The large overview shown by /descendants grows a page created by DenominoVisobit bigger, helps me to easily find which ancestors traditional graphical representations run out of space and you are lagging behind: the branch is tiny compared left with neighboring branchesviewing only part of your tree.# Finding death records is harder then birth/baptism The DenominoViso addon mitigates this by dropping names and marriage records in Dutch archives. So temporarily I typically set death to something like "after xxxx". I can now enter "after" in other textual details from the search box and search for "death events", all people boxes that still miss their real death event show make up.# Some sources are expected to contain a considerable (geographic) group of my ancestorstree so that many more boxes, for example tax records. Because in Gramps I have entered the details of that tax record in the description field thus a larger section of the eventtree, I can search on this be put in the page created by DenominoViso. Those persons not showing up while it is expected, can easily be identified for further researchview.

== Why = How ===

If your tree of ancestors/descendants grows a bit bigger, traditional graphical representations run out of space and you are left with viewing only part The consequence of your tree. The DenominoViso plugin mitigates this by dropping names and other textual details from is that the boxes that make up a tree so that many more boxesdocument needs to be interactive to determine which box belongs to which person, thus DenominoViso creates a graphical webpage in SVG/HTML/javascript. Such a larger section of the tree, document can be put in viewdisplayed with standard compliant browsers such as Microsoft Edge, Firefox or Opera (Old version of Internet Explorer will '''not''' work.).

=== What's in a name ===The consequence of this name DenominoViso is that the document needs to be interactive to determine which box belongs to which person, thus DenominoViso creates derived from a graphical webpage in SVG/HTML/javascriptuse-case I had not realized before I wrote this plugin. Such It means something like "let's have a document look at namegiving". It turns out that in my family not only family names can be displayed traced back over centuries, but also firstnames where children are typically named after their grandparents or great grandparents if there are many of them. Pages created with standard compliant browsers such as Firefox or Opera (Internet Explorer will '''not''' do)the DenominoViso plugin are ideal for this, just enter the specific part of the name in the search field and search for "Name".

What is seen on === How the webpage is typically a tree structure consisting of many boxes. Hovering the mouse over a box shows the name of that person on the statusbar (browser settings must allow javascript to set text on the statusline, something which is at present typically switched off by browsers in their standard configuration). Clicking on a box displays the known details about that person.developer uses it ===

== What's in Some examples of how I use a name ==page created by DenominoViso.* I am primarily looking for information on ancestors. The name large overview shown by a page created by DenominoViso , helps me to easily find which ancestors are lagging behind: the branch is derived from a use-case tiny compared with neighboring branches.* Finding death records is harder then birth/baptism and marriage records in Dutch archives. So temporarily I had not realized before I wrote this plugin. It means typically set death to something like "let's have a look at namegivingafter xxxx". It turns out that in my family not only family names I can be traced back over centuries, but also firstnames where children are typically named now enter "after their grandparents or great grandparents if there are many of them. Pages created with the DenominoViso plugin are ideal for this, just enter the specific part of the name " in the search field box and search for "Namedeath events", all people that still miss their real death event show up. ==Version History==* Gramps 4 - Update Some sources are expected to contain a considerable (geographic) group of Gramps 3 versionmy ancestors, to support GTK+3 and python 3for example tax records. No new functionality was added.* Because in Gramps 3 - An update I have entered the details of that tax record in the description field of the Gramps 2.x versionevent, to work with I can search on this in the new plugin-architecturepage created by DenominoViso. No new functionality was addedThose persons not showing up while it is expected, can easily be identified for further research.