-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Remaining work to get 'Background Wait Indicator' sufficient for most of Roslyn, and ready for Platform adoption. #61416
Comments
@ryzngard @vatsalyaagrawal @mikadumont For visibility. I recommend front loading the design portion of this in the end of 17.3, and then doing the impl side of it in 17.4. |
This is going to be nearly impossible for us to complete. The TWD is implemented as a separate process which then shows over the main VS window (so it has its own rendering loop). We can safely defer this to the editor. |
That's why it's in teh bucket of:
|
Dump of FAR as of today in main, will make buckets for work on each of these
|
Things We Can Port With Current Design
Things We Need A "Context Free" Background UI
|
Signature change: #62135 |
You mean 'chang sig' right? Not 'sig help'? |
So far, our experience with the new background work indicator (BWI) has been positive. The API is a near drop in for the existing threaded-wait-dialog (TWD) API and allows a much more lightweight, non-blocking, in-situ UI for letting the user know what's going on.
@ryzngard and I have been talking about what remains to make this a sufficient system for the 90% case for Roslyn, as well as being capable and proven out enough to then move to 'platform' as a general VS facility.
The remaining items are as follows:
Related issues:
The text was updated successfully, but these errors were encountered: