Amr Bashir f48ce21b31 Merge branch 'dev' into feat/gtk-appi-id 1 жил өмнө
..
.scripts 4b75834a41 chore: update license headers 2024 (#9043) 1 жил өмнө
mobile 4b75834a41 chore: update license headers 2024 (#9043) 1 жил өмнө
permissions 477bb8cd4e feat: add `cursor_position` getter (#9297) 1 жил өмнө
scripts b0421cbb21 chore: rebuild bundle.global.js (#9625) 1 жил өмнө
src f48ce21b31 Merge branch 'dev' into feat/gtk-appi-id 1 жил өмнө
test 8de308d1bf feat(core): implement new config structure (#8723) 1 жил өмнө
CHANGELOG.md 1bee4f279f Apply Version Updates From Current Changes (#9693) 1 жил өмнө
Cargo.toml 1bee4f279f Apply Version Updates From Current Changes (#9693) 1 жил өмнө
LICENSE_APACHE-2.0 319cf16a54 fix: prune packages, add license files, closes #1507 (#1769) 4 жил өмнө
LICENSE_MIT 319cf16a54 fix: prune packages, add license files, closes #1507 (#1769) 4 жил өмнө
README.md 96d346222f docs: Update Github workflow status shields (#6910) 2 жил өмнө
build.rs 477bb8cd4e feat: add `cursor_position` getter (#9297) 1 жил өмнө

README.md

Tauri

status License test core FOSSA Status Chat Server website support

Component Version
tauri

About Tauri

Tauri is a polyglot and generic system that is very composable and allows engineers to make a wide variety of applications. It is used for building applications for Desktop Computers using a combination of Rust tools and HTML rendered in a Webview. Apps built with Tauri can ship with any number of pieces of an optional JS API / Rust API so that webviews can control the system via message passing. In fact, developers can extend the default API with their own functionality and bridge the Webview and Rust-based backend easily.

Tauri apps can have custom menus and have tray-type interfaces. They can be updated, and are managed by the user's operating system as expected. They are very small, because they use the system's webview. They do not ship a runtime, since the final binary is compiled from rust. This makes the reversing of Tauri apps not a trivial task.

This module

This is the glue crate that holds everything together. It brings the runtimes, macros, utilities and API into one final product. It reads the tauri.conf.json file at compile time in order to bring in features and undertake actual configuration of the app (and even the Cargo.toml file in the project's folder). It handles script injection (for polyfills / prototype revision) at runtime, hosts the API for systems interaction, and even manages updating.

To learn more about the details of how all of these pieces fit together, please consult this ARCHITECTURE.md document.

Semver

tauri is following Semantic Versioning 2.0.

Licenses

Code: (c) 2019 - 2021 - The Tauri Programme within The Commons Conservancy.

MIT or MIT/Apache 2.0 where applicable.

Logo: CC-BY-NC-ND