Announcement

Collapse
No announcement yet.

Qt 5.1 To Feature Improved Support For Wayland

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

  • nerdopolis
    replied
    Originally posted by nerdopolis View Post
    ONLY kill unresponsive apps?
    The display server that would later be called Weston has supported moving frozen windows since at least 2010!
    http://www.youtube.com/watch?v=Cs9Ly...tailpage#t=67s
    EDIT: Before someone freaks out, The resume issue that appears in that video from 2010 WAS FIXED

    Leave a comment:


  • nerdopolis
    replied
    Originally posted by Awesomeness View Post
    I did research. Wayland will only allow to kill unresponsive apps, not allow to minimize them.

    ONLY kill unresponsive apps?
    The display server that would later be called Weston has supported moving frozen windows since at least 2010!

    Leave a comment:


  • Awesomeness
    replied
    Originally posted by smitty3268 View Post
    Link, or please explain why the simple process above won't work.
    I thought you were all so omniscient and yet do do not know that?
    Check the Wayland video from the last Xorg conference, you genius! Michael recorded the entire conference and the videos were heavily featured and yet you missed that?

    Leave a comment:


  • liam
    replied
    Originally posted by curaga View Post
    Yup, one of the worst techniques to do anything in computing.

    Just like sending commands is always better for network use than sending pixmaps (scraping pixels, VNC-style), polling is just about always the worst possible solution. But it's probably the only possible one, forced by Wayland's design, just like the pixel-scraping for networking (or the other proposition, per-toolkit thing which nobody will implement, or with which every toolkit will be incompatible with each other. Seriously, it's a huge advantage to have network support for *every* app by default, not just those compiled with toolkit foo.)

    I wouldn't argue about polling being a bad idea in general but sending commands isn't the best way for dumb retinal situations. Additionally, I don't know how well sending 3d commands would work from a performance POV.

    I'm not sure polling is there only option. Heck I'm not sure they settled on it. Only that it seemed to be the path they were going to use first.


    Hopefully there will be an fdo proposal made for sending drawing instructions across networks for those who want it but I'm fine with sending diffs.

    Leave a comment:


  • smitty3268
    replied
    Originally posted by Awesomeness View Post
    I did research. Wayland will only allow to kill unresponsive apps, not allow to minimize them.
    Link, or please explain why the simple process above won't work.

    Leave a comment:


  • Awesomeness
    replied
    Originally posted by smitty3268 View Post
    Please do some research. This is just plain false.
    I did research. Wayland will only allow to kill unresponsive apps, not allow to minimize them.

    Leave a comment:


  • curaga
    replied
    In RT systems your app is usually the only important thing on the whole system. So its efficiency and monopolizing the cpu doesn't matter there.

    Leave a comment:


  • newwen
    replied
    Originally posted by curaga View Post
    Yup, one of the worst techniques to do anything in computing.

    Just like sending commands is always better for network use than sending pixmaps (scraping pixels, VNC-style), polling is just about always the worst possible solution. But it's probably the only possible one, forced by Wayland's design, just like the pixel-scraping for networking (or the other proposition, per-toolkit thing which nobody will implement, or with which every toolkit will be incompatible with each other. Seriously, it's a huge advantage to have network support for *every* app by default, not just those compiled with toolkit foo.)
    In Real Time Systems, where determinism is everything, polling is the preferred method and usually, as in safety critical systems, interrupts are forbidden.
    Last edited by newwen; 31 January 2013, 11:21 AM.

    Leave a comment:


  • curaga
    replied
    Originally posted by liam View Post
    Last time I looked they were supposed to be using polling to determine if windows were responsive or not (I believe this works the same way as in android).
    Yup, one of the worst techniques to do anything in computing.

    Just like sending commands is always better for network use than sending pixmaps (scraping pixels, VNC-style), polling is just about always the worst possible solution. But it's probably the only possible one, forced by Wayland's design, just like the pixel-scraping for networking (or the other proposition, per-toolkit thing which nobody will implement, or with which every toolkit will be incompatible with each other. Seriously, it's a huge advantage to have network support for *every* app by default, not just those compiled with toolkit foo.)

    Leave a comment:


  • liam
    replied
    Originally posted by smitty3268 View Post
    There is a way to tell that applications are not responding (or otherwise something like a busy cursor wouldn't be possible).
    Last time I looked they were supposed to be using polling to determine if windows were responsive or not (I believe this works the same way as in android).

    Leave a comment:

Working...
X