Skip to content

Move licenses from window menu to settings screen#477

Merged
florent37 merged 3 commits intoopenflocon:mainfrom
timoloewe:licenses-to-settings-screen
Jan 25, 2026
Merged

Move licenses from window menu to settings screen#477
florent37 merged 3 commits intoopenflocon:mainfrom
timoloewe:licenses-to-settings-screen

Conversation

@timoloewe
Copy link
Copy Markdown
Contributor

Hey everyone! Thanks for this great project!

I'm a Linux user, and on Linux, Flocon's app window is rendered like this:

grafik

I'm not sure how this looks on other platforms (I guess it at least looks different on MacOS), but I don't like how the "Settings -> Licenses" menu is permanently rendered below the window title bar:

  • It permanently uses vertical space for something that you would rarely ever look at.
  • It (subjectively) doesn't look nice and doesn't integrate into the remaining look and feel of the desktop (I'm using Gnome, might be less problematic on Qt-based systems).

I was wondering if you would accept a change that would get rid of the window menu and instead moves the "Licenses" item to the in-app settings screen. That would also get rid of the fact that there are currently two places that are labeled as "Settings" (window menu and in-app).

Here's a screenshot of what my proposal looks like:
grafik

Of course, I'm happy to change visuals or other details according to your feedback. Also, feel free to reject if you prefer to keep the current state.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @timoloewe, 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 refactors the application's license information display by relocating it from the system-level window menu to a more integrated 'About' section within the in-app settings. This change aims to improve the user experience, particularly on Linux where the window menu was visually intrusive, and streamlines the application's overall UI by consolidating settings-related options into a single, consistent location.

Highlights

  • UI/UX Improvement: The 'Licenses' entry has been moved from the application's window menu to a new 'About' section within the in-app settings screen. This change addresses visual clutter and inconsistent UI behavior observed on certain desktop environments, such as Linux.
  • Window Menu Removal: The FloconMenu component, which previously rendered the window menu bar containing the 'Settings -> Licenses' option, has been entirely removed from the desktop application's main entry point.
  • New UI Components and Resources: New string resources (settings_about_title, settings_licenses) have been added, and a dedicated LicensesWindow composable has been implemented to display license information when accessed from the settings screen.
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
Copy Markdown
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 successfully moves the licenses screen access from a window menu item to a button within the settings screen. This is a great improvement for Linux users as it saves vertical space and integrates better with the desktop environment, and it also consolidates settings into one place. The changes are well-implemented, removing the old menu and adding the new UI elements cleanly. I've left one minor suggestion to use a string resource for a hardcoded window title to improve maintainability.

onCloseRequest: () -> Unit
) {
FloconWindow(
title = "Licenses",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

To improve maintainability and support for localization, it's best to use string resources instead of hardcoding text. You've already added a string resource for "Licenses", so it should be used here for the window title.

Suggested change
title = "Licenses",
title = stringResource(Res.string.settings_licenses),

.background(FloconTheme.colorPalette.primary),
)
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

remove line break

@rteyssandier rteyssandier added the enhancement New feature or request label Jan 21, 2026
@florent37
Copy link
Copy Markdown
Contributor

Hi @timoloewe thanks for the feedback, yes I only tried on macos, and never faced this ux bad behavior then
I do agree to move this :)

@florent37 florent37 merged commit b8b17dc into openflocon:main Jan 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants