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.

Sign up for GitHub

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

Jump to bottom

Sway 0.12 #1027

Closed
2 tasks done
ddevault opened this issue Jan 5, 2017 · 6 comments
Closed
2 tasks done

Sway 0.12 #1027

ddevault opened this issue Jan 5, 2017 · 6 comments

Comments

@ddevault
Copy link
Contributor

ddevault commented Jan 5, 2017 •
edited
Loading

List of things I want to ship in 0.12. Anyone's welcome to work on this stuff (or anything else). This list is unordered.

  • Redshift support
  • Implement improved IPC security flags
@ddevault
Copy link
Contributor Author

Executive decision: postponing the following tasks indefinitely:

  • Get surface-layers protocol upstreamed in wayland-protocols (discussion on wayland-devel)
  • Update swaylock, swaybar, swaybg to use surface-layers protocol
  • Implement swayslop based on surface-layers
  • Implement orbital/weston's screenshooter protocol and update swaygrab to use it
  • Discuss permission management protocols with wayland-devel
  • Implement KDE's DPMS protocol and write a DPMS daemon
  • Implement KDE's modesetting protocol and work with KDE to improve arandr-style client interfaces

And these permenantly:

0.12 will be a much smaller release, mostly to ship redshift and bugfixes on a reasonable timeframe. The primary goal of 0.13 will be to replace wlc with our own wayland compositor implementation.

@spagy
Copy link

spagy commented Feb 14, 2017

What's the benefit of switching from wlc to a custom wayland compositor? Is there a discussion about this somewhere?

@ddevault
Copy link
Contributor Author

ddevault commented Feb 14, 2017 •
edited
Loading

No, it's mostly happened on IRC. I'll give the basic rundown here:

Problems with wlc:

  • Performance (CPU, GPU, and power usage)
  • Design complexity
  • Maintenance (@Cloudef doesn't have time to work on it and few others contribute, which is compounded by the over-complex design)

Advantages to switching:

  • We can design our compositor with the hindsight wlc didn't have and avoid many problems
  • Easier to implement surface-layers if we have our own compositor, as well as other protocols we'll need in the future
  • Sway gets far more maintenance attention than wlc

Also, solving some of the problems in wlc that we need solved would necessitate design decisions that would be worse off for both projects.

@ddevault ddevault mentioned this issue Feb 15, 2017
Closed
@Drakulix Drakulix mentioned this issue Feb 15, 2017
Closed
@ddevault
Copy link
Contributor Author

0.12-rc1 has been released, please test it!

@ddevault
Copy link
Contributor Author

0.12-rc2 released, please test it! The following changes were included: 0.12-rc1...0.12-rc2

@ddevault
Copy link
Contributor Author

ddevault commented Mar 7, 2017

sway 0.12 released!

@ddevault ddevault closed this as completed Mar 7, 2017
@JerziKaminsky JerziKaminsky mentioned this issue Apr 14, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ddevault @spagy