api-guidelines
tauri
api-guidelines | tauri | |
---|---|---|
32 | 470 | |
1,203 | 77,375 | |
0.6% | 1.2% | |
3.3 | 9.8 | |
about 2 months ago | 7 days ago | |
Rust | ||
Apache License 2.0 | 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.
api-guidelines
- Best practices for designing traits in public crates?
-
Functional Options Pattern in Go and Rust
Just wanting to let this here for some further input: - https://rust-lang.github.io/api-guidelines/ - https://rust-unofficial.github.io/patterns/ - https://deterministic.space/elegant-apis-in-rust.html
-
Hey Rustaceans! Got a question? Ask here (15/2023)!
The API guidelines will help you write nice APIs. Clippy will usually at least find some things, try running with -Wclippy::pedantic for a lot more messages. Also you can ask mentors for specific guidance. Hope that helps.
-
Naming traits
There has been some previous discussion on this here: https://github.com/rust-lang/api-guidelines/discussions/28
-
What is the proper guidance on using generics as parameters for an API
I'm currently writing an API and using the API guidelines book. On the Flexibility page, there's a section on using generics as function parameters to minimize assumptions. The issue that I'm having is that the only example it gives is std::fs::File::open. Specifically, I want to know what is the "standard" way to use generics as parameters?
-
Prefixes in name and Reexports
I search up in the rust-api-guideline, but no luck finding something like this. There used to be an Organization according to this thread, but upon digging the repo commits, it was deleted by this commit. "We can reintroduce this section if we come up with a way to give firmer advice here."
-
What are some good practices when writing rust?
public api of a library should follow Rust API Guidelines.
-
astro-float 0.6.6 arbitrary precision floating point library update
API was made compliant with Rust API Guidelines.
-
Picking Up Rust Before C With My Goals In Mind?
Finally, there's also the Little Book of Rust Books where you could look for tutorial materials or things like like Rust Design Patterns, Rust API Guidelines, and The Rust Performance Book. (See also rust-learning)
-
Learning rust
Rust API Guidelines: If you're planning on building libraries or APIs in Rust, these guidelines provide recommendations for designing and presenting APIs in the language. They're written by the Rust library team, based on their experience building the Rust standard library and other crates in the ecosystem.
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?
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
Wails - Create beautiful applications using Go
patterns - A catalogue of Rust design patterns, anti-patterns and idioms
neutralinojs - Portable and lightweight cross-platform desktop application development framework
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
dioxus - Fullstack GUI library for web, desktop, mobile, and more.
idiomatic-rust - 🦀 A peer-reviewed collection of articles/talks/repos which teach concise, idiomatic Rust.
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
rust - Empowering everyone to build reliable and efficient software.
egui - egui: an easy-to-use immediate mode GUI in Rust that runs on both web and native
gdnative - Rust bindings for Godot 3
iced - A cross-platform GUI library for Rust, inspired by Elm