Looks great! I wonder if we don't open this details sheet by default. Maybe it can be opened during/after installation for more details? We would still show simple progress similar to installing an app from the App Store. What are your thoughts?

Looks great! I wonder if we don't open this details sheet by default. Maybe it can be opened during/after installation for more details? We would still show simple progress similar to installing an app from the App Store. What are your thoughts?

That's a great idea. Then does the 'install' button change to a 'details' button?

Or is it "Install" to a second "Install" button in the details page

@austincondiff thoughts on this UI/UX? I like the implied confirm step after clicking install, and the chance to show a little more information before installing.

In my opinion it is too disruptive. Imagine the use-case. User comes in and thinks, "I use JavaScript, TypeScript, Rust, Python, and Swift."

Option A (the on in your video)

1. Find JavaScript
2. Click Install in row
3. Click Install in sheet
4. Click Continue
5. Find TyoeScript
6. Click Install in row
7. Click Install in sheet
8. Click Continue
9. Find Rust
10. Click Install in row
11. Click Install in sheet
12. Click Continue
13. Find Python
14. Click Install in row
15. Click Install in sheet
16. Click Continue
17. Find Swift
18. Click Install in row
19. Click Install in sheet
20. Click Continue

OR

Option B

1. Find JavaScript
2. Click Install in row
3. Find TypeScript
4. Click Install in row
5. Find Rust
6. Click Install in row
7. Find Python
8. Click Install in row
9. Find Swift
10. Click Install in row

If the user cares to see more details, they can click the circle "i" symbol next to the install button.

Maybe this info icon is there regardless of whether install has started or not. That way users can get more details before installing. Similar to the App Store.

That sounds like a good compromise. Install button initiates install immediately, info button presents the same view but doesn't start installing.

Well wait, to be fair we're still forcing the longer UX because we want to make sure we're not running willy nilly running commands on the user's machine. So no matter what the UX is this for each language.

1. Find Swift
2. Install Swift
3. Wait for install dialogue to complete

Also a heads up, we may want to fork the mason repository in the future or see if they'd be interested in extending it. Right now there's no way to indicate that a package could be found on a user's machine without installing. Swift and Rust are good cases of that, where the language bundles the server executable in the tooling. For that reason Swift isn't in the Mason registry (you can't really install SourceKitLSP without the Swift toolchain)