Amr Bashir 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
..
.scripts 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
mobile 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
permissions 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
scripts 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
src 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
test 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
CHANGELOG.md 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
Cargo.toml 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
LICENSE_APACHE-2.0 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
LICENSE_MIT 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
README.md 36eee37220 Restructure the repository (#10796) 11 mesiacov pred
build.rs 36eee37220 Restructure the repository (#10796) 11 mesiacov pred

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