![]() ![]() We’re calling these the new “Tinted” themes, and you can take a look at these below. One of the benefits of streamlining the color service is that we can provide a fresher set of color themes beyond the basic “Dark” and “Light”. We’re working on both issues, so stay tuned and we’ll update as we make progress. ![]() We’re also aware that 3 rd party themes may run into similar complications, so those may not work as expected with the UI Refresh yet. Our current blue theme has some compatibility issues that we couldn’t iron out in time for Ignite, and instead of delaying this preview, we’ve had to make the decision to make it unavailable for now. This is leading to more consistency, and we believe will result in the cohesive experience that will make Visual Studio more comfortable to use. The new refreshed styles use only about one hundred tokens, which may still seem like a lot, but are much easier to maintain and will make it easier to spot incorrect use. This frequently led to inconsistent experiences, accessibility issues and many other issues that led to an experience that didn’t feel cohesive. Styles across Visual Studio before the UI Refresh used over 4,000 color tokens which were difficult to maintain and were easily misused. For the Visual Studio UI Refresh, this has been most evident in the simplification of the colors that we use in Visual Studio. One of the pillars of the Fluent UI design language is around cohesiveness. Our journey isn’t done yet your feedback is absolutely critical! At this time, we don’t have a timeline for when this will be the primary UX for Visual Studio, which is why we’re spending so much time working with our users to get as much information as we possibly can. Now, this experience is ready for you to try so we can continue to build on your feedback. We’ve found that we can meet the ideals of the Fluent design language while still prioritizing the things that our developers say are the most important. As an example of this, the first screenshots we shared, showed a reduction of nearly a full line of code in the editor space, but the editor in 17.9 preview 1 is only reduced by a quarter of a line.Ĭomparison of the Editor in the various iterations of the UI Refresh This means a more inclusive experience to help everyone be more productive and comfortable while still maximizing code space and respecting the feedback you’ve shared with us. In this version of the UI Refresh, you’ll get to experience a balance of the feedback we received with the accessibility requirements around things like clickable target space and reduction of visual clutter. However, since we revealed the images in our first post, we got a lot of feedback about the things that our developers found important. ![]() Our main goals are still based around the Fluent design language and focus on three pillars: cohesiveness, accessibility, and productivity. The fundamentals of the new experience haven’t changed. Once that box is checked, you’ll need to restart Visual Studio for the UI Refresh to be enabled. Then, look for “Experimental control styles”. To enable the UI Refresh, first go to Tools > Manage Preview Features from the main menu in Visual Studio. Now, here at Ignite, we’re excited to finally make a version of the UI Refresh available for folks to try for themselves. We’ve been spending the time since then working through all your comments to ensure your valuable feedback gets weaved into the UI Refresh. The feedback we’ve collected from that first post and the developer community ticket has been wonderful. We’ve been working on a refresh for the Visual Studio UI to improve productivity, create a more inclusive environment, and keep up with evolving global accessibility requirements. Back in May, we showed a first look into the UI Refresh that we’ve been working on for Visual Studio. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |