-
Notifications
You must be signed in to change notification settings - Fork 10
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
Include the icon and splash screen configuration in the generated .csproj #662
Comments
This is by design |
I understand, but it makes it much harder to customize, especially as users will have to customize it in 99% of cases (if they use their own .svg) |
At least the required syntax to customize should be included in a README file that would be generated next to the icon svg and splash_screen svg |
As discussed. This isn't a change we really want to make to the templates because the starting point should be by design as simplistic as possible. To address the issues of knowing how to configure the Icon / SplashScreen we already have some intellisense support with the Uno.Sdk and are looking at ways we can expand this. Additionally we need to do a review of the docs for the Uno.Sdk and Uno.Resizetizer to ensure that there is proper back linking between relevant docs and ensure that it remains easy for people to see how they can either customize these items with the properties provided by the Uno.Sdk or take manual control with the available metadata for each item that is used by Resizetizer. cc: @agneszitte |
cc @jeromelaban for info as well |
Will be tracked with |
Will be tracked with |
@MartinZikmund, @dansiegel closing this issue as the work will be tracked with:
|
What would you like to be added:
Currently resizetizer "magically" picks up the icon, icon_foreground and splash_screen files somehow and the user will have no idea how that happens and how to customize it (which will almost always be needed as the padding size for example will almost always need adjusting.
Why is this needed:
Usability.
The text was updated successfully, but these errors were encountered: