Changes

 == Description ==<hr>

The ''Filtered Descendant Report'' is directly based on the ''Detailed Descendant Report''. As such, itincludes all the options (which make sense) in addition to some new ones. Because multiplefamily branches can be included, the Henry and d'Aboville numbering systems options were removed(considering that people common to more than one branch will get the number assigned to them when theyare first found).

The main difference is that a filter can be used to determine who to include in the report (so thatyou can have several family branches) instead of basing all the descendants from a single person. Thekey is to find at least one common person to all the rules in the filter. If at least one commonperson is found, the generations can be aligned so that it doesn't matter if the head of each branchis in the same generation.

In order to support this report, enhanced versions of some of the Gramps code is included so as tonot require modifications of the Gramps core itself. The enhanced changes are finding their wayinto the core, so it's only a matter of time until this plugin will no longer need to ship those changes.A list of enhancements can be found after the list of differences.

'''CAVEAT''': the filter is meant to be an OR filter (At least one rule must apply), meaning that we areexpecting the report to consist of one or more family branches, where each rule dictates the start of a branch.This plugin has NOT been stress tested over different varieties of rules. It does work with one or morerules and will treat the filter as if 'At least one rule must apply' is set (even if not). The pluginwill complain if no common people are found across all rules.

'''CAVEAT''': the only supported output file format currently is ''OpenDocument Text Enhanced''. Runningthe plugin with any other output format will cause an error (because the other format backends haven'tbeen updated to support the needed enhancements).

'''CAVEAT''': this is a second version, and as such has much missing that people might want. One obvious oneis support for ALL backend report formats, not just ODF. Also, not currently possible to get thephoto date to put into the caption. Also, no translation for messages (everything is currently English-only).This version is being released for Gramps v3.3 and to see if there is any interest outside myself :-{},and possibly to get my enhancement changes into the core if they seem useful.

As explained above, the filter can have one or more rules to allow multiple branches to be in the samereport. A person, common to ALL rules will align the generations. If no common person is found, anerror will be issued.

An added option allows the user to specify the report title. For ''Detailed Descendant Report'', thisis automatically set based on the name of the 'Center Person'. For ''Filtered Descendant Report'', this isautomatically set to the name of the selected filter, but can be overridden by the user.

This option (on the '''Content''' tab) tells the plugin whether to turn any http, https, or mailto links foundin text (i.e. notes, endnotes, etc.) to be real clickable links. Turning this option off results in thebehavior found in ''Detailed Descendant Report'' (that is, no URLs are made clickable). Turning it on willcause those URLs found to be clickable in the output file (if possible).

This option (on the '''Content''' tab) tells the plugin whether to add information to the report that hasbeen marked 'private'. Turning this option off results in the behavior found in''Detailed Descendant Report'' (that is, all information is included in the report). Turning it onwill cause the plugin to NOT include anything marked private. After all, what good is the private

This option (on the new Caption tab) specifies what should be in photo captions. For fulldetails on what can be specified, see:

Images now appear in the report document exactly how they appear within the Gramps UI. That is, if an imagehas been cropped, it will be cropped the same way in the report. The ''Detailed Descendant Report''behavior was to just insert the image so that the report showed the entire image.

Turned image manipulation functions into a real class so that an image file only needs to be openedonce (instead of everytime an ImgManip function is called). Also added a method to return the imageDPI (if available). This supports showing cropped images in the report file.