wry VS femtovg

The biggest benefits we derived from Tauri were Wry and the sidecar mechanism. Wry (the second half of Tauri: tao/wry) is a cross-platform WebView rendering library in Rust that supports all major desktop platforms like Windows, macOS, and Linux. It essentially spins up a native web view from whatever operating system it’s running on and doesn’t require an application to bundle one with it. Wry greatly reduces the overhead of “pushing” a browser to our users, instead leaning on the host OS to handle rendering a web view. This made our applications really lean.

Check out https://tauri.app/ - specifically, https://github.com/tauri-apps/wry, which provides a cross-platform interface to the system's WebView.

Tauri uses WebkitGTK, which has pretty bad performance compared to other browsers on the same hardware.

https://github.com/tauri-apps/wry/issues/890#issuecomment-14...

One small note regarding Native Webview meant above. You can find ultimate information on this topic here. In a nutshell, Tauri applications use as HTML renderer Webkit (safari engine) on MacOS, Microsoft Edge WebView2 on Windows, and WebKitGTK on Linux (port of Webkit for Linux). Pay attention to the fact that a Tauri application could behave differently on different platforms according to the information above.

wry looks like a better choice, but no one has bothered to work on this task, yet.

I think this might be somewhat close to what you're looking for: https://github.com/tauri-apps/wry

They're wrapping the Android webkit/webview stuff in wry and creating an activity for it. I imagine they've already achieved or are close to achieving full parity API-wise to proper Tauri desktop apps.

Another way to approach it is to wrap the web app in a webview and use Tauri for custom logic, see https://github.com/tauri-apps/wry. You'd need to teach yourself some Rust though. I'm sure you could achieve something similar with Express. The performance will be similar to using a browser so not terrible.

It uses the WebView that the underlying OS provides to render the application’s UI — this is one of the reasons why the application binaries are smaller (as compared to electron). The WRY library from the Tauri toolkit provides a unified interface to interact with WebViews provided by different operating systems. The WRY library uses the Tao crate for cross-platform window management.

Femtovg (https://github.com/femtovg/femtovg) which uses OpenGL to render

Congrats! I don't want to diminish the accomplishment, but have you seen femtovg? It seems like it's probably well-aligned with your needs.

I'm currently using femtovg for vector graphics in my games, and I would like to get into bevy by porting one of my game prototypes using it to bevy.

I use femtovg It's a simple vector graphics engine having all the important features you probably want from a 2D rendering engine: simple shapes, images, text

https://github.com/femtovg/femtovg/pull/5

Before Power10 was done, IBM actually asked us Raptor users about proposals for useful machine code instructions to add to it. I replied that I’d like to have hardware UTF-8 de-/encoding but they wanted a more detailed proposal and I never got around to write it. I’m not even sure that this would be worthwhile, but I see UTF-8 de-/encoding everywhere in the code I write and would like it to approach memory read/write speeds.

I was very disappointed to learn that they had gone more proprietary with Power10 so I would not have been able to use those instructions anyway. What a pity!

In my actual code, I'm using a library called femtovg that is a Rust port of a C library for 2D rendering. But In the blog post I kept the example simple to keep it relevant for people who might want to use Web Workers + WASM for other things; didn't want to get hung up on femtovg for someone who had never heard of it. As you say, if you all you need to do is basic 2D manipulations of a canvas that are supported by the native API, then you likely don't need WASM.

You guys should also check out the femtovg project, a 2D rendering API that sixty fps relies on.

https://github.com/femtovg/femtovg

It's a decent starting point for trying to build your own toolkit.

I have recently added a wgpu backend but for now it lives in my fork https://github.com/adamnemecek/femtovg

run the demo with `cargo run --example wgpu_demo --release`.

Also join the femtovg discord https://discord.gg/V69VdVu

I'm involved with the femtovg project. We are definitely looking for contributors. Join the discord channel.

It's not a GUI framework but I'm involved with this project called femtovg, it's a Rust nanovg port. I've recently added a wgpu backend. Run the demo with cargo run --example wgpu_demo --release. Some people have been using it for their own UIs, e.g. tuix. I think that you should consider rolling your own GUI toolkit, it's not that bad and you'll appreciate the control.