9 ms·

Is the same infrastructure available in Windows and MacOS?

deleted 3y ago
[deleted]
diath 3y ago
The last paragraph says: > At the moment, graphics offload will only work with Wayland on Linux. There is some hope that we may be able to implement similar things on MacOS, but for now, this is Wayland-only. It also depends on the content being in dmabufs.
knocte 3y ago
From the article: > What are the limitations? > At the moment, graphics offload will only work with Wayland on Linux. There is some hope that we may be able to implement similar things on MacOS, but for now, this is Wayland-only. It also depends on the content being in dmabufs.
- PlutoIsAPlanet 3y ago
  macOS supports similar things in its own native stack, but GTK doesn't make use of it.
pjmlp 3y ago
Nope, it is yet another step making Gtk only relevant for Linux development.
- andersa 3y ago
  Has it been relevant for something else before?
  - pjmlp 3y ago
    Yes, back when G stood for Gimp, and not GNOME.
    - microtonal 3y ago
      Even in those days, Gtk+ applications were quite horrible on non-X11 platforms. GTK has never been a good cross-platform toolkit in contrast to e.g. Qt.
      - pjmlp 3y ago
        I guess people enjoying GIMP and Inkscape would beg to differ.
        microtonal 3y ago
        Maybe it’s a thing on Windows (I don’t know), but I’ve never seen anyone use GIMP or Inkscape on macOS. I’m pretty sure they exist somewhere, but all Mac users I know use Photoshop, Pixelmator or Affinity Photo rather than GIMP.
        ognarb 3y ago
        Inskape devs have a lot of trouble making their app work on other OS.
- jdub 3y ago
  Supporting a feature on one platform does not make a toolkit less relevant or practical on another platform.
  - pjmlp 3y ago
    Except this has been happening for quite a while, hence why a couple of cross platform projects have migrated from Gtk to Qt, including Subsurface, a bit ironically, given the relationship of the project to Linus.
    - jdub 3y ago
      Gtk has always been primarily built by and for Linux users.
      - pjmlp 3y ago
        The GIMP Tolkit was always cross platform, the GNOME Tolkit not really.
        jdub 3y ago
        That is ahistorical, and the misnaming doesn't help make your point.
        pjmlp 3y ago
        As former random Gtkmm contributor, with articles on the The C/C++ User Journal, I am not the revisionist here.
        DonHopkins 3y ago
        What's a Tolkit? And why two of them? I thought GTK was the Toolkit, GIMP was the Image Manipulation Program, and Gnome was the desktop Network Object Model Environment. Am I a revisionist here? (I certainly have my reservations about them!)
jamesfmilne 3y ago
macOS has IOSurface [0], so it can be done there too. It would require someone to implement it for GTK. [0] https://developer.apple.com/documentation/iosurface https://developer.apple.com/documentation/iosurface
- audidude 3y ago
  When I wrote the macOS backend and GL renderer I made them use IOSurface already. So it's really a matter of setting up CALayer automatically the same way that we do it on Linux. I don't really have time for that though, I only wrote the macOS port because I had some extra holiday hacking time.
torginus 3y ago
On Windows and DirectX, you have the concept of Shared Handles, which are essentially handles you can pass between process boundaries. It also comes with a mutex mechanism to signal who is using the resource at the moment. Fun fact - Windows at the kernel level works with the concept of 'objects', which can be file handles, window handles, threads, mutexes, or in this case, textures, which are reference counted. Sharing a particular texture is just exposing the handle to multiple processes. A bit of reading if you are interested: https://learn.microsoft.com/en-us/windows/win32/direct3darticles/surface-sharing-between-windows-graphics-apis?redirectedfrom=MSDN#dxgi_1.1_synchronized_shared_surfaces https://learn.microsoft.com/en-us/windows/win32/direct3darti...

deleted 3y ago

[deleted]

The last paragraph says: > At the moment, graphics offload will only work with Wayland on Linux. There is some hope that we may be able to implement similar things on MacOS, but for now, this is Wayland-only. It also depends on the content being in dmabufs.

knocte 3y ago

From the article: > What are the limitations? > At the moment, graphics offload will only work with Wayland on Linux. There is some hope that we may be able to implement similar things on MacOS, but for now, this is Wayland-only. It also depends on the content being in dmabufs.

PlutoIsAPlanet 3y ago
macOS supports similar things in its own native stack, but GTK doesn't make use of it.

pjmlp 3y ago

Nope, it is yet another step making Gtk only relevant for Linux development.

andersa 3y ago
Has it been relevant for something else before?
- pjmlp 3y ago
  Yes, back when G stood for Gimp, and not GNOME.
  - microtonal 3y ago
    Even in those days, Gtk+ applications were quite horrible on non-X11 platforms. GTK has never been a good cross-platform toolkit in contrast to e.g. Qt.
    - pjmlp 3y ago
      I guess people enjoying GIMP and Inkscape would beg to differ.
      - microtonal 3y ago
        Maybe it’s a thing on Windows (I don’t know), but I’ve never seen anyone use GIMP or Inkscape on macOS. I’m pretty sure they exist somewhere, but all Mac users I know use Photoshop, Pixelmator or Affinity Photo rather than GIMP.
      - ognarb 3y ago
        Inskape devs have a lot of trouble making their app work on other OS.
jdub 3y ago
Supporting a feature on one platform does not make a toolkit less relevant or practical on another platform.
- pjmlp 3y ago
  Except this has been happening for quite a while, hence why a couple of cross platform projects have migrated from Gtk to Qt, including Subsurface, a bit ironically, given the relationship of the project to Linus.
  - jdub 3y ago
    Gtk has always been primarily built by and for Linux users.
    - pjmlp 3y ago
      The GIMP Tolkit was always cross platform, the GNOME Tolkit not really.
      - jdub 3y ago
        That is ahistorical, and the misnaming doesn't help make your point.
        pjmlp 3y ago
        As former random Gtkmm contributor, with articles on the The C/C++ User Journal, I am not the revisionist here.
        DonHopkins 3y ago
        What's a Tolkit? And why two of them? I thought GTK was the Toolkit, GIMP was the Image Manipulation Program, and Gnome was the desktop Network Object Model Environment. Am I a revisionist here? (I certainly have my reservations about them!)

jamesfmilne 3y ago

macOS has IOSurface [0], so it can be done there too. It would require someone to implement it for GTK. [0] https://developer.apple.com/documentation/iosurface https://developer.apple.com/documentation/iosurface

audidude 3y ago
When I wrote the macOS backend and GL renderer I made them use IOSurface already. So it's really a matter of setting up CALayer automatically the same way that we do it on Linux. I don't really have time for that though, I only wrote the macOS port because I had some extra holiday hacking time.

torginus 3y ago

On Windows and DirectX, you have the concept of Shared Handles, which are essentially handles you can pass between process boundaries. It also comes with a mutex mechanism to signal who is using the resource at the moment. Fun fact - Windows at the kernel level works with the concept of 'objects', which can be file handles, window handles, threads, mutexes, or in this case, textures, which are reference counted. Sharing a particular texture is just exposing the handle to multiple processes. A bit of reading if you are interested: https://learn.microsoft.com/en-us/windows/win32/direct3darticles/surface-sharing-between-windows-graphics-apis?redirectedfrom=MSDN#dxgi_1.1_synchronized_shared_surfaces https://learn.microsoft.com/en-us/windows/win32/direct3darti...