Windows 10: Microsoft is renaming UI Fabric GitHub repo to Fluent UI

Brink · Mar 13, 2020

Whatâs in a name? A lot it turns out. And we have a lot of them. Too many? We hear you and agree. Thatâs one of the key reasons weâre simplifying our story. To collectively rally around a single UI library for our web componentsâFluent UI.

Weâre starting with Fluent, our cross-platform design system. Fluent is the way Microsoft designs and builds digital product experiences, both internally and with our customers and community.

Weâve evolved Microsoft to speak a common language through a shared design system. Fluent UI will directly connect that effort to a broad set of products, through code, specifically the convergence of our most used web engineering frameworks â Fabric and Stardust.

Shortly, weâll rename our UI Fabric GitHub repo to reflect our future Fluent UI vision. This is step one toward our vision for a more simplified developer ecosystem.
This is step one toward our vision for a more simplified developer ecosystem.
This is what we mean when we say Fluent is Microsoftâs design-to-code system. Weâre bringing design and engineering together more than ever, to contribute to and leverage a shared foundation, and reach our shared goals. Weâre not suggesting that one size fits all, and we got here honestly, so we must evolve collectively.

Our goal is simpleâa shared foundation with open source engineering processes to create experience coherence, efficiency, and effectiveness. It enables us to do more with less.

Whatâs changing

Simply put, weâre merging two Microsoft repositories: UI Fabric and Stardust GitHub repos will live under the Microsoft GitHub organization as Fluent UI.
This allows our teams to collectively work together on a shared code base with a shared set of build and development tools to support our products and community more efficiently. It also allows us to get to a single UI library for Microsoft 365.

What this means for developers

Today? Weâre working with a goal of avoiding disruption or breaks in the UI Fabric developer experience. You will continue getting a stream of patches and minor releases as we iterate the current major release (version 7).

As we finalize our rename efforts, expect to see more regular updates and communication around our major releases. Our next major release will be the first batch of major changes in uniting our collective efforts, tentatively targeting summer 2020.

Our intent is to minimize the amount of interruptions to in flight developer workflows. Also, we want to be mindful and incremental in our approach and weâre using this opportunity to signal to the community our incoming changes.
Weâre working with a goal of avoiding disruption or breaks in the UI Fabric developer experience. You will continue getting a stream of patches and minor releases as we iterate the current major release (version 7).
The following is a short FAQ on the potential impact of the repo merge and rename effort:

Do I need to rename all my package imports to something new?
No. Package names will stay the same as a result of the merge and rename effort. Weâll continue releasing all UI Fabric packages as we do today. Weâll also alias publish the same packages under a new name, so that at any time you can use the new @fluentui/react package with no breaking changes.

Do I need to re-clone the repo?
No. You shouldnât need to re-clone the repo. Your clones should be redirected correctly.

Where do I file GitHub issues and pull requests now?
After the rename, you can file issues and pull requests in the new microsoft/fluentui repository. Our teams will collectively support them there.

What about the issues and pull requests that were opened before the merge?
Previous issues and pull requests will be captured in a microsoft/fluentui repository. For UI Fabric, contribution history and active pull requests will stay intact.

Is the current version of UI Fabric still supported?
Yes. Nothing is changing in our level of support to the community for the library.

What if I have more questions about the repo merge and rename?
Reach out to our team on the UI Fabric GitHub. File an issue and we will be happy to follow up with you to help where we can.

What does this mean for WinUI and the Fluent Design System within Windows?
The Fluent Design System lies at the core of our recommendations for how to build engaging user experiences on Windows and across platforms now, too. WinUI continues to embody the Fluent Design System as the native user experience platform of Windows. With the addition of the Javascript-based Fluent UI libraries, youâll also be able to build more coherent experiences across other platforms and the web, too, and the Fluent Design System will continue to expand.

New updates planned for Fluent UI

Our next major releases will focused on performance and theming:

Improve runtime performance through styling optimizations. Weâre evaluating how we can reduce css-in-js style calculation overhead to improve rendering performance.

Improve flexibility and composition of components. Leverage React hooks and function components, along side API surface improvements, to give developers more composition options.

Provide a more flexible, powerful theming system. Extend our list of design tokens and improve our theming tooling to apply your design.

Eliminate deprecated React API usage. This enables partners to test React concurrent mode rendering, which allows rendering to be interruptible reducing how much the UI thread is blocked during large updates.

Still have questions?

Feel free to reach out to our team with any questions you may have regarding our new collective effort around Fluent UI by filing an issue on the existing UI Fabric GitHub repository.

The Fluent UI team

Click to expand...

Source: https://developer.microsoft.com/en-u...nto-fluent-ui/

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

:)

dineshmaripi · Mar 13, 2020

Windows 10 UI and Issues

Why Microsoft is not adding fluent design system to its dialog boxes and context menu. It looks weird some parts of windows adapted fluent design but still in many places fluent design is not present. I want
Microsoft to ditch its ugly Ribbon UI in file explorer and office suite apps and bring new icons to replace those legacy icons that looks terrible as hell. Even the Action center needs some refinement. I wish Microsoft would bring rounded icons instead of
tiles in Action center and It will be nice if they make font-weight: bold by default in their windows UI.

Brink · Mar 13, 2020

Introducing WinAppDriver UI Recorder

A new open-sourced tool is now available for the Windows Application Driver (WinAppDriver) community: the WinAppDriver UI Recorder tool. This tool will enable users to easily create automated UI tests.

For those of you not familiar with WinAppDriver, it is a UI automation service for Windows 10 that users can use to test their applications. We recently released our v1.1 preview that you can read more about here.

What is UI Recorder

For many in the WinAppDriver community, Inspect has been the most common tool for users to select UI elements and view their attribute data. Though Inspect serves its intended purpose of viewing accessibility data, it falls behind when it comes to supporting scenarios specifically for UI automation, such as being able to generate XPath queries.

For situations such as these, the WinAppDriver UI Recorder tool hopes to fill in the gaps from Inspect and serve as its alternative.

As for its initial release, the UI Recorder tool will enable the following two key scenarios:

1) Inspecting UI elements and retrieving their XPath expressions

2) Generating C# code for certain actions (mouse click) when “Record” is active

Generated Code can be pasted into the UI Recorder Template folder for WinAppDriver playback

We’re hoping that with this tool, users will have a simpler and more intuitive approach in writing automation scripts for WinAppDriver.

Getting Started

The code for the UI Recorder is open-sourced and available on WinAppDriver’s GitHub repo here. It’s recommended to use Visual Studio 2017 to start building and compiling it. Once compiled, you can immediately start using UI Recorder.

In addition to access to the source, a zipped executable can be found here on our GitHub Releases section.

Using UI Recorder

The UI Recorder tool aims to provide an intuitive, and simplistic, user interface that is divided into two panels, as seen below:

UI Recorder tracks both keyboard and mouse interactions against an application interface—representing a UI action. When Recording is active, both the top and bottom panels are dynamically updated with varying UI element information every time a new UI action takes place. The Top Panel shows the generated XPath query of the currently selected UI element, and the Bottom Panel shows the raw XML information for the same element. You can navigate to the C# Code tab on the bottom panel to view generated C# code of the recorded action which you can use on a WinAppDriver test.

The following animation provides an example of the recording process:

The code recorded can be coped over to the clipboard and pasted onto the WinAppDriver UI Recorder template project to be replayed.

Providing Feedback

With the UI Recorder tool being open-source, we highly encourage the community to submit any PRs with changes or enhancements, and to post suggestions on how they would like to see the UI Recorder grow.
Please use the GitHub Issues Board to provide any feedback on the UI Recorder tool – we look forward to hearing about any suggestions, feature requests, or bug reports!

Staying Informed

To stay up to date with WinAppDriver news follow @mrhassanuz.

Summary

A new tool for WinAppDriver is available now: UI Recorder. Now users have an intuitive way automate UI with WinAppDriver by not only being able to generate XPath expressions on the fly, but also C# code from by recording UI action events through mouse clicks.
Click to expand...

Source: Introducing WinAppDriver UI Recorder - Windows Developer Blog

Brink · Mar 13, 2020

Introducing WinAppDriver UI Recorder

A new open-sourced tool is now available for the Windows Application Driver (WinAppDriver) community: the WinAppDriver UI Recorder tool. This tool will enable users to easily create automated UI tests.

For those of you not familiar with WinAppDriver, it is a UI automation service for Windows 10 that users can use to test their applications. We recently released our v1.1 preview that you can read more about here.

What is UI Recorder

For many in the WinAppDriver community, Inspect has been the most common tool for users to select UI elements and view their attribute data. Though Inspect serves its intended purpose of viewing accessibility data, it falls behind when it comes to supporting scenarios specifically for UI automation, such as being able to generate XPath queries.

For situations such as these, the WinAppDriver UI Recorder tool hopes to fill in the gaps from Inspect and serve as its alternative.

As for its initial release, the UI Recorder tool will enable the following two key scenarios:

1) Inspecting UI elements and retrieving their XPath expressions

2) Generating C# code for certain actions (mouse click) when “Record” is active

Generated Code can be pasted into the UI Recorder Template folder for WinAppDriver playback

We’re hoping that with this tool, users will have a simpler and more intuitive approach in writing automation scripts for WinAppDriver.

Getting Started

The code for the UI Recorder is open-sourced and available on WinAppDriver’s GitHub repo here. It’s recommended to use Visual Studio 2017 to start building and compiling it. Once compiled, you can immediately start using UI Recorder.

In addition to access to the source, a zipped executable can be found here on our GitHub Releases section.

Using UI Recorder

The UI Recorder tool aims to provide an intuitive, and simplistic, user interface that is divided into two panels, as seen below:

UI Recorder tracks both keyboard and mouse interactions against an application interface—representing a UI action. When Recording is active, both the top and bottom panels are dynamically updated with varying UI element information every time a new UI action takes place. The Top Panel shows the generated XPath query of the currently selected UI element, and the Bottom Panel shows the raw XML information for the same element. You can navigate to the C# Code tab on the bottom panel to view generated C# code of the recorded action which you can use on a WinAppDriver test.

The following animation provides an example of the recording process:

The code recorded can be coped over to the clipboard and pasted onto the WinAppDriver UI Recorder template project to be replayed.

Providing Feedback

With the UI Recorder tool being open-source, we highly encourage the community to submit any PRs with changes or enhancements, and to post suggestions on how they would like to see the UI Recorder grow.
Please use the GitHub Issues Board to provide any feedback on the UI Recorder tool – we look forward to hearing about any suggestions, feature requests, or bug reports!

Staying Informed

To stay up to date with WinAppDriver news follow @mrhassanuz.

Summary

A new tool for WinAppDriver is available now: UI Recorder. Now users have an intuitive way automate UI with WinAppDriver by not only being able to generate XPath expressions on the fly, but also C# code from by recording UI action events through mouse clicks.
Click to expand...

Source: Introducing WinAppDriver UI Recorder - Windows Developer Blog

Windows 10: Microsoft is renaming UI Fabric GitHub repo to Fluent UI

Microsoft is renaming UI Fabric GitHub repo to Fluent UI

Microsoft is renaming UI Fabric GitHub repo to Fluent UI

Microsoft is renaming UI Fabric GitHub repo to Fluent UI

Microsoft is renaming UI Fabric GitHub repo to Fluent UI - Similar Threads - Microsoft renaming Fabric

Issues with UI scaling on only parts of the UI

Issues with UI scaling on only parts of the UI

Segoe UI Fluent Icons and/or segmdl2 font files are broken/corrupted

Segoe UI Fluent Icons and/or segmdl2 font files are broken/corrupted

How to open Segoe UI Fluent Icons

How to open Segoe UI Fluent Icons

Office UI Fabric Icons as SVG or PNG files.

Is there any way to force turn on "Fluent Design UI" on my PC?

Ui

Users found this page by searching for:

c# service fabric application upgrade fluent