Skip to content

Conversation

@romanofranz
Copy link

The ThreePaneSceneStrategy displays three panes side-by-side on large screens (width > 1200dp) when the top three back stack entries support it. On medium screens (width > 600dp), it falls back to a TwoPaneScene.

The `ThreePaneSceneStrategy` displays three panes side-by-side on large screens (width > 1200dp) when the top three back stack entries support it. On medium screens (width > 600dp), it falls back to a `TwoPaneScene`.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @romanofranz, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new 'three-pane' layout recipe to the application, enhancing its adaptive UI capabilities. It provides a robust strategy for displaying multiple navigation entries concurrently based on screen real estate, ensuring an optimized user experience across various device sizes. The implementation includes a fallback mechanism to a two-pane layout for intermediate screen widths, improving flexibility and responsiveness.

Highlights

  • New Three-Pane Scene Recipe: A new recipe demonstrating a three-pane layout using the Scenes API has been added, enhancing the application's adaptive UI capabilities.
  • Dynamic Layout Strategy: The ThreePaneSceneStrategy is introduced, which intelligently displays three panes side-by-side on large screens (width > 1200dp) when the top three back stack entries support it.
  • Responsive Fallback Mechanism: For medium screens (width > 600dp), the strategy gracefully falls back to a TwoPaneScene, ensuring an optimized user experience across various device sizes.
  • Metadata-Driven Pane Support: Navigation entries can now declare their support for three-pane display through specific metadata, allowing the SceneStrategy to make informed layout decisions.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new three-pane scene recipe, which is a great addition for large-screen layouts. The implementation is mostly solid, but I've found a critical issue in the ThreePaneSceneStrategy logic that prevents the two-pane fallback from working correctly when the back stack grows. I've also included a few medium-severity suggestions to improve code correctness and documentation formatting. Please take a look at the detailed comments.

The `ThreePaneSceneStrategy` displays three panes side-by-side on large screens (width > 1200dp) when the top three back stack entries support it. On medium screens (width > 600dp), it falls back to a `TwoPaneScene`.
# Conflicts:
#	app/src/main/java/com/example/nav3recipes/scenes/threepane/ThreePaneActivity.kt
#	app/src/main/java/com/example/nav3recipes/scenes/threepane/ThreePaneScene.kt
@dturner
Copy link
Collaborator

dturner commented Dec 3, 2025

What benefit does this recipe provide over the TwoPaneScene recipe?

@romanofranz
Copy link
Author

What benefit does this recipe provide over the TwoPaneScene recipe?

To cover a wider range of devices. Material 3 guidelines suggest up to 3 panes, depending on the window size. Would it be better to update the TwoPaneScene to something like MultiPaneScene instead of creating a new recipe?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants