cargo tauri icon update

[kandrelczyk]

Hi,

Looks like cargo tauri icon needs a rework/update and I would like to discuss the features that should be added and approach to follow.

From what I understand image generation itself (i.e. generating images in different resolution) works fine and doesn't have to be changed but some of the features we're missing are:

• Android 16 adaptive icons
• different icons for different targets (e.g. some platforms support transparency but other don't)
• tinted icons for iOS and Android.

With all those new features I think just using command line arguments will not work (as in cargo tauri icon --android-file=android.png --android-tinted --ios-file=ios.png... and so on) and we should switch to a configuration file. The simplest way to do it seams to be just adding 'icon' section to tauri.conf.json and using this if present or falling back to current behavior if this section is missing. In this section we would:

1. define a single icon file that would replicate current behavior if it's the only entry present
2. define overrides per platform
3. define additional configuration options per platform

Any reasons not to do it this way? Any alternative ideas?

[Legend-Master]

Since we just generate all icons right now, does it make sense to just add the ones you just mentioned to the list first? If the process is short enough, I think we don't have to use a config for that?

I do think we should probably add some documentation about which icon is used where though

[FabianLars]

Maybe it should be a CLI flag instead but the general idea is good.
Something similar has been in my mind since before tauri supported mobile - having multiple input sizes. Didn't really think about a json config for this but using file naming conventions instead but that will likely get really confusing with what's been talked about here.

[kandrelczyk]

@FabianLars which part should be a CLI flag?

[FabianLars]

Instead of this part

if there's a icons folder with manifest.json inside use it to generate all the icons

I don't think we should hardcore the icons dir (especially since that's currently the output dir but I don't want to focus on the name too much). And we'd still have a manifest file whatever but instead of tauri icon path we'd have tauri icon --source-dir path or tauri icon path --use-manifest (shitty names but you get the idea)

[FabianLars]

Ah wait no, there's really no need for that specific flag, maybe I just misunderstood you and you meant the user provided with with icons so if the user provided path in tauri icon path is a dir and contains that file we can use this logic.

I shouldn't butt in if I'm only on my phone on a work trip in a place that's too hot for me :D

[kandrelczyk]

Ok, sounds great. If we agree about a "dir with manifest" solution the specifics can be changed later. I will start with:

• path is a file -> old logic
• path is a dir -> new logic