Is it viable to include @bjpcorp .svg scalable icons from the GTheme repository in the 6.1 release?
It will open the discussion (and experimentation opportunities) about the efficiencies of native and scaled icons. (Memory/resource usage, printing implications, developer maintenance issues and coding consistency.)
GThemes resources:
theme-icons/gramps-geo-birth2.svg
theme-icons/gramps-geo-death2.svg
theme-icons/gramps-geo-marriage2.svg
gtheme-icons/gramps-geo-mainmap.svg
gtheme-icons/gramps-geo-altmap.svg
To replace:
images/hicolor/scalable/actions/gramps-geo-birth.svg
images/hicolor/scalable/actions/gramps-geo-death.svg
images/hicolor/scalable/actions/gramps-geo-marriage.svg
images/hicolor/scalable/actions/gramps-geo-mainmap.svg
images/hicolor/scalable/actions/gramps-geo-altmap.svg
Replacing the .svg will NOT change the display of the Geography map views. Those views apparently use one of the “native” .png bitmap files in the images/highcolor from the images/hicolor/22x22/actions, images/hicolor/24x24/actions, or images/hicolor/48x48/actions folders. Deleting the native bitmap versions does force a fallback. However, it seems reasonable to first determine if falling back to scalable .svg pins will create an unbearable burden or memory leaks when there are thousands of pins.
Nor will it affect the images/Webstuff redundant .png files… used in web reports. (Which probably ought to use .svg so that print quality from Web Reports would improve.)
After inserting the
gramps-geo-marriage.svg into the scalable, Gramps will use the new image for any of the interpolated: sizes but the .png files where they exist for the native sizes.
