* Narrative web: Some improvements
- Event type, Date and place in bold
- Family events shifted one column on the left
- ancestortree css file before narrative-screen to allow modification
- Adaptation for all themes
Fixes#11393
* Narrative web: forgot a comma during last merge
* Allow scrolling if the ancestor tree is too large
* Translation of alternate stylesheets name
* Crash when using the family map
* Translate only the css title, not the file name
* Some minor corrections to css files
* Narrative web: open layers optimizations
* Narrative web: open layers and link in popup
* Narrative web: some events missing in popup
* Narrative web: Reference date column too large.
Allow the place title to use the maximum of width
* NarrativeWeb: shift children from one column
- adapt the css files to the new table
- some inconsistencies between the source and the css
* Make the drop down menu button size usable
* NarrativeWeb: Incorrect rendering when use of
alternate place name
* NarWeb: removing the unused image heigth option
* Click on image link gives a not found URL.
If the image used in home, introduction or contact page
is not already associated by a filtered object, we have a 404 error
* NarWeb: Index images and thumbnails pages optional
* Narweb: Improper Notes subtitle in web pages
* Narweb: List index truncated after 999
* Narweb: NarrativeWeb usage enhancements
* Narweb: avoid duplicate files in archive.
* Narweb: Add an optional news and updates page:
When you have a big database and you make intensive updates, it's
useful to have a list of the last modified objects.
you can select the period to show and how many records to see per object type.
* Narweb: forgot to add the module updates.py
* Narweb: some minor changes (pylint, img index bug)
* Popups don't work with the last openlayers version
It only needs to move the scripts at the end of the html body.
Use addEventListener instead of onload in the html body statement.
* Narweb: some popup problems
* Narweb: better score for pylint
* WEBCAL: Have config files for multiple databases.
* WEBCAL: best management for the narrative web link
* WEBCAL: use arrows, compress monthname and arrows
adapt the css files accordingly
* WEBCAL: use arrows in one day within a year
compress monthname and arrows
adapt the css files accordingly
* WEBCAL: index go now to the current month.
before this patch, the default month for the year calendar
was the month found at the web calendar generation.
Now, even if you create this report 8 months ago, the current
index will point to the current month.
* WEBCAL: trailing space.
* WEBCAL: year glance + some pylint improvements
* WEBCAL: incorrect width size with Mainz css.
* WEBCAL: problem with Visually css file
* WEBCAL: The table cell is highlighted when hover.
* WEBCAL: better pylint score.
* WEBCAL: Better rendering for full yer at a glance
* WEBCAL: better rendering on small devices
* WEBCAL: better quality code
Fixes#10124
Fix up Event Editors Place display for bidi text with Gramps ID (PR 924)
Some versions of Gtk/Pango have trouble with text containing both LTR and RTL characters. The bug notes this shows up in our Event Editor on the 'Place" field, where we have the place displayer title and the Gramps ID concatenated into the same string.
In older versions of Gtk (3.18.9 tested) the bracket around the Gramps ID would get mangled to the beginning of the string:
<images>
In newer versions of Gtk (3.24.3 tested) it was better to start with:
<images>
The older version of Gtk/Pango doesn't seem to properly interpret all of the potential Unicode bidi control characters, so the fix shown is the best I can do. The fixed version of the newer Gtk version is what is desired.
I note that the Place displayer should be fixed up to use more appropriate separators than just commas for RTL text, but that is another issue.
Fixes#11410
The bug submitter noticed that the GEDCOM export contained translated strings in the MEDI lines of his export. GEDCOM should contain English values for most such cases where 'types' are exported.
I scanned the export code for other potential cases, and found:
* Certain unexpected event types on individuals (Marriage)
* Certain unexpected event types on families (Immigration, Residence, etc.)
* Pedigree types that were not standardized on PEDI,_FREL,_MREL (Sponsored, Unknown)
* Family Attributes other than Number if children (Caste, Description, National etc.)
* Personal Attributes other than Caste, Description, ID, National, number of children, SSN (Occupation etc.)
* The MEDI types of this bug report...
Fixes#10762
User "petpil" (Gramps Bugtracker) noted that the Calculate Estimated Dates addon would not expand the size of its window content when the window was stretched. That addon used the ToolManagedWindowBatch which uses a Gtk Notebook to support several tabs. He also submitted a patch which fixes the problem.
The Gtk.Container.add method originally used apparently did not have expand/fill settings to allow the expansion. The Gtk.Box.pack_start used instead does.
I tested this with all the users of ToolManagedWindowBatch and ToolManagedWindow which inherit from ToolManagedWindowBase, and did not see any bad/unexpected side effects. The Calculate Estimated Dates addon was the only one that really could use this, as it was the only one which I spotted using a potentially large widget in the notebook tab.
* Max ages should be divisible by 5 to avoid out of range
errors.
* The chart width should be greater than 45 to look right and
avoid division by zero errors.
Fixes#11384
It turns out the changes was actually changing the wrong config setting...
I had to look this one up. Using a lambda like this is called a 'closure' by some; what is happening is that the value 'constant' is being evaluated at the time the lambda is called, not when it is assigned. So in this particular bit of code the preference setting was actually changing 'preferences.family-relation-type' (the value of the variable 'constant' set a bit after the lambda definition.
I reverted this particular bit of code, as I think this kind of Python knowledge is pretty obscure (I could have just used a different unique name for the 'constant' variable).
Fixes#11390
As it says, if Family Tree name contained non-ASCII characters, the titlebar on Windows would display it wrong. Turned out to be reading of a utf8 file without the 'encoding' set. On Windows this results in using the default encoding which is one of the code pages, NOT utf8.
that passes
If user has only a single font available that passes check for the Genealogical Symbols being all present, the original code crashed. Apparently never tested... #598Fixes#11395
Fixes#11380, #11339
In prior versions of Gramps you could use the undo/redo keys to edit items in the text entries. This no longer works.
This is related to the changes to suppress odd characters and leading/trailing spaces. The Gtk.Entry.set_text() call is effectively clearing the undo/redo list at every keystroke or when you leave the field.
In this PR I move the odd characters cleanup into UndoableEntry.do_insert_text instead of MonitoredEntry.
I scanned the users of MonitoredEntry and they all appeared to use Glade files, I scanned the glade files for anyone using just plain Entry (none found), they all appeared to use UndoableEntry or ValidatableMaskedEntry, so this should cover everyone.
* Narrative web: Ancestor's tree display looks weird
Solves the following:
- Person boxes overlap
- Some person boxes partially visible or hidden
Fixes#11382
* Narrative web: some cleanup in ancestortree.css
* Narrative web : ancestor tree and long names.
* Adapt ancestor tree css file for all themes
Via email a user noted a bug when "Gramps -v" was used with Gtk not installed (and gi was).
When the "gi.require_version('Gtk', '3.0')" was added during Gramps 5.0.0 timeframe, a corresponding exception was not.
Fixes#11366
* Make PedigreeView listen on event update signals.
The PedigreeView was not listening for updates on events, so changes to a birthday or death would not be reflected in the view.
* Remove comment about signal side-effects.
Fixes#11378
For the index, toc, bookmark etc. normal XML escape is correct, the original code also added sub-tags for line break and tab which was NOT correct.
New narrative web and web calendar features:
* Allow urls in the user's css files
* Allow alternate stylesheets in pages for narrative web and webcal
* Webcal: incorrect results when divorce event.
* Some pylint improvements
Resolves#11336.
Useful when you create a site web, you don't need to create a new
web when you are testing the stylesheets. The final user can change
the stylesheet for the current page.
i.e. on Firefox: View -> Page style -> The stylesheet
