Originally posted by Ericg
View Post
Announcement
Collapse
No announcement yet.
The Wayland Situation: Facts About X vs. Wayland
Collapse
X
-
Originally posted by valeriodean View PostnVidia and Intel?
Maybe you meant nVidia and AMD proprietary driver.
About Intel, there are no problems, as you probably know, their official drivers are open and delivered with the kernel.
About the open driver of nVidia and AMD, as you can read, they work because are open and then easy to adapt.
For the binary blob, the situation is different because only who have access to the code (the nVidia and AMD internal devs) can implement the needed modification.
As for the Intel drivers. It was not obvious to me that open source drivers translates directly to Wayland compatibility. Hence my question.
Comment
-
Originally posted by sireangelus View Post...
And i must say also that i'm used to build and load my own kernels... and that squeezes a little bit more of performance and battery life out of them.
...or harms performance/battery unless you really know what you are doing.
Have you by any chance kept your benchmark results for the various kernel configs?
Comment
-
Originally posted by daniels View Postyes, it's axial, hence the separate x and y co-ordinates. it's signed so you can place subsurfaces outside the bounds of the parent, e.g. to do external decorations.
Comment
-
-
Originally posted by Ericg View PostQt4, GTK2, and other-toolkit apps
Comment
-
Backwards compatibility
would most games require Xwayland?
In this case i'm thinking of Neverwinter Nights, which I know uses sdl, I don't know how that relates to any thing though
and what about a given gtk3 app would that app be compatable once gtk3 supports wayland or does the developer have to update it to support wayland?
Comment
-
Originally posted by garegin View Postericg can you confirm this for me? as far as i understand the pixel-perfect motto is not entirely true. on both osx and windows I sometimes get artifacts, so I don't think wayland can overcome that? or can itAll opinions are my own not those of my employer if you know who they are.
Comment
-
How will Wayland work with graphics tablets, particularly on multiple monitor setups? My tablet works great as long as I stick to a single monitor, but if I add in one of my other monitors into the mix working with the tablet quickly becomes a real pain. The main way I tried to deal with it is to bind the tablet to a single monitor using a coordinate transformation matrix with xinput, which works to limit the tablet to the screen I want but programs seem to at least partially ignore it, so that the further I get from the top left corner of an application the further my lines drift away from the cursor position making design work a nightmare in a multiscreen situation. It would be really nice if Wayland can allow me to make use of my tablet at the same time as the 2 spare monitors I have collecting dust at the moment.
Comment
Comment