Skip to content

Conversation

@andydotxyz
Copy link
Member

@andydotxyz andydotxyz commented Nov 4, 2025

Begin with linux as it's just metadata :)

Testing with an app of mine, adding The following to FyneApp.toml:

[OpenWith]
MimeTypes = "inode/directory"

@andydotxyz andydotxyz requested a review from sdassow November 6, 2025 16:44
@sdassow
Copy link
Contributor

sdassow commented Nov 7, 2025

Trying to fully grasp this without additional documentation was a bit of guesswork for me until I found https://specifications.freedesktop.org/desktop-entry/latest/mime-types.html - should we maybe reference it somehow?

@andydotxyz
Copy link
Member Author

Trying to fully grasp this without additional documentation was a bit of guesswork for me until I found https://specifications.freedesktop.org/desktop-entry/latest/mime-types.html - should we maybe reference it somehow?

Hmm, well - mime type is a universal thing and I don't want to link this to a system specific doc.
Next is the macOS support where we will look up the internal identifiers based on mime and hook appropriate code in.

A documentation page will be needed - but what is the intent of linking it back to the specifics of desktop entries?

@sdassow
Copy link
Contributor

sdassow commented Nov 9, 2025

A documentation page will be needed - but what is the intent of linking it back to the specifics of desktop entries?

Not necessary, it was just for general clarity, because the big picture wasn't immediately obvious.
That of course will be different if there's a documentation page, so all good.

@andydotxyz andydotxyz merged commit 16b2a70 into fyne-io:main Nov 10, 2025
7 checks passed
@andydotxyz andydotxyz deleted the feature/openwith branch November 10, 2025 11:46
Development map[string]string `toml:",omitempty"`
Release map[string]string `toml:",omitempty"`
Source *AppSource `toml:",omitempty"`
OpenWith *OpenWith `toml:",omitempty"`

Choose a reason for hiding this comment

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

I am late on review but shouldn't the naming on this be more like CanOpen *ContentTypes? "OpenWith" sounds more like the OS side of the equation, where the user is choosing which app it wants to associate with a given file type. This is advertising to the OS what types you can open.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks Drew, that is a great point. I will refactor on the landed code.

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.

3 participants