1 TAURI[편집]

1.1 설치[편집]

npm create tauri-app@latest

1.2 APP 만들기[편집]

1.2.1 HTML, CSS, and JavaScript 환경[편집]

Tauri는 프런트엔드 프레임워크와 Rust 코어를 사용하여 데스크톱 애플리케이션을 구축하기 위한 프레임워크.
각 앱은 두 부분으로 구성
- 창을 생성하고 해당 창에 기본 기능을 노출하는 Rust 바이너리
- 창 내부에 사용자 인터페이스를 생성하는 원하는 프런트엔드

1.2.1.1 APP 생성[편집]

1.2.1.1.1 프런트엔드를 구축[편집]

개발환경 확인사항

1) 폴더생성

mkdir ui

2) index.html 생성

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
  </head>
  <body>
    <h1>Welcome from Tauri!</h1>
  </body>
</html>

1.2.1.1.2 RUST 프로젝트 생성[편집]

모든 Tauri 앱의 중심에는 윈도우, 웹뷰를 관리하고 tauri Rust 상자를 통해 운영 체제를 호출하는 Rust 바이너리가 있습니다.
이 프로젝트는 Rust의 공식 패키지 관리자이자 범용 빌드 도구인 Cargo에 의해 관리된다.
우리의 타우리 CLI는 후드 아래에 카고를 사용하므로 직접 상호 작용할 필요가 거의 없습니다.
Cargo에는 테스트, 린팅 및 포맷과 같은 CLI를 통해 노출되지 않는 더 많은 유용한 기능이 있으므로 자세한 내용은 공식 문서를 참조하십시오.

실행

npm run taturi init

It will walk you through a series of questions:
- What is your app name?
  This will be the name of your final bundle and what the OS will call your app. You can use any name you want here.
- What should the window title be?
  This will be the title of the default main window. You can use any title you want here.
- Where are your web assets (HTML/CSS/JS) located relative to the <current dir>/src-tauri/tauri.conf.json file that will be created?
  This is the path that Tauri will load your frontend assets from when building for production.
  
  Use ../ui for this value.
- What is the URL of your dev server?
  This can be either a URL or a file path that Tauri will load during development.

Use ../ui for this value.

- What is your frontend dev command?
  This is the command used to start your frontend dev server.
  
  You can leave this blank since nothing needs to be compiled.
- What is your frontend build command?
  This is the command to build your frontend files.
  
  You can leave this blank since nothing needs to be compiled.

"If you're familiar with Rust, you will notice that tauri init looks and works a lot like cargo init.

You can just use cargo init and add the necessary Tauri dependencies if you prefer a fully manual setup.

The tauri init command generates a folder called src-tauri. It's a convention for Tauri apps to place all core-related files into this folder. Let's quickly run through the contents of this folder:"

Cargo.toml
Cargo's manifest file. You can declare Rust crates your app depends on, metadata about your app, and much more. For the full reference see Cargo's Manifest Format.

tauri.conf.json
This file lets you configure and customize aspects of your Tauri application from the name of your app to the list of allowed APIs. See Tauri's API Configuration for the full list of supported options and in-depth explanations for each.

src/main.rs
This is the entry point to your Rust program and the place where we bootstrap into Tauri. You will find two sections in it:

#![cfg_attr(not(debug_assertions), windows_subsystem = "windows")]

fn main() {
tauri::Builder::default()
   .run(tauri::generate_context!())
   .expect("error while running tauri application");
}

1.2.2 Next.js 환경[편집]

Front end build tools

1.2.3 Qwik[편집]

Front end build tools

1.2.4 SvelteKit[편집]

Front end build tools

1.2.5 Vite[편집]

Front end build tools

TAURI

DB CAFE

목차