Linked by Thom Holwerda on Wed 21st Feb 2018 23:10 UTC
OS/2 and eComStation

You have no idea how much effort went into getting this stupid white square on the screen.

If this one hell of a lede doesn't get your attention, nothing will.

Thread beginning with comment 654092
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by FlyingJester
by The123king on Fri 23rd Feb 2018 12:56 UTC in reply to "RE[3]: Comment by FlyingJester"
The123king
Member since:
2009-05-28

Wouldn't that have the added bonus of increased portability? One of my personal gripes with WINE is it's dependecy on X11, which can stymie porting attempts to non-UNIX systems, such as Haiku or AROS.

Reply Parent Score: 1

FlyingJester Member since:
2016-05-11

Wine itself doesn't depend on X11, it runs on OS X without X11.

Reply Parent Score: 3

The123king Member since:
2009-05-28

I was under the assumption that WINE on macOS still used X11, or have they got an native quartz interface now?

And surely the Windows port uses X11. I can't imagine it's easy integrating WINE win32 calls with actual Windows Win32 calls. I know ReactOS sort of does this, but that has no underlying Windows components to "replace"

Reply Parent Score: 2

jpkx1984 Member since:
2015-01-06

WINE has no hard dependency on X11, there is even an experimental wine build running on... Windows. However, there is one catch on Linux: WINE does not work on Wayland due to limitations of the latter. The Wayland protocol as such does not provide ability to introspect window positions or access the display (they want to keep it simple; extras are supposed to be implemented at the compositor level); that's why it breaks all the apps requiring such information: remote desktop apps, redshift, WINE etc. It could be some day Wayland compositors (such as Gnome's Mutter or KDE's KWin) will develop interfaces to share that information with apps but at this point we have to rely on Xorg.

Reply Parent Score: 4