context-userguide.md 8.1 KB
Newer Older
W
wusongqing 已提交
1 2 3 4
# Context Usage

## Context Overview

W
wusongqing 已提交
5
**Context** provides the capability of obtaining contextual information of an application.
W
wusongqing 已提交
6

W
wusongqing 已提交
7
The OpenHarmony application framework has two models: Feature Ability (FA) model and stage model. Correspondingly, there are two sets of context mechanisms. **application/BaseContext** is a common context base class. It uses the **stageMode** attribute to specify whether the context is used for the stage model.
W
wusongqing 已提交
8

W
wusongqing 已提交
9
- FA Model
W
wusongqing 已提交
10

W
wusongqing 已提交
11
  Only the methods in **app/Context** can be used for the context in the FA model. Both the application-level context and ability-level context are instances of this type. If an ability-level method is invoked in the application-level context, an error occurs. Therefore, you must pay attention to the actual meaning of the **Context** instance.
W
wusongqing 已提交
12

W
wusongqing 已提交
13
- Stage Model
W
wusongqing 已提交
14

W
wusongqing 已提交
15
  The stage model has the following types of contexts: **application/Context**, **application/ApplicationContext**, **application/AbilityStageContext**, **application/ExtensionContext**, **application/AbilityContext**, and **application/FormExtensionContext**. For details about these contexts and how to use them, see [Context in the Stage Model](#context-in-the-stage-model).
W
wusongqing 已提交
16 17 18 19 20 21 22 23 24

![contextIntroduction](figures/contextIntroduction.png)

## Context in the FA Model

Only the methods in **app/Context** can be used for the context in the FA model.

The FA model has only one context definition. All capabilities in the context are provided through methods. The context uses these methods to extend the capabilities of the FA.

W
wusongqing 已提交
25
**d.ts statement**
W
wusongqing 已提交
26 27 28

https://gitee.com/openharmony/interface_sdk-js/blob/master/api/app/context.d.ts

W
wusongqing 已提交
29
**Example**
W
wusongqing 已提交
30 31 32 33 34

```javascript
import featureAbility from '@ohos.ability.featureAbility'
export default {
  onCreate() {
W
wusongqing 已提交
35
    // Obtain the context and call related APIs.
W
wusongqing 已提交
36
    let context = featureAbility.getContext();
W
wusongqing 已提交
37 38
    context.getBundleName((data, bundleName)=>{
      console.info("ability bundleName:" + bundleName)
W
wusongqing 已提交
39
    });
W
wusongqing 已提交
40
    console.info('Application onCreate')
W
wusongqing 已提交
41 42
  },
  onDestroy() {
W
wusongqing 已提交
43
    console.info('Application onDestroy')
W
wusongqing 已提交
44 45 46 47 48 49
  },
}
```

## Context in the Stage Model

W
wusongqing 已提交
50
The following describes the contexts provided by the stage model in detail.
W
wusongqing 已提交
51 52 53

### application/Context

W
wusongqing 已提交
54 55 56 57 58 59 60
**application/Context** is the base class context that provides basic application information such as **resourceManager**, **applicationInfo**, **cacheDir**, and **area**. It also provides basic application methods such as **createBundleContext**.

**d.ts statement**

https://gitee.com/openharmony/interface_sdk-js/blob/master/api/application/Context.d.ts

### application/ApplicationContext
W
wusongqing 已提交
61

W
wusongqing 已提交
62
**application/ApplicationContext** is an application-level context. In addition to the capabilities provided by the base class context, the application-level context provides **registerAbilityLifecycleCallback** and **unregisterAbilityLifecycleCallback** to monitor the ability lifecycle in a process.
W
wusongqing 已提交
63 64 65

**How to Obtain**

W
wusongqing 已提交
66
Obtain the context by calling **context.getApplicationContext()** in **Ability**.
W
wusongqing 已提交
67 68 69 70

**Example**

```javascript
W
wusongqing 已提交
71
import AbilityStage from "@ohos.application.AbilityStage";
W
wusongqing 已提交
72

W
wusongqing 已提交
73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112
var lifecycleid;

export default class MyAbilityStage extends AbilityStage {
    onCreate() {
        console.log("MyAbilityStage onCreate")
        let AbilityLifecycleCallback  =  {
            onAbilityCreate(ability){
                console.log("AbilityLifecycleCallback onAbilityCreate ability:" + JSON.stringify(ability));        
            },
            onAbilityWindowStageCreate(ability){
                console.log("AbilityLifecycleCallback onAbilityWindowStageCreate ability:" + JSON.stringify(ability));           
            },
            onAbilityWindowStageDestroy(ability){
                console.log("AbilityLifecycleCallback onAbilityWindowStageDestroy ability:" + JSON.stringify(ability));
            },
            onAbilityDestroy(ability){
                console.log("AbilityLifecycleCallback onAbilityDestroy ability:" + JSON.stringify(ability));             
            },
            onAbilityForeground(ability){
                console.log("AbilityLifecycleCallback onAbilityForeground ability:" + JSON.stringify(ability));             
            },
            onAbilityBackground(ability){
                console.log("AbilityLifecycleCallback onAbilityBackground ability:" + JSON.stringify(ability));              
            },
            onAbilityContinue(ability){
                console.log("AbilityLifecycleCallback onAbilityContinue ability:" + JSON.stringify(ability));
            }
        }
        // 1. Obtain applicationContext through the context attribute.
        let applicationContext = this.context.getApplicationContext();
        // 2. Use applicationContext to register and listen for the ability lifecycle in the application.
        lifecycleid = applicationContext.registerAbilityLifecycleCallback(AbilityLifecycleCallback);
        console.log("registerAbilityLifecycleCallback number: " + JSON.stringify(lifecycleid));       
    }
    onDestroy() {
        let applicationContext = this.context.getApplicationContext();
        applicationContext.unregisterAbilityLifecycleCallback(lifecycleid, (error, data) => {
        console.log("unregisterAbilityLifecycleCallback success, err: " + JSON.stringify(error));
        });
    }
W
wusongqing 已提交
113 114 115 116 117
}
```

**d.ts statement**

W
wusongqing 已提交
118
https://gitee.com/openharmony/interface_sdk-js/blob/master/api/application/ApplicationContext.d.ts
W
wusongqing 已提交
119 120 121 122 123 124 125 126 127 128 129 130 131 132 133

### application/AbilityStageContext

**application/AbilityStageContext** is the context for the HAP file. In addition to those provided by the base class **application/Context**, this context contains **HapModuleInfo** and **Configuration**.

**How to Obtain**

Obtain the context from the **context** attribute in **AbilityStage**.

**Example**

```javascript
export default class MyAbilityStage extends AbilityStage {
  onCreate() {
    // The context attribute is of the AbilityStageContext type.
W
wusongqing 已提交
134
    console.log('HapModuleInfo is ' + this.context.currentHapModuleInfo);
W
wusongqing 已提交
135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155
  }
}
```

**d.ts statement**

https://gitee.com/openharmony/interface_sdk-js/blob/master/api/application/AbilityStageContext.d.ts

### application/AbilityContext

In the stage model, each ability has a context attribute.

**Ability** provides methods to manage the ability lifecycle, and **AbilityContext** provides methods to operate abilities (such as **startAbility** and **connectAbility**).

**How to Obtain**

Obtain the context from the **context** attribute in **Ability**.

**Example**

```javascript
W
wusongqing 已提交
156 157
import Ability from '@ohos.application.Ability'

W
wusongqing 已提交
158
export default class MainAbility extends Ability {
W
wusongqing 已提交
159 160 161
    onCreate(want, launchParam) {
        console.log("[Demo] MainAbility onCreate")
        globalThis.abilityWant = want;
W
wusongqing 已提交
162 163
    }

W
wusongqing 已提交
164 165 166
    onDestroy() {
        console.log("[Demo] MainAbility onDestroy")
    }
W
wusongqing 已提交
167

W
wusongqing 已提交
168 169 170
    onWindowStageCreate(windowStage) {
        // Set the main page for this ability when the main window is created.
        console.log("[Demo] MainAbility onWindowStageCreate")
W
wusongqing 已提交
171

W
wusongqing 已提交
172 173 174
        // Obtain AbilityContext and print the ability information.
        let context = this.context;
        console.log("[Demo] MainAbility bundleName " + context.abilityInfo.bundleName)
W
wusongqing 已提交
175

W
wusongqing 已提交
176 177
        windowStage.setUIContent(this.context, "pages/index", null)
    }
W
wusongqing 已提交
178

W
wusongqing 已提交
179 180 181 182
    onWindowStageDestroy() {
        // Release the UI related resources when the main window is destroyed.
        console.log("[Demo] MainAbility onWindowStageDestroy")
    }
W
wusongqing 已提交
183

W
wusongqing 已提交
184 185 186 187
    onForeground() {
        // The ability is switched to run in the foreground.
        console.log("[Demo] MainAbility onForeground")
    }
W
wusongqing 已提交
188

W
wusongqing 已提交
189 190 191 192 193
    onBackground() {
        // The ability is switched to run in the background.
        console.log("[Demo] MainAbility onBackground")
    }
};
W
wusongqing 已提交
194 195 196 197
```

### application/FormExtensionContext

W
wusongqing 已提交
198
For details, see [FormExtensionContext](../reference/apis/js-apis-formextensioncontext.md).
W
wusongqing 已提交
199

W
wusongqing 已提交
200
## Common Incorrect Usage
W
wusongqing 已提交
201

W
wusongqing 已提交
202
**Error 1: Use globalThis to obtain the context in the stage model.**
W
wusongqing 已提交
203 204 205 206

**Reason**

In the FA model, each ability instance has a JS VM instance. Therefore, a global ability instance can be obtained from the **global** object of the JS engine. In the stage model, where all the processes of an application share a JS VM instance, there is no global ability instance, and using **globalThis** may cause an error or crash.