Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Splash Screen #65

Closed
stdavis opened this issue Aug 3, 2022 · 2 comments · Fixed by #82, #83, #84, #85 or #86
Closed

Splash Screen #65

stdavis opened this issue Aug 3, 2022 · 2 comments · Fixed by #82, #83, #84, #85 or #86
Assignees
Labels
enhancement New feature or request

Comments

@stdavis
Copy link
Member

stdavis commented Aug 3, 2022

We would also like to add a simple splash screen to the map similar to Web AppBuilder's Splash widget. Ideally, the splash screen would take HTML input that we could create in the config file. It would be nice if there was an option in the config file to enable or disable the splash screen. It might also be nice to have a "Don't Show This Again" checkbox for users to dismiss the splash screen for future sessions. The use case: when we disable commenting on this map, the splash screen would inform users that commenting is no longer permitted on the map. It could also serve the purpose of a simple info panel (issue #43).

@stdavis stdavis added the enhancement New feature or request label Aug 3, 2022
@stdavis stdavis self-assigned this Aug 19, 2022
@stdavis
Copy link
Member Author

stdavis commented Aug 19, 2022

Another thought: As currently implemented, once the user checks the "Don't Show This Again" option, then the splash screen will never be shown to that user again unless they manually clear their browser's localStorage or maybe after a major browser upgrade or something.

We could make it so that this is specific to the version of the application. So each time the app version number changes, the user would have to dismiss it again.

stdavis added a commit that referenced this issue Aug 19, 2022
If the `splashScreen.content` prop becomes unwieldy, we can move it to a separate config file.

Closes #65
stdavis added a commit that referenced this issue Aug 24, 2022
If the `splashScreen.content` prop becomes unwieldy, we can move it to a separate config file.

Closes #65
@msilski
Copy link
Contributor

msilski commented Sep 7, 2022

I tested out the splashScreen.enabled property and I'm not sure it is working. I've set it to false, set it to null, and removed the property from the config and the splashScreen stays enabled. Could you take a look at it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment