What is Tauri?
Electron.
Tauri binding for Python through Pyo3
51–60 of 61 posts
Re: Tauri binding for Python through Pyo3
#52Earlier quoted context omitted.
I worked on a team the switched v2 of our product from Python + QT to Tauri specifically to get away from QT. If you have any kind of specific design requirements, QT is pain. The ability to use the frontend web stack is a huge win especially for a team that already has frontend developers. Rust was a nice bonus.
Doesn't qt also offers a webview solution?
Re: Tauri binding for Python through Pyo3
#53There are pros/cons primarily being Tauri seems to allow creation of mobile apps which Wails doesn’t, but overall it’s been fantastic since I find Go to be an easier language for me.
Re: Tauri binding for Python through Pyo3
#54Earlier quoted context omitted.
Doesn't qt also offers a webview solution?
It’s very basic. Good enough for oauth flow but not much beyond that, definitely not to host your entire UI. Also I don’t see what the point of that would be.
Re: Tauri binding for Python through Pyo3
#55Earlier quoted context omitted.
It’s very basic. Good enough for oauth flow but not much beyond that, definitely not to host your entire UI. Also I don’t see what the point of that would be.
My point it's that you said you changed from QT to Tauri because of being able to use frontend frameworks but QT also allows you to do the same. Anki does something like that, but since you mentioned rust that might be the reason of the change to Tauri.
Re: Tauri binding for Python through Pyo3
#56Python, along with C++ enjoys the benefits of Qt. You can build great stuff with cross-platform Qt. And it won't be webview(Electron / Tauri) based. What would be the benefits of this? I can't think of any yet.
I worked on a team the switched v2 of our product from Python + QT to Tauri specifically to get away from QT. If you have any kind of specific design requirements, QT is pain. The ability to use the frontend web stack is a huge win especially for a team that already has frontend developers. Rust was a nice bonus.
Re: Tauri binding for Python through Pyo3
#57Not to distract from Python or Tauri, but lately I’ve been using Wails[0] which is similar to Tauri but with Go instead of Rust. There are pros/cons primarily being Tauri seems to allow creation of mobile apps which Wails doesn’t, but overall it’s been fantastic since I find Go to be an easier language for me. [0] https://wails.io/
It runs fine but, speaking as someone with no prior Android experience, once you need to leave the "Everything is in the view" model, it gets confusing. But that's more Android's fault than the framework's
Re: Tauri binding for Python through Pyo3
#58Python, along with C++ enjoys the benefits of Qt. You can build great stuff with cross-platform Qt. And it won't be webview(Electron / Tauri) based. What would be the benefits of this? I can't think of any yet.
Re: Tauri binding for Python through Pyo3
#59Not to distract from Python or Tauri, but lately I’ve been using Wails[0] which is similar to Tauri but with Go instead of Rust. There are pros/cons primarily being Tauri seems to allow creation of mobile apps which Wails doesn’t, but overall it’s been fantastic since I find Go to be an easier language for me. [0] https://wails.io/
Yep I've gotten basic Tauri stuff to run on Android. It runs fine but, speaking as someone with no prior Android experience, once you need to leave the "Everything is in the view" model, it gets confusing. But that's more Android's fault than the framework's
Re: Tauri binding for Python through Pyo3
#60Python, along with C++ enjoys the benefits of Qt. You can build great stuff with cross-platform Qt. And it won't be webview(Electron / Tauri) based. What would be the benefits of this? I can't think of any yet.
This, of course, comes at a cost of performance as CSS alone is very complicated and has a lot there to support. On the flip side, there are many things that are easy to do with HTML+CSS that are much more difficult with native UI frameworks. Just the reflow support for multiple sizes/scaling in browsers is hard to match.