-
Notifications
You must be signed in to change notification settings - Fork 93
Description
Background:
Currently, the MSIX package does not allow an option for creating an .msix package with existing user-provided assets—instead, it either:
- Generates the required assets using the logo at the
logo_path, if that argument is provided, or... - Copies default "Flutter Icon" assets instead
This isn't tremendously helpful, because:
- A package with 'default flutter icon assets', while functional, is, of course, not suitable for production distribution, and...
- The existing icon generation logic, while appreciated, is quite rudimentary and does not produce high quality results for some use cases, such as my own.
Proposal:
Allow users to decline asset generation and provide custom assets (i.e. pre-rendered PNGs) instead.
Example use case:
This is my app icon:
If I pass this to the msix create command via the logo_path parameter, the generated assets (as viewed by extracting the resultant .msix package) look like this:
Which isn't quite acceptable to me—I want specific padding, rounded corners that are aligned with Microsoft's guidelines, and for the whitespace in non-square assets to be filled in.
So, using a script I created, I prepared the assets to my specifications:
But without the needed modifications to the msix tool, there's no way to automatically include these custom assets in my app's .msix package.
