OK, I paraphrased slightly - it actually says that Local Media Objects are a "feature that although allowed by FH is not well supported as it prefers to use Media Records in most Media dialogues". Either way, I took that as an indication that most FH users won't be familiar with the term so might struggle with selecting the correct option.
I would probably leave image handling to the specialist apps (such as IrfanView), but it's an individual author's judgement over where to put the balance between features and complexity. Once allowed in, it's certainly harder to remove!
* Export Gedcom File plugin new features
- Mark1834
- Megastar
- Posts: 2458
- Joined: 27 Oct 2017 19:33
- Family Historian: V7
- Location: South Cheshire, UK
Re: Export Gedcom File plugin new features
Mark Draper
Re: Export Gedcom File plugin new features
I'm not going to go over most of the points being discussed here, but I did want to add that the media manipulation section is an absolute must for me and it is hugely convenient to have it in the GEDCOM export plugin. Yes, it could be argued that it is scope-creep from merely exporting a GEDCOM file, and yes, it could be done elsewhere if necessary, but I find it most convenient where it is.
There is a lot of complexity in the plugin, and it took me some time to understand the different options and which ones were pertinent to what I wanted to do. There was some trial and error involved. I believe most of this complexity has arisen because Mike has responded to user requests over time and built many add-ons. Also, the large number of export target products means there will always be a lot of options. It is sometimes it is worth taking a step back and seeing what can be simplified, but it doesn't necessarily mean taking an axe to things. For example, the media scaling options can just be ignored by people not needing them.
There is a lot of complexity in the plugin, and it took me some time to understand the different options and which ones were pertinent to what I wanted to do. There was some trial and error involved. I believe most of this complexity has arisen because Mike has responded to user requests over time and built many add-ons. Also, the large number of export target products means there will always be a lot of options. It is sometimes it is worth taking a step back and seeing what can be simplified, but it doesn't necessarily mean taking an axe to things. For example, the media scaling options can just be ignored by people not needing them.
Adrian Cook
Researching Cook, Summers, Phipps and Bradford, mainly in Wales and the South West of England
Researching Cook, Summers, Phipps and Bradford, mainly in Wales and the South West of England
- tatewise
- Megastar
- Posts: 28341
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Export Gedcom File plugin new features
I have revised the plugin dialogues, mostly on the Basic Options tab, in response to recent comments.
It is difficult to change the drop-list architecture because the legacy users 'sticky' settings are saved in that form.
However, the wording tries to follow FH more closely where possible or is more explanatory.
Preliminary changes have been made to allow some Character Set Encoding options to be eliminated in a later version.
It also fixes some minor issues and now reformats the _UID field to suit destination products.
See the attached Export Gedcom File plugin Version 4.6.7 Date 27 Nov 2021 ZIP file.
Download then right-click and Extract All... before installing into FH.
It is difficult to change the drop-list architecture because the legacy users 'sticky' settings are saved in that form.
However, the wording tries to follow FH more closely where possible or is more explanatory.
Preliminary changes have been made to allow some Character Set Encoding options to be eliminated in a later version.
It also fixes some minor issues and now reformats the _UID field to suit destination products.
See the attached Export Gedcom File plugin Version 4.6.7 Date 27 Nov 2021 ZIP file.
Download then right-click and Extract All... before installing into FH.
Last edited by tatewise on 19 Feb 2022 17:19, edited 1 time in total.
Reason: Attachment deleted as later version is in the Plugin Store.
Reason: Attachment deleted as later version is in the Plugin Store.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
- Mark1834
- Megastar
- Posts: 2458
- Joined: 27 Oct 2017 19:33
- Family Historian: V7
- Location: South Cheshire, UK
Re: Export Gedcom File plugin new features
It's more verbose, but definitely clearer without the reference to Local Media Objects. I was scratching my head for a moment about the button label "Reset these Str+ Options" until I realised that it was a reference to the GEDCOM Destination code.
IMO, it might be clearer to have a fixed label along the lines of "Reset Options to Destination Defaults" so you don't need the pop-up to tell you what it does. It's also simpler code for future maintenance!
IMO, it might be clearer to have a fixed label along the lines of "Reset Options to Destination Defaults" so you don't need the pop-up to tell you what it does. It's also simpler code for future maintenance!
Mark Draper
- tatewise
- Megastar
- Posts: 28341
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Export Gedcom File plugin new features
See the attached Export Gedcom File plugin Version 4.6.9 Date 09 Feb 2022 ZIP file.
Download then right-click and Extract All... before installing into FH.
It works for FH V7 (and probably for FH V6 and FH V5 too but they need testing).
It offers the same features as the earlier version but now allows all file paths & names to use any Unicode characters.
i.e. It uses the same library and techniques that were introduced with the Show Project Statistics plugin in the thread Lua Error in Show Project Statistics 2.6 (20118).
It would be a useful test if anyone can use the plugin on a Project with exotic Unicode characters in the Project name or in any Media file names that are included with the export.
Download then right-click and Extract All... before installing into FH.
It works for FH V7 (and probably for FH V6 and FH V5 too but they need testing).
It offers the same features as the earlier version but now allows all file paths & names to use any Unicode characters.
i.e. It uses the same library and techniques that were introduced with the Show Project Statistics plugin in the thread Lua Error in Show Project Statistics 2.6 (20118).
It would be a useful test if anyone can use the plugin on a Project with exotic Unicode characters in the Project name or in any Media file names that are included with the export.
Last edited by tatewise on 19 Feb 2022 17:20, edited 2 times in total.
Reason: Attachment deleted as later version is in the Plugin Store.
Reason: Attachment deleted as later version is in the Plugin Store.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry