Installed GrampsAIO-6.1.0-beta1-1_win64 and imported a copy of my tree.
The FamilySearch icon in the status bar alerts… Not logged in to FamilySearch
From the menu Family Trees >> FamilySearch Sign In… User consent declined
I opened my default browser and signed in.
And what happens next?
I’m not clear on how to use the FS plugin.
Before we can issue authentication keys, the new FamilySearch Integration will need to be certified by FamilySearch. I am just waiting for our middleware to be installed before asking FamilySearch to begin their certification process. Perhaps Sam can give a progress update on this.
An alternative for testing would be to use our development key to access the FamilySearch beta server. @SourceAirbender Is this still possible?
Yup! Direct mode should still work if you run gramps with
GRAMPS_FS_ENABLE_DIRECT=1 python3 -m gramps
or
GRAMPS_FS_ENABLE_DIRECT=1 GRAMPS_FS_DEBUG=1 python3 -m gramps
You just have to set the correct mode in the corresponding preferences tab
Still no access.
In Preferences >> Integrations there is a blank Middleware base URL and Middleware access coee (issued secret) and entering GRAMPS_FS_ENABLE_DIRECT=1 python3 -m gramps or GRAMPS_FS_ENABLE_DIRECT=1 GRAMPS_FS_DEBUG=1 python3 -m gramps into either field does not allow sign in.
Hard to test when there is no access.
I believe SourceAirbender was giving command line to run, not values for the URL field.
Having GRAMPS_FS_ENABLE_DIRECT=1 in the environment when Gramps runs should allow direct connection to the test server without an access code
I strongly feel that there should be NO startup alerts if the FamilySearch service is not running nor attempts to touch an external service without the user enabling a preferences switch. (The should extended to any external service, including Addon Manager or polling RSS feeds.)
Or perhaps there could be a multi-level settings in the Warnings tab of Preferences for each service? Then we could have the “Never ask again” suppression dialog. But the first time use of Gramps should not have a lot of warnings, ‘do this first’ or other barriers.
The single dialog for the Tip of the Day is enough startup ‘noise’. And we could have a default 1st-use tip with about important options in Preferences. (Like whether to Tag/Cite every record of the initial import.)
On my Android smart phone, I can restrict application Permissions with:
I believe that the 6.1 release is to make it easier for the FamilySearch folks to alpha test. Once their alpha test is passed, our community can start beta testing.
Requiring them to build-from-source would probably have given the first impression that Gramps will be too hard for their volunteers at FamilySearch Centers. So it would have made sense for their executives to push resources for our collaboration to other priorities.
This one of the reasons that we need to batter down as many onboarding barriers for newbies as possible for the 6.2 release. There will be ONE opportunity for a first impression with a HUGE audience of local FamilySearch Centers volunteers. If we fall on our faces, we might be able to make a countering splash at the 2027 RootsTech.
To use the FamilySearch Integration, the user will first have to apply for an authentication key on our website. Then, to enable the functionality, they will have to enter the key into the “Integrations” tab in the preferences.
Yes. Gordon asked me to provide a FamilySearch compatible Windows AIO for their certification testing.
Perhaps that FamilyHistory statusbar Icon could be hidden unless the Integrations for FamilySearch has been validated? And only then use the Green / B&W to indicate whether the middleware is actively connecting.
(Speaking of that statusbar icon, those 16x16 FS-BLA-16 and FS-G-16 are so tiny that it is hard to de-cypher. At first I thought it was was a screen noise from a video corruption. Perhaps a 22x22? )
And the Hide LDS tab in person and family editors checkbox Preferences item should probably be moved from the Data tab to the FamilySearch Integrations tab and be marked with the icon. 
/ 
I can ask, but we have to adhere to the FamilySearch Solutions Program Brand Guide. Their logos and artwork are only available in certain sizes. The choice is 16x16 or 32x32 in this case.
The LDS tab is also available to users who don’t use the FamilySearch Integration.
True. But it makes more sense with the FamilySearch subsection of the Integration than where it is now. When looking for LDS related features, users will naturally expect them to be located adjacently.
I don’t have a strong opinion about this. I’m happy for @SourceAirbender to decide.
It would be greatly appreciated by those of us with worsening eyesight.
Even the 2px delta of the larger 24x24 Navigator sidebar to the 22x22 causes undue difficulty for discriminating between Geography view modes. You won’t be able to squeeze a 24x24 into the statusbar if it is every made less fat. But a 22x22 should work. And an even Larger size for the wiki (or when people output the PDF to hardcopy) is a necessity.
I think there should be a check box for FamilySearch Integration Enabled at the top of the Integration tab with the default True. If a user does not want the integration access, they should not have the status bar icon nor the login menu item.
The hide LDS tab option should remain as is. Its function is not dependent on integration.
I think there should be a check box for FamilySearch Integration Enabled at the top of the Integration tab with the default True. If a user does not want the integration access, they should not have the status bar icon nor the login menu item.
Thought this was a good idea, just finished implementing it.
I still have no way to beta test the new feature.
We have a meeting with Gordon tomorrow morning. Hopefully we will be able to open the FamilySearch Integration up for wider beta testing very shortly.
