See the Delete Recent File List plugin in the Plugin Store. There may be other plugins and other use cases where FH does not have commands to adjust some registry keys.
* Plugin Author Guidelines in KB
- tatewise
- Megastar
- Posts: 28921
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Plugin Author Guidelines in KB
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
- ColeValleyGirl
- Megastar
- Posts: 5643
- Joined: 28 Dec 2005 22:02
- Family Historian: V7
- Location: Cirencester, Gloucestershire
- Contact:
Re: Plugin Author Guidelines in KB
Good catch.tatewise wrote: ↑06 Apr 2024 16:00See the Delete Recent File List plugin in the Plugin Store. There may be other plugins and other use cases where FH does not have commands to adjust some registry keys.
Helen Wright
ColeValleyGirl's family history
ColeValleyGirl's family history
- Mark1834
- Megastar
- Posts: 2644
- Joined: 27 Oct 2017 19:33
- Family Historian: V7
- Location: South Cheshire, UK
Re: Plugin Author Guidelines in KB
That's why the first draft says must not modify the Registry, apart from the specific Family Historian keys, and then only if essential to the stated plugin function, such as restoring a backup of user settings. - restoring is an illustrative example of what cannot be achieved by other methods, but not an exclusive one.
Mark Draper
- Mark1834
- Megastar
- Posts: 2644
- Joined: 27 Oct 2017 19:33
- Family Historian: V7
- Location: South Cheshire, UK
Re: Plugin Author Guidelines in KB
Thanks again for the comments, there were some good points made.
The two main themes seem to be improving the document focus, and fine-tuning of some of the detailed items.
The recommendations and general description overlapped partly with the existing Getting Started Writing Plugins page, so we have removed these from the draft and merged them into the existing page.
Referencing specific plugins was very useful to refine what plugins must and mustn’t do, so that is now included.
Taking these points together, we have therefore deleted the original draft, and replaced it with a new page, Privacy and Security Standards for Published Plugins. That gives it a much sharper focus, as it documents solely the new standards that published plugins (here and in the Plugin Store) will be expected to adhere to, so removing any ambiguity around what’s required and what’s just recommended.
The two main themes seem to be improving the document focus, and fine-tuning of some of the detailed items.
The recommendations and general description overlapped partly with the existing Getting Started Writing Plugins page, so we have removed these from the draft and merged them into the existing page.
Referencing specific plugins was very useful to refine what plugins must and mustn’t do, so that is now included.
Taking these points together, we have therefore deleted the original draft, and replaced it with a new page, Privacy and Security Standards for Published Plugins. That gives it a much sharper focus, as it documents solely the new standards that published plugins (here and in the Plugin Store) will be expected to adhere to, so removing any ambiguity around what’s required and what’s just recommended.
Mark Draper