Qt-Advanced-Docking-System
tauri
Qt-Advanced-Docking-System | tauri | |
---|---|---|
3 | 470 | |
1,665 | 77,588 | |
- | 1.4% | |
8.3 | 9.8 | |
13 days ago | 3 days ago | |
C++ | Rust | |
GNU Lesser General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Qt-Advanced-Docking-System
-
Going all-in on Rust
Personally, I'm partial to the PyO3+PyQt/PySide option because Qt's QWidget APIs are a very polished and mature way to build a portable "as native as feasible without writing a separate frontend for each platform" GUI with great quality-of-life things like QMainWindow::saveState, PyQt-compatible bindings for addons like Qt Advanced Docking System, and tooling like MyPy. (It also helps that, as a KDE user, QWidget is the platform's native UI API.)
-
How do I include external libraries in a project? Specifically the Qt Advanced Docking System
Clone it into a subdirectory and then add it via add_subdirectory(Qt-Advanced-Docking-System). Then add it to your app via target_link_libraries(MyAppName PRIVATE qtadvanceddocking) as seen in https://github.com/githubuser0xFFFF/Qt-Advanced-Docking-System/blob/master/examples/simple/CMakeLists.txt.
tauri
- Ask HN: Best stack for building a desktop app?
-
Tauri CRUD Boilerplate
Hi, dear Tauri! Long time no see. I published my first post, Developing a Desktop Application via Rust and NextJS. The Tauri Way almost a year ago. Since then, Tauri has become stronger. I'm happy about that! And now, I am very pleased to make a useful contribution to the Tauri community. As a full-stack developer, I frequently face situations where I need to start a DB-based UI project as fast as possible. It's stressful if I need to start the project from 100% scratch. I prefer to keep some boilerplates on hand, which will save me time and nerves and will be the subject of this article.
-
Show HN: Floro – Visual Version Control for static assets and strings
Hey Thanks!
Just electron & vite. I might actually migrate off electron, Tauri (https://tauri.app/) seems to be getting more stable and it's gotten great reviews.
I think this is the boilerplate I used though https://github.com/cawa-93/vite-electron-builder.
-
3D and 2D: Testing out my cross-platform graphics engine
Well the great thing about WebAssembly is that you can port QT or anything else to be at a layer below -- thanks to WebAssembly Interface Types[0] and the Component Model specification that works underneath that.
To over-simplify, the Component Model manages language interop, and WIT constrains the boundaries with interfaces.
IMO the problem here is defining a 90% solution for most window, tab, button, etc management, then building embeddings in QT, Flutter/Skia, and other lower level engines. Getting a good cross-platform way of doing data passing, triggering re-renders, serializing window state is probably the meat of the interesting work.
On top of that, you really need great UX. This is normally where projects fall short -- why should I use this solution instead of something like Tauri[2] which is excellent or Electron?
[0]: https://github.com/WebAssembly/component-model/blob/main/des...
[1]: https://github.com/WebAssembly/component-model/blob/main/des...
[2]: https://tauri.app/
-
Interview with Colin Lienard, Founder of GitLight
Welcome to the 2nd episode of our series “Building with Tauri”, where we chat with developers who build amazing projects and products using Tauri.
-
Building W-9 Crafter
Tauri seemed like the "thing" I should switch to because everybody loves Rust (heh), and because it ships significantly smaller apps.
-
Tauri + React + ShadcnUI
First of all, I will be using npm as my package manager but feel free to use whatever you prefer. Find more info here.
- Slint 1.5: Embracing Android, Improving Live-Preview, and Pythonic Slint
- Shoes makes building little graphical programs for Mac, Windows, Linux simple
-
Tauri - Rust, Js and Native Apps
Today I'm talking about Tauri! Do you know all the various tools that allow you to develop native applications starting from web languages? They often need an intermediate compilation, in the middle of which you end up encountering various problems not always transparent and directly solvable with a language mostly detached from native development. On the other hand, there's still the ease of developing attractive and easily usable interfaces, which are more difficult to develop with low level languages.
What are some alternatives?
dockingpanes - A Visual Studio style docking windows library for Qt Widgets based applications
Wails - Create beautiful applications using Go
Qt - Qt Base (Core, Gui, Widgets, Network, ...)
neutralinojs - Portable and lightweight cross-platform desktop application development framework
Qv2ray - :star: Linux / Windows / macOS 跨平台 V2Ray 客户端 | 支持 VMess / VLESS / SSR / Trojan / Trojan-Go / NaiveProxy / HTTP / HTTPS / SOCKS5 | 使用 C++ / Qt 开发 | 可拓展插件式设计 :star:
dioxus - Fullstack GUI library for web, desktop, mobile, and more.
gtk-rs - Rust bindings for GTK 3
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
PyO3 - Rust bindings for the Python interpreter
egui - egui: an easy-to-use immediate mode GUI in Rust that runs on both web and native
openauto - AndroidAuto headunit emulator
iced - A cross-platform GUI library for Rust, inspired by Elm