Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add support for devicefamily qualifier #2215

Open
3 of 7 tasks
MartinZikmund opened this issue Nov 28, 2019 · 4 comments
Open
3 of 7 tasks

Add support for devicefamily qualifier #2215

MartinZikmund opened this issue Nov 28, 2019 · 4 comments
Labels
difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI kind/enhancement New feature or request platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform platform/ios 🍎 Categorizes an issue or PR as relevant to the iOS platform platform/wasm 🌐 Categorizes an issue or PR as relevant to the WebAssembly platform project/resources 🈷️ Categorizes an issue or PR as relevant to resources and localization (Resources, Assets,...)

Comments

@MartinZikmund
Copy link
Member

MartinZikmund commented Nov 28, 2019 •
edited
Loading

What would you like to be added:

Add support for devicefamily qualifier as listed in Docs.

Why is this needed:

To tailor resources to a specific device type, or have separate XAML layout for specific devices.

For which Platform:

  • iOS
  • Android
  • WebAssembly
  • WebAssembly renderers for Xamarin.Forms
  • Windows
  • Build tasks
  • Solution Templates
@MartinZikmund MartinZikmund added kind/enhancement New feature or request triage/untriaged Indicates an issue requires triaging or verification platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform platform/ios 🍎 Categorizes an issue or PR as relevant to the iOS platform platform/wasm 🌐 Categorizes an issue or PR as relevant to the WebAssembly platform and removed triage/untriaged Indicates an issue requires triaging or verification labels Nov 28, 2019
@pdecostervgls
Copy link

Possibly linked to: #2197
Are you going to work on this Martin? I am currently attempting it but I could use some guidance.

@MartinZikmund
Copy link
Member Author

@pdecostervgls Awesome! Do you have any issue created for this already? Or can I assign you to this one? I will be happy to help ;-) !

@pdecostervgls
Copy link

Im assigned to the issue I linked, but it is only for the theme qualifier. If I am to dive into this we might as well look into the other ones, though I'm unsure which ones are unimplemented already. You can asign me to this issue as well.

@MartinZikmund
Copy link
Member Author

Oh, I am blind 😀 . I will keep this one open to track potential other ones and will hop to the other issue to assist.

@agneszitte agneszitte added the project/resources 🈷️ Categorizes an issue or PR as relevant to resources and localization (Resources, Assets,...) label Sep 21, 2020
@jeromelaban jeromelaban added the difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. label Feb 15, 2021
@MartinZikmund MartinZikmund added area/eu difficulty/challenging 🤯 Categorizes an issue for which the difficulty level is reachable with internals understanding epic and removed difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels Jun 1, 2021
@MartinZikmund MartinZikmund changed the title Add support for more default resource qualifiers Add support for devicefamily qualifier Jun 1, 2021
@MartinZikmund MartinZikmund added difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI and removed difficulty/challenging 🤯 Categorizes an issue for which the difficulty level is reachable with internals understanding epic labels Jun 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI kind/enhancement New feature or request platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform platform/ios 🍎 Categorizes an issue or PR as relevant to the iOS platform platform/wasm 🌐 Categorizes an issue or PR as relevant to the WebAssembly platform project/resources 🈷️ Categorizes an issue or PR as relevant to resources and localization (Resources, Assets,...)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@MartinZikmund @jeromelaban @agneszitte @pdecostervgls