-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
New icons for UI elements #6867
Comments
|
Terminal icon maybe? |
I'm thinking something more wirefeame and line-art like the ones in Segoe. I don't want to genericize our brand! |
Fluent Icons should be the grounding - rather than Segoe MDL2 Icons |
As far as I have seen, Fluent icons are not used in subtle pictographic representations for settings UIs and other ephemeral UI. Monochrome icons are still the framework default inside applications. |
I think I was not clear enough - There are the Fluent brand/app logo icons, but there seems to be a "replacement" for the MDL2 Icons... Fluent UI Icons, as can be seen in the Repo https://github.com/microsoft/fluentui-system-icons and as mentioned in this Medium post https://medium.com/microsoft-design/developing-an-open-source-icon-system-at-microsoft-b1796315df9f |
I see, I misunderstood. Sorry, and thanks! |
@carlos-zamora Edge (Dev channel) has new Fluent icons: |
I think we should also replace these icons: with these Suggestions? @cinnamon-msft @carlos-zamora @DHowett @mdtauk |
When icons are made available for general use in Windows that comply with the modern design guidelines, we will use them. Until then, we will not. |
Newer versions of Windows are now using Segoe Fluent Icons |
@PankajBhojwani This was the thread for "add more action icons", but apparently I didn't leave notes. The best I could find was: 40bdbad |
Description of the new feature/enhancement
We need some new iconography for some of our UI elements, specifically the command palette and settings UI. Below are the requested icons:
Proposed technical implementation details (optional)
The text was updated successfully, but these errors were encountered: