Announcement

Collapse
No announcement yet.

The Focus Of Wayland's Weston Compositor

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

  • RahulSundaram
    replied
    Originally posted by dee. View Post
    Good thing Wayland isn't developed by the GNOME team then...
    GNOME maintains excellent ABI compatibility for its libraries. Wayland is a library as well and does a similarly good job.

    Leave a comment:


  • plonoma
    replied
    The developers want to make sure that the Wayland API is good enough so that they don't have to break any APIs in the future.
    The issue is around that problems arise, mistakes can be made.
    Taking great care in designing things is a good protection to avoid problems but is not a guarantee things are perfect and will never have to be redesigned.

    @Darxus
    Thank you for resolving the speculation.
    It's very nice to hear some information about the version stuff.

    Leave a comment:


  • Darxus
    replied
    The protocol has versioning stuff so that they can make changes without breaking backward compatibility. A lot of thought seems to have gone into it.

    Calm down with all the speculation.
    Last edited by Darxus; 04-20-2013, 09:54 PM. Reason: spelling

    Leave a comment:


  • dee.
    replied
    Originally posted by nerdopolis View Post
    API compatibility AFAIK is one of the reasons why Wayland development takes a long time. The developers want to make sure that the Wayland API is good enough so that they don't have to break any APIs in the future.

    Of course they can ADD API's, but they want to make sure exiting ones work.

    And for very good reasons. It would be a disaster for leagacy apps if the display server broke it's API every week...
    Good thing Wayland isn't developed by the GNOME team then...

    Leave a comment:


  • nerdopolis
    replied
    Originally posted by plonoma View Post
    You have to be able to improve the API and ABI.
    Sometimes this means changing things.
    A good version system is much easier to get right then a whole ABI, API of Wayland and Weston.

    Promising too much compatibility is very bad for technical reasons.
    API compatibility AFAIK is one of the reasons why Wayland development takes a long time. The developers want to make sure that the Wayland API is good enough so that they don't have to break any APIs in the future.

    Of course they can ADD API's, but they want to make sure exiting ones work.

    And for very good reasons. It would be a disaster for leagacy apps if the display server broke it's API every week...

    Leave a comment:


  • plonoma
    replied
    You have to be able to improve the API and ABI.
    Sometimes this means changing things.
    A good version system is much easier to get right then a whole ABI, API of Wayland and Weston.

    Promising too much compatibility is very bad for technical reasons.

    Leave a comment:


  • TheBlackCat
    replied
    Originally posted by plonoma View Post
    Promising too much binary compatibility would be a dumb rookie mistake.
    Right, because of course no established projects have binary compatibility promises...

    Leave a comment:


  • plonoma
    replied
    Minimization message on phoronix:
    http://www.phoronix.com/scan.php?pag...tem&px=MTMyMjQ

    Some interesting comments about it:
    http://phoronix.com/forums/showthrea...176#post318176
    Last edited by plonoma; 04-20-2013, 11:21 AM.

    Leave a comment:


  • plonoma
    replied
    Originally posted by Ericg View Post
    ... but people forget that Wayland promises binary compatibility from 1.0 up until 2.0 (and maybe even beyond 2.0 ...) ...
    Promising too much binary compatibility would be a dumb rookie mistake.
    People are fallible there for making a system where everything has to be correct the first time or we are stuck forever with things is of course obviously very, extremely questionable.

    Leave a comment:


  • Nuc!eoN
    replied
    Originally posted by Ericg View Post
    I got it to succeed on an intel graphics laptop 2months ago or so via weston-launch. Maybe something has broken aince then? what's the arch wiki say for wayland?
    I tried with v1.1. It happens on my Laptop and PC, both are radeon cards. The Arch wiki isn't very informative for now. On Wayland irc they say it's a bug that happened to many users.
    Would you retry with the latest release? Shouldn't be much hassle :P

    Leave a comment:

Working...
X