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

Added placeholder support for tile loading #1849

Closed
wants to merge 5 commits into from

Conversation

ReinisSprogis
Copy link
Contributor

Summary:
This update introduces customizable loading placeholders for the Tile widget, offering both a default grid and the option to use a custom widget as a placeholder. The feature is controlled by the showPlaceholder boolean parameter within TileLayer. When showPlaceholder is true, developers can either rely on the default grid or specify their own widget to be displayed during tile loading. This addition significantly improves the app's visual feedback during slow loading times.

Key Changes:

showPlaceholder Parameter: Determines whether any placeholder is shown during tile loading. A false value results in no placeholder, maintaining a clean but potentially empty tile space during load.
Custom Placeholder Widget: When showPlaceholder is true, and a custom widget is provided via the placeholder parameter, this widget will be displayed as the loading indicator. This allows for unique, app-specific loading visuals.
Default Grid Placeholder: In the absence of a custom widget (with showPlaceholder set to true), a default grid serves as the loading indicator, enhancing the user's awareness of the loading process without overwhelming the visual experience.

Benefits:
Improved User Experience: Offers immediate visual feedback during tile loading, enhancing the perception of responsiveness, especially in low bandwidth scenarios.
Flexibility and Customization: Developers can customize tile loading experience with custom placeholders.

@ReinisSprogis
Copy link
Contributor Author

#1853 would make this invalid. Need to make changes if #1853 ended up approved.

@JaffaKetchup JaffaKetchup marked this pull request as draft March 13, 2024 21:37
@JaffaKetchup
Copy link
Member

Closing this PR, as it looks as though we're going to progress with #1853.

@ReinisSprogis ReinisSprogis deleted the placeholder branch July 13, 2024 06:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants