update doc

Author: syf20020816

README.md

@@ -1,10 +1,10 @@
 # GenUI Book
 
-🥳 GenUI v0.1.0 has been released
+🥳 GenUI v0.1.1 has been released
 
-- [GenUI](https://github.com/Privoce/GenUI/releases/tag/v0.1.0)
-- [Ract](https://github.com/Privoce/ract/releases/tag/v0.1.1)
-- [GenUI Builtin Component](https://github.com/Privoce/GenUI-Builtin-Component/releases/tag/v0.2.0)
+- [GenUI](https://github.com/Privoce/GenUI/releases/tag/v0.1.1)
+- [Ract](https://github.com/Privoce/ract/releases/tag/v0.1.6)
+- [GenUI Builtin Component](https://github.com/Privoce/GenUI-Builtin-Component/releases/tag/v0.2.1)
 - [GenUI Book](https://privoce.github.io/GenUI.github.io)
 
 ## Contact & Feedback

docs/v0.1.0/en/doc/config/env.mdx

@@ -1,4 +1,4 @@
-import { Tab, Tabs } from 'rspress/theme';
+import { Tab, Tabs } from "rspress/theme";
 
 # Env
 
@@ -52,21 +52,22 @@ Take `Ract` installed using `cargo` as an example:
         🔸 env: Set the `path` for the chain env.toml file
         🔸 chain_env_toml: Set the rust dependency for GenUI toolchain
 
-        ? Which env file do you want to config?  
+        ? Which env file do you want to config?
         > env
         chain_env_toml
         # ---
-        ? Get or Set Config?  
+        ? Get or Set Config?
         get
         > set
         ```
     </Tab>
     <Tab label="Manual Configuration">
         You need to find the installation address of ract, for example, if you use `cargo` to install it, the address is: `~/.cargo/bin/.env`
-        ```shell 
+        ```shell
         vim ~/.cargo/bin/.env
         ```
     </Tab>
+
 </Tabs>
 
 ## `env.toml`(chain_env_toml)
@@ -78,16 +79,31 @@ Take `Ract` installed using `cargo` as an example:
 Only `[dependencies]` in the `env.toml` file points to the dependency location
 
 ```toml title="env.toml"
+version = "0.1.6"
+is_latest = true
+auto_update = true
+check = { auto = true, last_time = 1741547846, frequency = 172800 }
+
 [dependencies]
 makepad-widgets = "~/.cargo/bin/chain/makepad"
 gen_components = "~/.cargo/bin/chain/gen_components"
 ```
 
-|key|value type|description|
-|---|-----|---|
-|`makepad-widgets`|`String`|`makepad-widgets` dependency address|
-|`gen_components`|`String`|`gen_components`(GenUI Builtin Components) dependency address|
+| key               | value type | description                                                      |
+| ----------------- | ---------- | ---------------------------------------------------------------- |
+| `version`         | `String`   | `ract` version number                                            |
+| `is_latest`       | `bool`     | Is it the latest version                                         |
+| `auto_update`     | `bool`     | Automatic update                                                 |
+| `check`           | `Check`    | Detection                                                        |
+| `makepad-widgets` | `String`   | Dependency address of `makepad-widgets`                          |
+| `gen_components`  | `String`   | Dependency address of `gen_components`(GenUI Builtin Components) |
+
+| key               | value type | description                                                      |
+| ----------------- | ---------- | ---------------------------------------------------------------- |
+| `auto`            | `bool`     | Automatic detection                                              |
+| `last_time`       | `u64`      | Timestamp of the latest detection (s)                            |
+| `frequency`       | `u64`      | Detection frequency (s)                                          |
 
 ### Set Config
 
-The modification method of `env.toml` is the same as `.env`. You only need to select `chain_env_toml` when `Ract` asks you.
+The modification method of `env.toml` is the same as `.env`. You only need to select `chain_env_toml` when `Ract` asks you.

docs/v0.1.0/en/doc/config/ract_toml.mdx

@@ -32,9 +32,11 @@ import { Tab, Tabs } from "rspress/theme";
 | `target`   | `FrameworkType`       | Project type                                                                 |
 | `members`  | `Option<Vec<Member>>` | Project members                                                              |
 | `compiles` | `Option<Vec<usize>>`  | Projects to be compiled. If not set, compile the first project in the member |
+|`resources`|`Resource`|Package resource pointer|
 
 > - [`FrameworkType`](/doc/config/types#frameworktype)
 > - [`Member`](/doc/config/types#member)
+> - [`Resource`](/doc/config/types#resources)
 
 ### Source Code `.ract`
 
@@ -62,5 +64,6 @@ pub struct RactToml {
     /// - if compiles length is 1, compile the project in the members by index
     /// - if compiles length is more than 1, use multiple threads to compile the projects
     pub compiles: Option<Vec<usize>>,
+    pub resources: Vec<Resource>,
 }
 ````

docs/v0.1.0/en/doc/config/types.mdx

@@ -37,6 +37,24 @@ pub struct Member {
 }
 ```
 
+
+### Resource
+
+- `String`: resource path
+- `Obj`:
+    - `src`: source resource path
+    - `target`: `target path`
+
+#### Source Code
+
+```
+#[derive(Debug, Clone)]
+pub enum Resource {
+    String(String),
+    Obj { src: PathBuf, target: String },
+}
+```
+
 ## `gen_ui.toml`
 
 ### CompilerConf

docs/v0.1.0/en/doc/tutorial/quick-start.mdx

@@ -9,7 +9,7 @@ This is a quick start example, through which you can quickly understand the deve
 | Name | Version |
 | ---- | ------- |
 | Mac  | -       |
-| Ract | 0.1.0+  |
+| Ract | 0.1.6+  |
 
 > [!TIP]
 >
@@ -19,9 +19,9 @@ This is a quick start example, through which you can quickly understand the deve
 
 `Ract` is the first step in your journey to GenUI, please choose the latest version to download
 
-> Releases: https://github.com/Privoce/ract/releases
+> 👍 crates.io: https://crates.io/crates/ract
 >
-> cratio: https://crates.io/crates/ract
+> Releases: https://github.com/Privoce/ract/releases
 
 > [!WARNING]
 >

docs/v0.1.0/en/doc/tutorial/script.mdx

@@ -6,16 +6,53 @@ The script part of `GenUI` uses the Rust language and is wrapped in the `<script
 >
 > This document only briefly describes the use of the script part. For specific documents, please refer to: [API](/zh/api/index)
 
+## Define components
+
+For custom components, we need to use the `#[component]` macro to declare the component's properties, but not all types are allowed. Types that can be used in properties need to implement the `Default` trait.
+Custom structs and enums need to be annotated with `#[prop]`.
+
+```rust
+<script>
+#[component]
+pub struct MyView{
+    name: String
+}
+</script>
+```
+
 ## Define component properties
 
-For custom components, we need to use the `#[prop]` macro to declare the component's properties, but not all types are allowed. The types that can be used in the properties need to implement the `Default` trait.
+When you want to build a custom struct or enum in a component, you need to use `#[prop]` to annotate it and implement the `Default` trait
 
 ```rust
 <script>
-#[prop]
+#[component]
 pub struct MyView{
+    user: User,
+    auth: Auth
+}
+
+#[prop]
+#[derive(Debug, Clone)]
+pub struct User{
     name: String
 }
+
+impl Default for User{
+    fn default() -> Self{
+        Self{ name: "John" }
+    }
+}
+
+#[prop]
+#[derive(Default, Clone, Copy, Debug)]
+pub enum Auth{
+    #[default]
+    Custom,
+    User,
+    Remote,
+    Other
+}
 </script>
 ```
 
@@ -54,25 +91,26 @@ In this example, we define the value of the `text` property of `label` in `MyVie
 </template>
 
 <script>
-#[prop]
+#[component]
 pub struct MyView{
     txt: String
 }
 
-let mut prop = default_prop!{
-    MyView{
-        txt: "Hello".to_string()
+impl Default for MyView{
+    fn default() -> Self{
+        Self{
+            txt: "Hello".to_string()
+        }
     }
-};
+}
 </script>
 ```
 
 In this code, the `get_txt` and `set_txt` methods are automatically generated.
 
 ## Methods and callbacks
 
-For methods and callbacks, use `fn` or `closure` to declare them. In the following example, we define the `change_txt` method as the callback method for button clicks.
-
+Methods and callbacks need to be defined in the component structure using `impl`. In the following example, we define the `change_txt` method as the callback method for button clicks.
 ```rust
 <template>
     <component name="MyView">
@@ -82,27 +120,23 @@ For methods and callbacks, use `fn` or `closure` to declare them. In the followi
 </template>
 
 <script>
-#[prop]
+#[component]
 pub struct MyView{
     txt: String
 }
 
-let mut prop = default_prop!{
-    MyView{
-        txt: "Hello".to_string()
+impl Default for MyView{
+    fn default() -> Self{
+        Self{
+            txt: "Hello".to_string()
+        }
     }
-};
+}
 
-fn change_txt(){
-    prop.set_txt("World".to_string());
+impl MyView{
+    fn change_txt(&mut self){
+        self.set_txt("World".to_string());
+    }
 }
 </script>
-```
-
-The above method can also be rewritten using `closure`
-
-```rust
-let mut change_txt = ||{
-    prop.set_txt("World".to_string());
-};
 ```

docs/v0.1.0/en/doc/tutorial/template/sugar_syntax.mdx

@@ -28,25 +28,31 @@ The followings are details:
 
 ### Examples
 
+> [!DANGER]
+>
+> When using syntax sugar, you need to bind the id just like the bind type
+>
+> We plan to introduce an automatic id strategy in the `v0.1.3` version (automatically generate an id for each component that does not have an id added during static compilation)
+
 #### Single for
 
 ```html
-<label :for="item in label_list" :text="item"></label>
+<label id="mv_label" :for="item in label_list" :text="item"></label>
 ```
 
 #### Nested use
 
 ```html
-<view :for="item in label_list">
-    <label :text="item"></label>
+<view id="my_view" :for="item in label_list">
+    <label id="mv_label" :text="item"></label>
 </view>
 ```
 
 #### Nested for
 
 ```html
-<view :for="(index, item) in label_list">
-    <label :for="item1 in item[index]" :text="item1"></label>
+<view id="mv_view" :for="(index, item) in label_list">
+    <label id="mv_label" :for="item1 in item[index]" :text="item1"></label>
 </view>
 ```
 

docs/v0.1.0/en/doc/tutorial/template/template_type.mdx

@@ -1,12 +1,12 @@
 # Component Type
 
-The component types here only refer to static components and custom components
+The component types here only refer to builtin components and custom components
 
-## Static Components
+## Builtin Components
 
-Static components refer to the underlying components that can be used directly during development without the need for secondary development. These underlying components are provided by [GenUI Builtin Components](/zh/components/index).
+Built-in components refer to the underlying components that can be used directly during development without the need to develop them yourself. These underlying components are provided by [GenUI Builtin Components](/components/index).
 
-All static component properties and callbacks are immutable and have built-in types
+All builtin component properties and callbacks are immutable and have built-in types
 
 ## Custom Components
 
@@ -15,7 +15,7 @@ Custom components refer to components that are secondary developed based on exis
 To put it simply, any component wrapped with `<component name="SpecialName"></component>` is a custom component.
 
 1. The `name` of a custom component indicates the component name when the component is referenced externally
-2. Custom components can also have an `id` attribute. `id` and `name` are independent of each other. For custom components, `id` is only valid internally, and `name` is valid externally. That is: [Inside-outside principle](/zh/doc/tutorial/template/basic#Inside-outside principle)
+2. Custom components can also have an `id` attribute. `id` and `name` are independent of each other. For custom components, `id` is only valid internally, and `name` is valid externally. That is: [Inside-outside principle](/doc/tutorial/template/basic#internal-and-external-principles)
 3. The `<component>` tag has no meaning, it only represents the declaration of the custom component
 4. Custom components inherit the `view` component by default, so the properties of the `view` component can also be used by custom components
 5. Custom components do not inherit the callbacks of the `view` component, only the properties