https://github.com/snaipe/sweet

A sway-to-i3 IPC compatibility layer
https://github.com/snaipe/sweet

compatibility i3 i3wm ipc sway swaywm wayland

Last synced: 21 days ago
JSON representation

A sway-to-i3 IPC compatibility layer

• Host: GitHub
• URL: https://github.com/snaipe/sweet
• Owner: Snaipe
• License: gpl-3.0
• Created: 2018-10-23T22:00:02.000Z (about 6 years ago)
• Default Branch: master
• Last Pushed: 2018-10-23T23:04:50.000Z (about 6 years ago)
• Last Synced: 2024-10-31T11:45:07.275Z (2 months ago)
• Topics: compatibility, i3, i3wm, ipc, sway, swaywm, wayland
• Language: Go
• Size: 15.6 KB
• Stars: 2
• Watchers: 3
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Sweet

A [sway][sway]-to-[i3][i3] IPC compatibility layer.

```

go get -u snai.pe/sweet

```

# Why

Sway provides a value for I3SOCK, but the json output it sends can vary

slightly from stock i3. This sometimes break programs consuming this API,

because they expect some fields to be always present, even if they don't

quite make sense in a pure wayland sense.

Sweet solves this problem by creating an IPC socket at $SWAYSOCK.i3, which

tries to mimic as much as it can i3's output.

# Usage

The simplest way to set up sweet is to add to your sway config:

```

exec sweet

```

and then set `I3SOCK="$SWAYSOCK.i3"` in your environment.

# Changes

* The class and the instance of a wayland window will always be the app ID of the view.

* The `app_id` field is removed from view objects

* View objects of wayland windows provide the `window_properties` map.

[sway]: https://swaywm.org/

[i3]: https://i3wm.org/