Add logos to packages

[SlimRG]

Today I develop my program WingetGUI
So... I'd like to show logos of apps.
In my opinion, it will be a good idea to have URL on logo of package
New windows terminal also support images in title, so you can use this logo in installation progress too.
What do you think about it?

[rbarbrow]

how would you show a logo via a command-line interface?

[SlimRG]

Something like that?

[jantari]

how would you show a logo via a command-line interface?

It would just be ignored by the command-line winget. I think it's a good idea to have an OPTIONAL logo url in the manifest for GUI wrappers to consume.

[SlimRG]

Yes, of course
Logo URL should be only OPTIONAL parameter of manifest

[khaffner]

I had the same idea, but did not find this issue before i posted here: microsoft/winget-pkgs#22577

I support this 👍

[drewid]

Definitely should be supported as the repo could/should definitely be resourced other than command line to be more useful and holistic.

[drewid]

Should be a simple manifest addition

[khaffner]

Should be a simple manifest addition

Yes, I see two options:

1. Encode the image in base64. Takes huge amount of space, but the maintainers have full control over the content of the image. Inelegant.
2. A link to an image. This opens up to third parties modifying the image to something awful without winget knowing, except if we also have a field in the manifest for the hash of the image. The same way installer files are secured in the manifest. GUI implementations can then get the image, verify hash, and only show image if hashes match.

[denelon]

We're tracking this work in:

• Add support for icons via COM APIs #3026

The schema support has been added to the 1.5 schema. The WinGet community repository will not accept manifests with the icon fields included (by policy), but we will be fetching them during validation, and exposing them via the COM API so other GUI based solutions can display them. Once the back-end work is completed, all 1.5 manifests will be used as the signal to capture the icon and make it available via a URL, and the SHA256 for the image and the image type will be automatically included in the manifests served by WinGet even though this metadata will not be in the winget-pkgs repository.

Note: The Dev Home experience will provide an example of how to implement this once it's all wired up.

winget-cli/schemas/JSON/manifests/v1.5.0/manifest.defaultLocale.1.5.0.json

Lines 54 to 112 in 83cd0dc

	"Icon": {
	"type": "object",
	"properties": {
	"IconUrl": {
	"$ref": "#/definitions/Url",
	"description": "The url of the hosted icon file"
	},
	"IconFileType": {
	"type": "string",
	"enum": [
	"png",
	"jpeg",
	"ico"
	],
	"description": "The icon file type"
	},
	"IconResolution": {
	"type": [ "string", "null" ],
	"enum": [
	"custom",
	"16x16",
	"20x20",
	"24x24",
	"30x30",
	"32x32",
	"36x36",
	"40x40",
	"48x48",
	"60x60",
	"64x64",
	"72x72",
	"80x80",
	"96x96",
	"256x256"
	],
	"description": "Optional icon resolution"
	},
	"IconTheme": {
	"type": [ "string", "null" ],
	"enum": [
	"default",
	"light",
	"dark",
	"highContrast"
	],
	"description": "Optional icon theme"
	},
	"IconSha256": {
	"type": [ "string", "null" ],
	"pattern": "^[A-Fa-f0-9]{64}$",
	"description": "Optional Sha256 of the icon file"
	}
	},
	"required": [
	"IconUrl",
	"IconFileType"
	]
	}
	},