Originally posted by sireangelus
View Post
Announcement
Collapse
No announcement yet.
The Wayland Situation: Facts About X vs. Wayland
Collapse
X
-
Originally posted by jrdls View PostVery nice article. I've seen some demos here and there of wayland and the rendering looks smooth. I have a couple of questions though:
I) Are there any features in wayland/weston that you guys have to implement before they are considered ready for production use or are they ready now?
II) Do you think Matt Hartley from The Linux Action Show will wear the monkey suit? XD
2) Monkey suit? o.O I must have missed that episodeAll opinions are my own not those of my employer if you know who they are.
Comment
-
Originally posted by RussianNeuroMancer View Posthttp://phoronix.com/forums/showthrea...589#post260589 (message #18).All opinions are my own not those of my employer if you know who they are.
Comment
-
Originally posted by GreatEmerald View PostYea, I thought it might be. I'm learning British English, though, so that's why my preference is no comma before and. But thanks for clearing that up.
Of course, being the sort of thing that pedants can argue about endlessly, the internet is full of deep discussion on it, in Wikipedia entries, articles rehashing what everyone else has said, infographics, and crude comics.
Comment
-
Originally posted by Ericg View Post1) Daniel is still working on touchpad acceleration. Also, to my knowledge, minimization, and unfullscreening have yet to be finalized. Those are the only three "Big" things I know about. Daniel may know of some more.
2) Monkey suit? o.O I must have missed that episode
Comment
-
Originally posted by Ericg View PostWait, you're actually USING powersave on battery? You do know that it uses MORE power if you're doing anything that lasts more than a couple seconds, right? Time To Idle.
Comment
-
Originally posted by Skrapion View PostThere's so much wrong here.
First of all, WDM is the Windows Driver Model, and it was dropped when Windows Vista was released. The driver API in Windows Vista is called the Windows Driver Foundation, and the display driver portion of that is called the Windows Display Driver Model (WDDM), which is perhaps what you're thinking of.
Everything else is pretty much right, but not related to the question, which was already answered by other user.
EDIT: Except for the thing about Win32 API, which is actually the answer given. One does not target DWM or whatever it was the underlying infrastructure before, but Win32 API. And when something gets deprecated, there are still compatibility layers, similar to what xwayland does.
Originally posted by dee. View PostMatt said he'd wear a monkey suit on air if Wayland gets finished (ie. in production use in a regular desktop distro) faster than Mir...
For them, finished is "kinda works", so they're likely to be "finished" before. Even when Wayland already "kinda works", even when it's only with open source drivers.
Comment
-
Originally posted by cmr~ View PostIt doesn't have to be a window manager, it could delegate that to something else. It also doesn't have to place windows on the screen. It composites multiple sources into one.
Originally posted by Ericg View PostWait, you're actually USING powersave on battery? You do know that it uses MORE power if you're doing anything that lasts more than a couple seconds, right? Time To Idle.
Comment
-
Originally posted by Ericg View PostWait, you're actually USING powersave on battery? You do know that it uses MORE power if you're doing anything that lasts more than a couple seconds, right? Time To Idle.Last edited by sireangelus; 08 June 2013, 01:09 PM.
Comment
-
Originally posted by GreatEmerald View PostBy the way, why is it called a "compositor", anyway, if it's actually a window manager? Aside from the fact that you require it to support compositing, that is.
Noun
1. The act of combining parts or elements to form a whole.
And that is really what a compositor does at its lowest level, it create a composite image out of a bunch of smaller images. It takes various images (the windows), manipulates them appropriately (for instance removing bits that are hidden below other bits), then combines them to form a larger image. This larger image is then displayed on the screen.
The Wayland protocol is in charge of getting the images of the windows to the compositor so it can put them together, then the compositor passes the single large image back to Wayland which then passes it along to the hardware so it can be placed on the screen.
It is a bit more complicated then this in practice, since there are optimizations that can be done. For example it can only re-send parts of the image that have changed. But the basic idea goes a long way to explaining what is happening.Last edited by TheBlackCat; 08 June 2013, 12:58 PM.
Comment
Comment