-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Specify custom desktop file fields in FyneApp.toml #3958
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a great idea!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies these pending comments did not get sent :(
cmd/fyne_demo/FyneApp.toml
Outdated
|
||
[LinuxAndBSD] | ||
GenericName = "Fyne Demo" | ||
Categories = "Development;" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the trailing ";" optional? It doesn't seem natural to have it here.
Also should we use a more common list separator for Go developers and convert it where required for the output?
?Perhaps even making it a toml list instead of string?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if it technically is required but the official documentation uses it.
https://freedesktop.org/wiki/Howto_desktop_files/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A TOML list sounds like a great idea :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if it technically is required but the official documentation uses it.
By using FDo formatting you still require folk to understand the spec - which we should avoid if possible just like how naming avoids it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed but I've switched to TOML lists now so it should no longer be an issue.
|
||
[Development] | ||
HelperText = "This binary was build with debug symbol" | ||
|
||
[Release] | ||
HelperText = "This binary was build without debug symbol" | ||
|
||
[LinuxAndBSD] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we make it "Linux,BSD" or "Linux&BSD" it will be machine parsable if we decide to match go's approach to this logic :).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried that but it does not seem to be supported. I tried +
, ,
, and &
before opening this PR but neither seem to be supported.
Comment = "A demo of Fyne and its capabilities." | ||
Keywords = "demo;fyne;" | ||
Keywords = ["demo", "fyne"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
cmd/fyne_demo/FyneApp.toml
Outdated
HelperText = "This binary was built without debug symbols" | ||
|
||
[LinuxAndBSD] | ||
GenericName = "Fyne Demo" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is generic name, and how often should it differ from the Name specified in the details section above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For Rymdport, I have "File Transfer" as GenericName. Just like Firefox has "Web Browser". I hope that helps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yea thanks. I guess maybe it should be "demo app" or "developer tools" so it's clearer why they are different in this example?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point. I'll get that fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps "Toolkit Demo" even?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great addition thanks
Thanks. This is going to make the release binaries in Geoffrey so much nicer for Rymdport's users :) |
The documentation for custom metadata fields needs to be added to https://docs.fyne.io/started/metadata.html |
Please open an issue for that instead of commenting on a PR that was merged a year ago. |
Description:
This PR adds support for specifying custom metadata fields for Linux and BSD. It is currently hooked up to provide support for adding
GenericName
,Categories
,Comment
, andKeywords
to the desktop files. These fields are the ones that I had to specify manually in io.github.jacalz.rymdport.desktop for Flatpak packaging to be accepted.Checklist: