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
AppStream Button #24
Comments
|
Mandating or recommending it in the spec IMHO doesn't make sense, as things like that don't belong there. |
Why not? I mean, it's not about mandating, because it's not about enforcing but facilitating. If it's not easy, it won't be used at all. A good way to facilitate is by having the Appstream project actively suggest it. |
|
It's not really in-scope as part of the specification of AppStream metadata - but as said, making the project suggest it would make a lot of sense. |
|
When you have a final design, let me know, so I can include it in the docs! |
|
Ping on this one - do we have something ready to ship? |
|
Final design attached; |
|
Added as 0aa623a - thank you :-) |
Some time ago we started discussing about the appstream://id scheme.
Then I discussed with our Visual Design Group that it might be interesting to have a button that we can use to indicate that a button leads to an AppStream URI (from a website, although it might make sense on applications as well).
Here's what @Ken-Vermette came up with, and I think it's an interesting approach:
https://share.kde.org/index.php/s/MPpOOEl7JpGAWzu/download
Do you think it would make sense?
The text was updated successfully, but these errors were encountered: