Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clearification about winit and gtk #509

Closed
ShalokShalom opened this issue Aug 2, 2022 · 4 comments
Closed

Clearification about winit and gtk #509

ShalokShalom opened this issue Aug 2, 2022 · 4 comments

Comments

@ShalokShalom
Copy link

The text at the end of the readme suggests me, that gtk is planned to be outfaded.

Is this true, and is there a timeframe for this?

How high on the priority list is this?

thanks

@FabianLars
Copy link
Member

that gtk is planned to be outfaded.

Not anytime soon, running webkitgtk outside of gtk is not fun or not even possible, i don't know.
The idea is to (somehow) decouple gtk from tao/winit so that we can hopefully switch wry/tauri to upstream winit again.
A relevant issue which tracks smaller differences: #470.
Apart from gtk and the things mentioned in the other issue, we also need to make the other features we added like menus, trays, etc. modular (uncoupled from tao) so that we can use them with winit. This also needs changes on the winit side so it probably will take a while, but the current plan is to have that done for tauri v2.

@ShalokShalom
Copy link
Author

But that would still leave webkitgtk?

Even with the OpenGL renderer?

The @servo project tried to develop an interface just in web languages and with WebGL rendering.

I really want a Qt based solution.
Or really anything else than GTK.

There is a Qt port of WebKit as well.

@FabianLars
Copy link
Member

both gtk and webkitgtk will stay with us, yes. It just won't be part of winit directly.

i don't know about the far future, but for now opengl windows will also use gtk windows since we swapped the whole linux platform to use that.

I really want a Qt based solution.

Yeah no, that most likely won't happen. Using qt from rust is just the worst, i can't even describe it tbh.

There is a Qt port of WebKit as well.

It's chromium, but whatever. Here's also another issue about that: tauri-apps/tauri#4554

So tldr: qt won't happen. Even native x11/wayland is currently more likely.

And the last thing, since you mentioned servo, there's ongoing research to turn servo into a webview and make tauri+servo happen :)

@amrbashir
Copy link
Member

The plan is to extract functionalities from tao into their own separate crates (menus and system trays. global shortcut and clipboard will be removed), then we will make a winit_gtk crate which is just winit but with gtk as the linux backedn (so basically tao without the extras). I hope this clarifies the situation.

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

No branches or pull requests

3 participants