Skip to content
This repository has been archived by the owner on Jul 15, 2024. It is now read-only.

Remove the GTK backend #103

Merged
merged 1 commit into from
Jun 25, 2023
Merged

Remove the GTK backend #103

merged 1 commit into from
Jun 25, 2023

Conversation

DJMcNab
Copy link
Member

@DJMcNab DJMcNab commented Jun 15, 2023

As discussed in office hours today and #glazier > Near-term Linux pushes

To clarify reasoning, we don't have any will to maintain this backend - the other Linux backends need more attention

@DJMcNab DJMcNab marked this pull request as ready for review June 15, 2023 18:48
@xStrom
Copy link
Member

xStrom commented Jun 15, 2023

This may be the right thing to do, but we shouldn't rush this.

I think we should wait on this until we have a clearer consensus on the Linux strategy. There have been many attempts to reach such a consensus in the past, but they've fizzled out.

I will go through historic issues and chat logs and create a Linux strategy meta issue here in the Glazier repo. Then we can have additional discussion on top. The idea is to have a clear idea of what are the pros and cons of each Linux backend and what the ideal future scenario looks like.

@DJMcNab
Copy link
Member Author

DJMcNab commented Jun 25, 2023

To track this in the git history:

  • We currently don't believe that the GTK backend can work with wgpu/Vulkan, and that is currently the only supported drawing scheme
  • See also Deciding the Linux strategy #106

Therefore, we are having to remove this backend.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants