Skip to content
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

Any hope for Hyprland support? #16

Open
Joni-Samanen opened this issue Feb 7, 2024 · 3 comments
Open

Any hope for Hyprland support? #16

Joni-Samanen opened this issue Feb 7, 2024 · 3 comments

Comments

@Joni-Samanen
Copy link

How difficult you think it would be to implement?

@lthms
Copy link
Owner

lthms commented Feb 8, 2024

I’d have to have a look at Hyprland IPC protocol tbh. Do you know how it compares to Sway/i3’s?

@Joni-Samanen
Copy link
Author

Unfortunately I have no idea... I saw a project somewhere on that basically revolved around converting some piece of software from sway to hyprland, and there was a lot of talk about the IPCs but can't remember what it was... I'll try to take a look if I can find it (or anything else that might be useful.

This is such a cool idea btw, I too fell in love with material-shell when I first tried it a couple of years ago, it just makes so much sense and fits perfectly to my workflow.

@Geerayef
Copy link

Hey!

I love the idea of spatial-shell, great work!
Regarding Hyprland IPC: I found an interesting wrapper written in GO for Hyprland's IPC that might contribute to this topic of getting spatial-shell to work with Hyprland: https://pkg.go.dev/github.com/imxyy1soope1/go-hyprland-ipc/hyprctl
There are also wrappers for Hyprland's IPC in Dart and Rust, but I'm not sure how complete they are, this one seemed a bit more comprehensive to me.

Maybe this can help serve as a nice overview to compare with Sway's IPC. From my limited understanding they shouldn't be drastically different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants