Announcement

Collapse
No announcement yet.

Wayland & Weston 1.2.1 Released

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • phoronix
    started a topic Wayland & Weston 1.2.1 Released

    Wayland & Weston 1.2.1 Released

    Phoronix: Wayland & Weston 1.2.1 Released

    Kristian H?gsberg has put out the first point release to Wayland 1.2 and its adjoining Weston reference compositor. While mostly about bug-fixes, there's also some original new work found in Wayland/Weston 1.2.1...

    http://www.phoronix.com/vr.php?view=MTQ0Mjg

  • mrugiero
    replied
    Originally posted by mark45 View Post
    Khristian said the documentation was also improved, but last modified says 04 April 2013:
    http://wayland.freedesktop.org/docs/pdf/

    Where do I get the new documentation?
    The PDF is not updated, but the html probably is (it's anyway more up to date than the PDF, I tried to read both a few months ago and the HTML was far more complete, IIRC).

    Leave a comment:


  • mark45
    replied
    Khristian said the documentation was also improved, but last modified says 04 April 2013:
    http://wayland.freedesktop.org/docs/pdf/

    Where do I get the new documentation?

    Leave a comment:


  • TheBlackCat
    replied
    Originally posted by mrugiero View Post
    LXDE is supposed to be lightweight, while KWin is supposed to be full-featured. I don't think that's compatible.
    On porting, it still means a port is needed, not only to the toolkit, but on the X specifics.
    The kwin core is pretty lightweight and getting much lighter. There are a lot of add-ons and effects that make the version used in KDE workspaces heavier.

    The primary goal of frameworks 5 in general is to modularize the libraries like kwin so it is easier for developers in other projects to just use what they want. A huge amount of developer work has gone into doing this for kwin under frameworks 5.

    Leave a comment:


  • mrugiero
    replied
    Originally posted by gufide View Post
    Kwin with Xrender has became quite lightweight! You would be very suprised of what the last updates brought to the KDE's window manager
    Becoming more lightweight by accident doesn't count, IMO; also, Xrender will not be available on Wayland. The point is where the focus is. KWin tries to provide the most useful features (even if they can do so with a relative lightweight approach), while LXDE, as a lightweight DE, tries to provide a minimalistic approach. This is not something against KWin, but I think the user bases aren't compatible. If you use KWin, you probably want a full featured desktop, like KDE is.

    Leave a comment:


  • gufide
    replied
    Originally posted by mrugiero View Post
    LXDE is supposed to be lightweight, while KWin is supposed to be full-featured. I don't think that's compatible.
    On porting, it still means a port is needed, not only to the toolkit, but on the X specifics.
    Kwin with Xrender has became quite lightweight! You would be very suprised of what the last updates brought to the KDE's window manager

    Leave a comment:


  • mrugiero
    replied
    Originally posted by TheBlackCat View Post
    Not exactly true although not exactly false, either. I don't know about GTK, but Qt 5 provides Wayland compositor classes that make it much easier for DE's to write Wayland compositors. So although porting to Qt 5 will not give automatic support, it will make the porting much easier.

    That is assuming LXDE doesn't switch to using Kwin. The modularization of frameworks 5 should make this possible, but who knows whether the LXDE camp has any interest.
    LXDE is supposed to be lightweight, while KWin is supposed to be full-featured. I don't think that's compatible.
    On porting, it still means a port is needed, not only to the toolkit, but on the X specifics.

    Leave a comment:


  • gufide
    replied
    Originally posted by 89c51 View Post
    After the whole drama with scott moreau i don't remember anyone implementing the stuff he was trying to add to the protocol and were needed for full DEs. Some E devs were doing stuff but i am not sure about the status of this.
    The point is minimization does not need to be implemented in the protocol, because minimization can be handle by so many ways. The implementation is done by the compositor. Example, on kde you can choose the way kwin will minimize windows. With a minimization inside the protocol, that would not be possible, unless you bypass everything like we do on Xorg.

    The client can tell the compositor to minimize itself but nothing is handled on weston.

    Leave a comment:


  • 89c51
    replied
    After the whole drama with scott moreau i don't remember anyone implementing the stuff he was trying to add to the protocol and were needed for full DEs. Some E devs were doing stuff but i am not sure about the status of this.

    Leave a comment:


  • gufide
    replied
    Originally posted by jrch2k8 View Post
    minimize is not part of the protocol and never was, Weston a wayland demo client don't minimize because weston devs have figure out wich of the 300 method for minimize will be more efficient, is just that. beside weston is a toy demo so they dont focus too much on it beyond test code

    Kwin/Clutter/etc all minimize just fine
    oh thanks! That was I tought but I wasn't sure

    Leave a comment:

Working...
X