Migrating to windows-sys

[WanderLanz]

Attempting at move windows-sys for win32 api.

[sigmaSd]

I think you should keep this open, it's a reasonable improvement

[WanderLanz]

I think you should keep this open, it's a reasonable improvement

I've just gotten too busy to keep track of this pr and didn't see anyone saying anything about moving from winapi, besides #662 for compile times, in addition to needing the crossterm-winapi pr in order to make the build work (without breaking changes).

I'll go ahead and reopen it and the crossterm-winapi pr for review, but I might not be responsive.
I've done most of the (albeit easy) work so anyone else is more than welcome to make another pr if this one becomes stale or breaking.

[TimonPost]

Thanks for PR, just haven't gotten to it yet as I'm not sure about the benefits yet. The only reason I can think of is that winapi is not actively maintained, and windows-rs is owned by Microsoft. But winapi works perfectly and we do not have the need to switch really. So kinda low priority-wise to get this in. Especially this change needs to be well tested. Altough

[WanderLanz]

@TimonPost No problem at all. windows-rs is not even technically 1.0 yet and we need to make changes in crossterm-winapi as well, so it's maybe not worth the change just for minimal improvements.

I just figured that it might help in keeping everything up to date with any new API, e.g. ConPTY, allowing the awesome contributors here to provide more features down the road and keep everything working well.

Also, if winapi is unmaintained for the foreseeable future, this issue and others might creep up on us.

Hope everyone's having a good day, remember to take frequent breaks.

[jasiukiewicztymon]

@TimonPost can you review this maybe it would help for #772 issue and resolve this problem.. Thanks!

[WanderLanz]

Hey I've been busy on other things so I can't maintain this to current. It probably won't happen until @TimonPost makes a concerted effort themselves, but it's easy enough for someone to do again within a day.

I'll leave it open just as a reminder that winapi is, at least slowly, becoming deprecated, its last commit was three years ago, and migration to windows-sys is requested, but feel free to close anytime.

• Posture check!

[kirawi]

Thanks for PR, just haven't gotten to it yet as I'm not sure about the benefits yet. The only reason I can think of is that winapi is not actively maintained, and windows-rs is owned by Microsoft. But winapi works perfectly and we do not have the need to switch really. So kinda low priority-wise to get this in. Especially this change needs to be well tested. Altough

I do want to add that it helps out dependents since a lot of newer crates and some older crates use windows instead. So having both winapi and windows in the dependency tree is not ideal.

[TimonPost]

Agreed! If its something the ecosystem works towards we can make this effort. If someone feels like it it can be rebased. Try run the interactive demo in the examples. Mainly testing the features that are essentially different in windows vs unix. resizing, cursor position, events etc...

[WanderLanz]

I found some time, so I went ahead and just forced a rebase here. quick tests seem to pass. ...except resizing, and I don't know why, so if anyone wants to take a shot at it go ahead.

Just to note, async-std has upgraded to windows-sys (via async-io), but no release yet so that will still pull in winapi for now.

crossterm-winapi still needs update