| value | number | Yes| Current value of the chart, that is, the position to which the pointer points in the chart. It is used as the initial value of the chart when the component is created.|
| min | number | No| Minimum value of the current data segment.<br>Default value: **0**|
| min | number | No| Minimum value of the current data segment.<br>Default value: **0**|
| max | number | No| Maximum value of the current data segment.<br>Default value: **100**|
| max | number | No| Maximum value of the current data segment.<br>Default value: **100**|
## Attributes
## Attributes
In addition to the [universal attributes](ts-universal-attributes-size.md), the following attributes are supported.
| Name| Type| Description|
| Name| Type| Description|
| -------- | -------- | -------- |
| -------- | -------- | -------- |
| value | number | Value of the chart.<br>Default value: **0**|
| value | number | Value of the chart. It can be dynamically changed.<br>Default value: **0**|
| startAngle | number | Start angle of the chart. The value 0 indicates 0 degrees, and a positive value indicates the clockwise direction.<br>Default value: **-150**|
| startAngle | number | Start angle of the chart. The value **0** indicates 0 degrees, and a positive value indicates the clockwise direction.<br>Default value: **0**|
| endAngle | number | End angle of the chart. The value 0 indicates 0 degrees, and a positive value indicates the clockwise direction.<br>Default value: **150**|
| endAngle | number | End angle of the chart. The value **0** indicates 0 degrees, and a positive value indicates the clockwise direction.<br>Default value: **360**|
| colors | Array<ColorStop> | Colors of the chart. Colors can be set for individual segments.|
| colors | Array<[ColorStop](#colorstop)> | Colors of the chart. Colors can be set for individual segments.|
| strokeWidth | [Length](ts-types.md#length) | Stroke width of the chart.|
| strokeWidth | Length | Stroke width of the chart.|
| ColorStop | [[ResourceColor](ts-types.md#resourcecolor8), number] | Type of the gradient stop. The first parameter specifies the color, and the second parameter specifies the offset, which ranges from 0 to 1.|
| ColorStop | [[ResourceColor](ts-types.md#resourcecolor), number] | Type of the gradient stop. The first parameter indicates the color value. If it is set to a non-color value, the black color is used. The second parameter indicates the color weight. If it is set to a negative number or a non-numeric value, the color weight is 0, which means that the color is not displayed.|
## Example
## Example
...
@@ -53,15 +55,30 @@ Describes a gradient stop.
...
@@ -53,15 +55,30 @@ Describes a gradient stop.
@Component
@Component
structGaugeExample{
structGaugeExample{
build(){
build(){
Column(){
Column({space:20}){
Gauge({value:50,min:0,max:100})
// Use the default value of min and max, which is 0-100, and the default values of startAngle and endAngle, which are 0 and 360, respectively.
| src | string\|[PixelMap](../apis/js-apis-image.md#pixelmap7)\|[Resource](ts-types.md#resource) | Yes | - | Image source. Both local and online images are supported.<br>When using resources referenced using a relative path, for example, `Image("common/test.jpg")`, the **\<Image>** component cannot be called across bundles or modules. Therefore, you are advised to use `$r` to reference image resources that need to be used globally.<br>- The following image formats are supported: PNG, JPG, BMP, SVG, GIF.<br>\- Base64 strings are supported. The value format is `data:image/[png\|jpeg\|bmp\|webp];base64,[base64 data]`, where `[base64 data]` is a Base64 string.<br/>\- The value can also be a path starting with `dataability://`, which is used to access the image path provided by a Data ability.<br>\- Strings with the `file:///data/storage` prefix are supported, which are used to read image resources in the` files` folder in the installation directory of the application. Using such strings requires read permission on the files in the installation directory. |
| src | string\|[PixelMap](../apis/js-apis-image.md#pixelmap7)\|[Resource](ts-types.md#resource) | Yes | - | Image source. Both local and online images are supported.<br>When using resources referenced using a relative path, for example, `Image("common/test.jpg")`, the **\<Image>** component cannot be called across bundles or modules. Therefore, you are advised to use `$r` to reference image resources that need to be used globally.<br>- The following image formats are supported: PNG, JPG, BMP, SVG, GIF.<br>\- Base64 strings are supported. The value format is `data:image/[png\|jpeg\|bmp\|webp];base64,[base64 data]`, where `[base64 data]` is a Base64 string.<br/>\- The value can also be a path starting with `dataability://`, which is used to access the image path provided by a Data ability.<br>\- Strings with the `file:///data/storage` prefix are supported, which are used to read image resources in the` files` folder in the installation directory of the application. Using such strings requires the read permission on the files in the installation directory.|
| objectRepeat | [ImageRepeat](ts-appendix-enums.md#imagerepeat) | NoRepeat | Whether the image is repeated.<br>> **NOTE**<br>> This attribute is not applicable to SVG images.|
| objectRepeat | [ImageRepeat](ts-appendix-enums.md#imagerepeat) | NoRepeat | Whether the image is repeated.<br>**NOTE**<br>This attribute is not applicable to SVG images. |
| interpolation | ImageInterpolation | None | Interpolation effect of the image. This attribute is intended to alleviate aliasing that occurs when a low-definition image is zoomed in.<br>> **NOTE**<br>> This attribute is not applicable to SVG images or **PixelMap** objects. |
| interpolation | ImageInterpolation | None | Interpolation effect of the image. This attribute is intended to alleviate aliasing that occurs when a low-definition image is zoomed in.<br>**NOTE**<br>This attribute is not applicable to SVG images or **PixelMap** objects. |
| renderMode | ImageRenderMode | Original | Rendering mode of the image.<br>> **NOTE**<br>> This attribute is not applicable to SVG images.|
| renderMode | ImageRenderMode | Original | Rendering mode of the image.<br>**NOTE**<br>This attribute is not applicable to SVG images. |
| sourceSize | {<br>width: number,<br>height: number<br>} | - | Decoding size of the image. The original image is decoded into an image of the specified size. If the value is of the number type, the unit px is used.<br>> **NOTE**<br>> This attribute is not applicable to **PixelMap** objects.|
| sourceSize | {<br>width: number,<br>height: number<br>} | - | Decoding size of the image. The original image is decoded into an image of the specified size. If the value is of the number type, the unit px is used.<br>**NOTE**<br>This attribute is not applicable to **PixelMap** objects. |
| matchTextDirection | boolean | false | Whether to display the image in the system language direction. When this parameter is set to true, the image is horizontally flipped in the right-to-left (RTL) language context. |
| matchTextDirection | boolean | false | Whether to display the image in the system language direction. When this parameter is set to true, the image is horizontally flipped in the right-to-left (RTL) language context. |
| fitOriginalSize | boolean | true | Whether to fit the component to the original size of the image source when the component size is not set. |
| fitOriginalSize | boolean | true | Whether to fit the component to the original size of the image source when the component size is not set. |
| fillColor | [ResourceColor](ts-types.md#resourcecolor8) | - | Fill color of the image. This attribute only applies to an SVG image. Once set, the fill color will replace that of the SVG image. |
| fillColor | [ResourceColor](ts-types.md#resourcecolor8) | - | Fill color of the image. This attribute only applies to an SVG image. Once set, the fill color will replace that of the SVG image. |
Cascading Style Sheets (CSS) is a language used to describe the HML page structure. All HML components have default styles. You can customize styles for these components using CSS to design various pages. For details, see [Universal Styles](../reference/arkui-js/js-components-common-styles.md).
Cascading Style Sheets (CSS) is a language used to describe the HML page structure. All HML components have default styles. You can customize styles for these components using CSS to design various pages. For details, see [Universal Styles](../reference/arkui-js/js-components-common-styles.md).
## Size Unit
## Size Unit
- Logical px set by \<length>:
- Logical px set by **\<length>**:
- The default logical screen width is 720 px (for details, see the "window" section in [config.json](js-framework-js-tag.md)). Your page will be scaled to fit the actual width of the screen. For example, on a screen with the actual width of 1440 physical px, 100 px is displayed on 200 physical px, with all sizes doubled from 720 px to 1440 px.
- If you set autoDesignWidth to true (for details, see the "window" section in [config.json](js-framework-js-tag.md)), the logical px are scaled based on the screen density. For example, if the screen density is 3x, 100 px will be rendered on 300 physical px. This approach is recommended when your application needs to adapt to multiple devices.
- The default logical screen width is 720 px (for details, see the **"window"** section in **[config.json](js-framework-js-tag.md)**). Your page will be scaled to fit the actual width of the screen. For example, on a screen with the actual width of 1440 physical px, 100 px is displayed on 200 physical px, with all sizes doubled from 720 px to 1440 px.
- If you set **autoDesignWidth** to **true** (for details, see the **"window"** section in **[config.json](js-framework-js-tag.md)**), the logical px are scaled based on the screen density. For example, if the screen density is 3x, 100 px will be rendered on 300 physical px. This approach is recommended when your application needs to adapt to multiple devices.
- Percentage set by <percentage>: The component size is represented by its percentage of the parent component size. For example, if the width <percentage> of a component is set to 50%, the width of the component is half of its parent component's width.
- Percentage set by **\<percentage>**: The component size is represented by its percentage of the parent component size. For example, if the width **\<percentage>** of a component is set to **50%**, the width of the component is half of its parent component's width.
## Style Import
## Style Import
CSS files can be imported using the @import statement. This facilitates module management and code reuse.
CSS files can be imported using the **@import** statement. This facilitates module management and code reuse.
## Style Declaration
## Style Declaration
The .css file with the same name as the .hml file in each page directory describes the styles of components on the HML page, determining how the components will be displayed.
The **.css** file with the same name as the **.hml** file in each page directory describes the styles of components on the HML page, determining how the components will be displayed.
1. Internal style: The style and class attributes can be used to specify the component style. Example:
1. Internal style: The **style** and **class** attributes can be used to specify the component style. Example:
```html
```html
<!-- index.hml -->
<!-- index.hml -->
<divclass="container">
<divclass="container">
...
@@ -30,7 +29,6 @@ The .css file with the same name as the .hml file in each page directory describ
...
@@ -30,7 +29,6 @@ The .css file with the same name as the .hml file in each page directory describ
</div>
</div>
```
```
```css
```css
/* index.css */
/* index.css */
.container{
.container{
...
@@ -38,8 +36,7 @@ The .css file with the same name as the .hml file in each page directory describ
...
@@ -38,8 +36,7 @@ The .css file with the same name as the .hml file in each page directory describ
}
}
```
```
2. External style files: You need to import the files. For example, create a style.css file in the common directory and import the file at the beginning of index.css.
2. External style files: You need to import the files. For example, create a **style.css** file in the **common** directory and import the file at the beginning of **index.css**.
```css
```css
/* style.css */
/* style.css */
.title{
.title{
...
@@ -47,7 +44,6 @@ The .css file with the same name as the .hml file in each page directory describ
...
@@ -47,7 +44,6 @@ The .css file with the same name as the .hml file in each page directory describ
}
}
```
```
```css
```css
/* index.css */
/* index.css */
@import'../../common/style.css';
@import'../../common/style.css';
...
@@ -61,19 +57,18 @@ The .css file with the same name as the .hml file in each page directory describ
...
@@ -61,19 +57,18 @@ The .css file with the same name as the .hml file in each page directory describ
A CSS selector is used to select elements for which styles need to be added to. The following table lists the supported selectors.
A CSS selector is used to select elements for which styles need to be added to. The following table lists the supported selectors.
| .class | .container | Selects all components whose class is container. |
| .class | .container | Selects all components whose **class** is **container**. |
| \#id | \#titleId | Selects all components whose id is titleId. |
| \#id | \#titleId | Selects all components whose **id** is **titleId**. |
| tag | text | Selects all <text> components. |
| tag | text | Selects all **\<text>** components. |
| , | .title, .content | Selects all components whose class is title or content. |
| , | .title, .content | Selects all components whose **class** is **title** or **content**. |
| \#id .class tag | \#containerId .content text | Selects all grandchild **\<text>** components whose grandparent components are identified as containerId and whose parent components are of the content class. To select child components, use > to replace the space between **\#id** and **.class**, for example, **\#containerId>.content**. |
| \#id .class tag | \#containerId .content text | Selects all grandchild **\<text>** components whose grandparent components are identified as **containerId** and whose parent components are of the **content** class. To select child components, use **>** to replace the space between **\#id** and **.class**, for example, **\#containerId>.content**.|
The following is an example:
Example:
```html
```html
<!-- Page layoutxxx.hml -->
<!-- Pagelayoutexample.hml -->
<divid="containerId"class="container">
<divid="containerId"class="container">
<textid="titleId"class="title">Title</text>
<textid="titleId"class="title">Title</text>
<divclass="content">
<divclass="content">
...
@@ -82,18 +77,17 @@ The following is an example:
...
@@ -82,18 +77,17 @@ The following is an example:
</div>
</div>
```
```
```css
```css
/* Page style xxx.css */
/* Pagestyleexample.css */
/* Set the style for all <div> components. */
/* Set the style for all <div> components. */
div{
div{
flex-direction:column;
flex-direction:column;
}
}
/* Set the style for the component whose class is title.*/
/* Set the style for the components whose class is title. */
.title{
.title{
font-size:30px;
font-size:30px;
}
}
/* Set the style for the component whose id is contentId. */
/* Set the style for the components whose id is contentId. */
#contentId{
#contentId{
font-size:20px;
font-size:20px;
}
}
...
@@ -101,11 +95,11 @@ div {
...
@@ -101,11 +95,11 @@ div {
.title,.content{
.title,.content{
padding:5px;
padding:5px;
}
}
/* Set the style for all texts of components whose class is container.*/
/* Set the style for all texts of components whose class is container.*/
.containertext{
.containertext{
color:\#007dff;
color:#007dff;
}
}
/* Set the style for direct descendant texts of components whose class is container.*/
/* Set the style for direct descendant texts of components whose class is container.*/
.container>text{
.container>text{
color:#fa2a2d;
color:#fa2a2d;
}
}
...
@@ -115,31 +109,29 @@ The above style works as follows:
...
@@ -115,31 +109,29 @@ The above style works as follows:
In the preceding example, .container text sets title and content to blue, and .container > text sets title to red. The two styles have the same priority, but .container > text declares the style later and overwrites the former style. (For details about the priority, see [Selector Specificity](#selector-specificity).)
In the preceding example, **.container text** sets title and content to blue, and **.container > text** sets title to red. The two styles have the same priority, but **.container > text** declares the style later and overwrites the former style. For details about the priority, see [Selector Specificity](#selector-specificity).
## Selector Specificity
## Selector Specificity
The specificity rule of the selectors complies with the W3C rule, which is only available for inline styles, id, class, tag, grandchild components, and child components. (Inline styles are those declared in the style attribute.)
The specificity rule of the selectors complies with the W3C rule, which is only available for inline styles, **id**, **class**, **tag**, grandchild components, and child components. (Inline styles are those declared in the **style** attribute.)
When multiple selectors point to the same element, their priorities are as follows (in descending order): inline style > id > class > tag.
When multiple selectors point to the same element, their priorities are as follows (in descending order): inline style > **id** > **class** > **tag**.
## Pseudo-classes
## Pseudo-classes
A CSS pseudo-class is a keyword added to a selector that specifies a special state of the selected element(s). For example, :disabled can be used to select the element whose disabled attribute is true.
A CSS pseudo-class is a keyword added to a selector that specifies a special state of the selected elements. For example, **:disabled** can be used to select the element whose **disabled** attribute is **true**.
In addition to a single pseudo-class, a combination of pseudo-classes is supported. For example, :focus:checked selects the element whose focus and checked attributes are both set to true. The following table lists the supported single pseudo-class in descending order of priority.
| Pseudo-class | Available Components | Description |
In addition to a single pseudo-class, a combination of pseudo-classes is supported. For example, **:focus:checked** selects the element whose **focus** and **checked** attributes are both set to **true**. The following table lists the supported single pseudo-class in descending order of priority.
| -------- | -------- | -------- |
| :disabled | Components that support the disabled attribute | Selects the element whose disabled attribute is changed to true (unavailable for animation attributes). |
| :active | Components that support the click event | Selects the element activated by a user. For example, a pressed button or a selected tab-bar (unavailable for animation attributes). |
| :waiting | button | Selects the element whose waiting attribute is true (unavailable for animation attributes). |
| :checked | input[type="checkbox", type="radio"], and switch | Selects the element whose checked attribute is true (unavailable for animation attributes). |
The following is an example for you to use the **:active** pseudo-class to control the style when a user presses the button.
| Pseudo-class | Available Components | Description |
| :disabled | Components that support the **disabled** attribute | Selects the element whose **disabled** attribute is changed to **true** (unavailable for animation attributes). |
| :active | Components that support the click event<br> | Selects the element activated by a user. For example, a pressed button or a selected **tab-bar** (unavailable for animation attributes).|
| :waiting | button | Selects the element whose **waiting** attribute is **true** (unavailable for animation attributes). |
| :checked | input[type="checkbox", type="radio"], switch| Selects the element whose **checked** attribute is **true** (unavailable for animation attributes). |
The following is an example for you to use the **:active** pseudo-class to control the style when a user presses the button.
```html
```html
<!-- index.hml -->
<!-- index.hml -->
...
@@ -151,32 +143,30 @@ The following is an example for you to use the **:active** pseudo-class to contr
...
@@ -151,32 +143,30 @@ The following is an example for you to use the **:active** pseudo-class to contr
```css
```css
/* index.css */
/* index.css */
.button:active{
.button:active{
background-color:#888888;/* After the button is activated, the background color is changed to #888888. */
background-color:#888888;/* After the button is activated, the background color is changed to #888888. */
}
}
```
```
> **NOTE**
> **NOTE**
>
>
> Pseudo-classes are not supported for the **\<popup>** component and its child components, including **\<popup>**, **\<dialog>**, **\<menu>**, **\<option>**, and **\<picker>**.
> Pseudo-classes are not supported for the **\<popup>** component and its child components, including, **\<dialog>**, **\<menu>**, **\<option>**, and **\<picker>**.
## Precompiled Styles
## Precompiled Styles
Precompilation is a program that uses specific syntax to generate CSS files. It provides variables and calculation, helping you define component styles more conveniently. Currently, Less, Sass, and Scss are supported. To use precompiled styles, change the suffix of the original .css file. For example, change **index.css** to **index.less**, **index.sass**, or **index.scss**.
Precompilation is a program that uses specific syntax to generate CSS files. It provides variables and calculation, helping you define component styles more conveniently. Currently, Less, Sass, and Scss are supported. To use precompiled styles, change the suffix of the original **.css** file. For example, change **index.css** to **index.less**, **index.sass**, or **index.scss**.
- The following index.less file is changed from index.css.
- The following **index.less** file is changed from **index.css**.
```less
```less
/* index.less */
/* index.less */
/* Define a variable. */
/* Define a variable. */
@colorBackground: #000000;
@colorBackground: #000000;
.container {
.container {
background-color: @colorBackground; /* Use the variable defined in the .less file. */
background-color: @colorBackground; /* Use the variable defined in the .less file. */
}
}
```
```
- Reference a precompiled style file. For example, if the **style.scss** file is located in the common directory, change the original index.css file to **index.scss** and import **style.scss**.
- Reference a precompiled style file. For example, if the **style.scss** file is located in the **common** directory, change the original **index.css** file to **index.scss** and import **style.scss**.
```scss
```scss
/* style.scss */
/* style.scss */
/* Define a variable. */
/* Define a variable. */
...
@@ -185,20 +175,18 @@ Precompilation is a program that uses specific syntax to generate CSS files. It
...
@@ -185,20 +175,18 @@ Precompilation is a program that uses specific syntax to generate CSS files. It
Reference the precompiled style file in **index.scss**:
Reference the precompiled style file in **index.scss**:
```scss
```scss
/* index.scss */
/* index.scss */
/* Import style.scss. */
/* Import style.scss. */
@import'../../common/style.scss';
@import'../../common/style.scss';
.container{
.container{
background-color:$colorBackground;/* Use the variable defined in style.scss. */
background-color:$colorBackground;/* Use the variable defined in style.scss. */
}
}
```
```
> **NOTE**
> **NOTE**
>
>
> Place precompiled style files in the common directory.
> Place precompiled style files in the **common** directory.
The TypeScript-based declarative development paradigm provides a wide array of basic components, which can be combined and extended in a declarative manner to describe the UI of an application. It also provides basic data binding and event processing mechanisms to help you implement the application interaction logic.
The eTS-based declarative development paradigm provides a wide array of basic components, which can be combined and extended in a declarative manner to describe the UI of an application. It also provides basic data binding and event processing mechanisms to help you implement the application interaction logic.
## HelloWorld Example
## HelloWorld Example
...
@@ -23,7 +23,7 @@ struct Hello {
...
@@ -23,7 +23,7 @@ struct Hello {
Button() {
Button() {
Text('Click me')
Text('Click me')
.fontColor(Color.Red)
.fontColor(Color.Red)
}.onClick(() => {
}.onClick(() => {
this.myText = 'UI'
this.myText = 'UI'
})
})
.width(500)
.width(500)
...
@@ -38,14 +38,14 @@ struct Hello {
...
@@ -38,14 +38,14 @@ struct Hello {
The preceding sample code shows the structure of a simple page. It involves the following basic concepts:
The preceding sample code shows the structure of a simple page. It involves the following basic concepts:
- Decorator: a special kind of declaration that can be applied to classes, structures, methods, and variables. In the sample code, @Entry, @Component, and @State are decorators.
- Decorator: a special kind of declaration that can be applied to classes, structures, methods, and variables. In the sample code, **@Entry**, **@Component**, and **@State** are decorators.
- Custom component: a reusable UI unit, which can be combined with other components. In the sample code, struct Hello decorated by @Component is a custom component.
- Custom component: a reusable UI unit, which can be combined with other components. In the sample code, struct Hello decorated by **@Component** is a custom component.
- UI description: declaratively describes the UI structure. In the sample code, the block of code in the build() method provides the UI description.
- UI description: declaratively describes the UI structure. In the sample code, the block of code in the build() method provides the UI description.
- Built-in component: the default basic or layout component preset in the framework. You can directly invoke these components, such as <Column>, <Text>, <Divider>, and <Button> components in the sample code.
- Built-in component: the default basic or layout component preset in the framework. You can directly invoke these components, such as **\<Column>**, **\<Text>**, **\<Divider>**, and **\<Button>** components in the sample code.
- Attribute method: a method used to configure component attributes, such as fontSize(), width(), height(), and color().
- Attribute method: a method used to configure component attributes, such as **fontSize()**, **width()**, **height()**, and **color()**.
- Event method: a method used to add the component response logic to an event. In the sample code, the onClick method is added for the Button component for defining the click response logic.
- Event method: a method used to add the component response logic to an event. In the sample code, the **onClick** method is added for the Button component for defining the click response logic.
The ArkUI that uses the JavaScript-based web-like development paradigm supports custom components for you to extend existing components. You can encapsulate custom private attributes and events into new components to reuse them multiple times in your project. This also improves code readability. The following is an example:
The ArkUI that uses the JavaScript-compatible web-like development paradigm supports custom components for you to extend existing components. You can encapsulate custom private attributes and events into new components to reuse them multiple times in your project. This also improves code readability. The following is an example:
- Building a custom component
- Building a custom component
```
```html
<!-- comp.hml -->
<!-- comp.hml -->
<divclass="item">
<divclass="item">
<textclass="title-style">{{title}}</text>
<textclass="title-style">{{title}}</text>
...
@@ -15,8 +15,7 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
...
@@ -15,8 +15,7 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
</div>
</div>
```
```
```css
```
/* comp.css */
/* comp.css */
.item{
.item{
width:700px;
width:700px;
...
@@ -40,8 +39,7 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
...
@@ -40,8 +39,7 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
}
}
```
```
```js
```
// comp.js
// comp.js
exportdefault{
exportdefault{
props:{
props:{
...
@@ -64,7 +62,7 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
...
@@ -64,7 +62,7 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
@@ -73,8 +71,7 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
...
@@ -73,8 +71,7 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
</div>
</div>
```
```
```css
```
/* xxx.css */
/* xxx.css */
.container{
.container{
background-color:#f8f8ff;
background-color:#f8f8ff;
...
@@ -84,8 +81,7 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
...
@@ -84,8 +81,7 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
}
}
```
```
```js
```
// xxx.js
// xxx.js
exportdefault{
exportdefault{
data:{
data:{
...
@@ -101,6 +97,6 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
...
@@ -101,6 +97,6 @@ The ArkUI that uses the JavaScript-based web-like development paradigm supports
In this example, the parent component passes the customized attribute through title to the child component, and the child component receives the attribute value in props. The child component passes text to the parent through the bound event, and the passed value is obtained via e.detail. To successfully bind the child component event to the parent component, ensure that the event name meet the requirements for event binding. For details, see [Basic Usage of Custom Components](../reference/arkui-js/js-components-custom-basic-usage.md). The following figures show how the custom component works.
In this example, the parent component passes the customized attribute through title to the child component, and the child component receives the attribute value in props. The child component passes text to the parent through the bound event, and the passed value is obtained via e.detail. To successfully bind the child component event to the parent component, ensure that the event name meet the requirements for event binding. For details, see [Basic Usage of Custom Components](../reference/arkui-js/js-components-custom-basic-usage.md). The following figures show how the custom component works.
The TypeScript-based declarative development paradigm of ArkUI is a simplified, high-performance UI development framework for cross-device applications.
The eTS-based declarative development paradigm of ArkUI is a simplified, high-performance UI development framework for cross-device applications.
## Basic Capabilities
## Basic Capabilities
In ArkUI that uses the TypeScript-based declarative development paradigm, the programming mode is closer to natural semantics. You can intuitively describe the UI without caring about how the framework implements UI drawing and rendering, leading to simplified and efficient development. The UI capabilities are provided from three dimensions: component, animation, and state management. System capability APIs are also provided to allow for effortless invocation of system capabilities.
In ArkUI that uses the eTS-based declarative development paradigm, the programming mode is closer to natural semantics. You can intuitively describe the UI without caring about how the framework implements UI drawing and rendering, leading to simplified and efficient development. The UI capabilities are provided from three dimensions: component, animation, and state management. System capability APIs are also provided to allow for effortless invocation of system capabilities.
For details about the UI components, see [Component Reference (TypeScript-based Declarative Development Paradigm)](../reference/arkui-ts/ts-universal-events-click.md).
For details about the UI components, see [Component Reference (eTS-based Declarative Development Paradigm)](../reference/arkui-ts/ts-universal-events-click.md).
- Out-of-the-box components
- Out-of-the-box components
...
@@ -39,20 +39,20 @@ For details about the UI components, see [Component Reference (TypeScript-based
...
@@ -39,20 +39,20 @@ For details about the UI components, see [Component Reference (TypeScript-based
- Declarative UI frontend
- Declarative UI frontend
Provides basic language specifications of the UI development paradigm, built-in UI components, layouts, and animations, and multiple state management mechanisms, with a wide array of APIs for you to call as required.
Provides basic language specifications of the UI development paradigm, built-in UI components, layouts, and animations, and multiple state management mechanisms, with a wide array of APIs for you to call as required.
- Language runtime
- Language runtime
Provides the parsing capability for the UI paradigm syntax and allows for cross-language API calls for a high-performance running environment of the TS language.
Provides the parsing capability for the UI paradigm syntax and allows for cross-language API calls for a high-performance running environment of the eTS language.
- Declarative UI backend engine
- Declarative UI backend engine
Provides UI rendering pipelines that are compatible with different development paradigms, multiple basic components, layout calculation, dynamic effects, and interaction events, with state management and drawing capabilities.
Provides UI rendering pipelines that are compatible with different development paradigms, multiple basic components, layout calculation, dynamic effects, and interaction events, with state management and drawing capabilities.
- Render engine
- Render engine
Provides efficient drawing capabilities, which enable rendering instructions collected by the rendering pipeline to be drawn to the screen.
Provides efficient drawing capabilities, which enable rendering instructions collected by the rendering pipeline to be drawn to the screen.
- Porting layer
- Porting layer
Provides abstract APIs to connect to different systems, such as system rendering pipelines and lifecycle scheduling.
Provides abstract APIs to connect to different systems, such as system rendering pipelines and lifecycle scheduling.
