delete xiaomi quick game (#3299)

Author: tangkaikk

versions/2.4/en/SUMMARY.md

@@ -105,7 +105,6 @@
     - [Publish to OPPO Mini Games](publish/publish-oppo-instant-games.md)
     - [Publish to vivo Mini Games](publish/publish-vivo-instant-games.md)
     - [Publish to Honor Mini Games](publish/publish-honor-mini-game.md)
-    - [Publish to Xiaomi Quick Games](publish/publish-xiaomi-quick-games.md)
     - [Publish to Baidu Mini Games](publish/publish-baidugame.md)
         - [Baidu Open Data Context](publish/publish-baidugame-sub-domain.md)
     - [Publish to WeChat Mini Games](publish/publish-wechatgame.md)

versions/2.4/en/asset-workflow/compress-texture.md

@@ -50,7 +50,6 @@ In addition to `JPG` and `PNG` which are supported across all platforms, the sup
 | OPPO Mini Game | ETC1 |
 | vivo Mini Game | ETC1 / ASTC |
 | Huawei Quick Game | ETC1 |
-| Xiaomi Quick Game | ETC1 |
 | iOS | ASTC / ETC1 / ETC2 / PVR / WEBP |
 | Android / Huawei AGC | ASTC / ETC1 / ETC2 / WEBP |
 

versions/2.4/en/index.md

@@ -27,7 +27,7 @@ After years of rapid development, there are significant differences in usage bet
 - [DragonBones ReplaceTexture](components/dragonbones.md).
 - **As of v2.1.4**, Cocos Creator supports publishing to [Alipay Mini Games](publish/publish-alipay-mini-games.md).
 - **As of v2.1**, Cocos Creator introduced 3D support. Please refer to [v2.1.0 Release Notes](release-notes/upgrade-guide-v2.1.md).
-- **As of v2.0.10**, Cocos Creator supports publishing to [Xiaomi Quick Games](publish/publish-xiaomi-quick-games.md) and [Cocos Play](publish/publish-cocosplay.md).
+- **As of v2.0.10**, Cocos Creator supports publishing to [Cocos Play](publish/publish-cocosplay.md).
 - **As of v2.0.7**, Cocos Creator supports publishing to [Huawei Quick Games](publish/publish-huawei-quick-games.md).
 - **As of v2.0.5**, Cocos Creator supports publishing to [OPPO Mini Games](publish/publish-oppo-instant-games.md) and [vivo Mini Games](publish/publish-vivo-instant-games.md).
 - **As of v2.0.4**, Cocos Creator supports publishing to [Google Play Instant](publish/publish-android-instant.md).

versions/2.4/en/publish/index.md

@@ -14,7 +14,6 @@
 - [Publish to OPPO Mini Games](publish-oppo-instant-games.md)
 - [Publish to vivo Mini Games](publish-vivo-instant-games.md)
 - [Publish to Honor Mini Games](publish-honor-mini-game.md)
-- [Publish to Xiaomi Quick Games](publish-xiaomi-quick-games.md)
 - [Publish to Baidu Mini Games](publish-baidugame.md)
     - [Baidu Open Data Context](publish-baidugame-sub-domain.md)
 - [Publish to WeChat Mini Games](publish-wechatgame.md)

versions/2.4/en/publish/publish-in-command-line.md

@@ -39,7 +39,7 @@ You can also to compile the native project of the native platform separately by
 
   - `excludedModules`: The modules need remove from engine. Engine modules can find from [here](https://github.com/holycanvas/engine/blob/76460006e5046475cb714c48f801af8ea6a4fac9/modules.json)
   - `title` - Project title
-  - `platform` - Publish platform [web-mobile, web-desktop, android, win32, ios, mac, wechatgame, wechatgame-subcontext, baidugame, baidugame-subcontext, xiaomi, alipay, qgame, quickgame, huawei, cocosplay, fb-instant-games, android-instant]
+  - `platform` - Publish platform [web-mobile, web-desktop, android, win32, ios, mac, wechatgame, wechatgame-subcontext, baidugame, baidugame-subcontext, alipay, qgame, quickgame, huawei, cocosplay, fb-instant-games, android-instant]
   - `buildPath` - Publish path
   - `startScene` - Start scene uuid
   - `debug` - Whether or not debug mode

versions/2.4/en/publish/publish-xiaomi-quick-games.md

@@ -13,7 +13,7 @@ This option is only related to the script, specific aspects of the impact, most
 | :---------- | :----------- | :----------- |
 | Declare components | Support | Not Support |
 | [Modular](../scripting/modular-script.md) | Support, you can refer to other Normal Script by [require](../scripting/modular-script.md#require), can not require Plugin Script | Not Support, also can not require Normal Script |
-| Variable Declaration | The variables defined within script are not exposed to global | Once published, local variables declared within the script that are not in any function are exposed as global variables. If in the editor, then it is the same as the Normal Script.<br>The local variables won't be exposed as global variables on WeChat, Baidu, Xiaomi, Alipay and ByteDance minigame. To achieve the same effect, you should declare the local variables as properties in global variable `window`. |
+| Variable Declaration | The variables defined within script are not exposed to global | Once published, local variables declared within the script that are not in any function are exposed as global variables. If in the editor, then it is the same as the Normal Script.<br>The local variables won't be exposed as global variables on WeChat, Baidu, Alipay and ByteDance minigame. To achieve the same effect, you should declare the local variables as properties in global variable `window`. |
 | use strict | Forced, undefined variables can not be assigned | Need to manually declare, otherwise once the undefined variable is assigned it will become a global variable |
 | When the script is imported into the project | The ES2015 feature in the script is [compiled](../scripting/reference/javascript-support.md) first, and then into a unified modular analysis process | Do not do anything |
 | During the project building phase | All Normal Scripts will be packaged into a **single** script file, and in the release mode will be further compressed | Not packaged, and in the release mode will be compressed. |

versions/2.4/en/scripting/plugin-scripts.md

@@ -227,7 +227,7 @@ In TypeScript, a namespace is an ordinary, named Javascript object that is locat
 
 Creator defaults all scripts in the assets directory will be compiled, and a modular package is automatically generated for each script so that the scripts can reference each other via `import` or `require`. When we want to place a script's variables and methods in the global namespace rather than in a module, we need to select this script resource and set the script `import as plugin` in the **Properties**. Scripts that are set up as Plug-ins will not encapsulated in a modularly and are not automatically compiled.
 
-> **Note**: in the WeChat, Baidu, Xiaomi, Alipay mini game environments, the global variables need to explicitly set properties of `window` to declare successfully, such as `window.data = {};`.
+> **Note**: in the WeChat, Baidu, Alipay mini game environments, the global variables need to explicitly set properties of `window` to declare successfully, such as `window.data = {};`.
 
 So for TypeScript scripts that contain namespaces, we can neither compile and modularize the scripts nor set them as plugin scripts (which will cause TS files not to be compiled into JS). If you need to use namespaces, we need to work with a specific workflow.
 

versions/2.4/en/scripting/typescript.md

@@ -433,10 +433,6 @@
                         "text": "Publish to Honor Mini Games",
                         "link": "publish/publish-honor-mini-game.md"
                     },
-                    {
-                        "text": "Publish to Xiaomi Quick Games",
-                        "link": "publish/publish-xiaomi-quick-games.md"
-                    },
                     {
                         "text": "Publish to Baidu Mini Games",
                         "link": "publish/publish-baidugame.md",

versions/2.4/en/summary.json

@@ -112,7 +112,6 @@
     - [发布到 OPPO 小游戏](publish/publish-oppo-instant-games.md)
     - [发布到 vivo 小游戏](publish/publish-vivo-instant-games.md)
     - [发布到荣耀小游戏](publish/publish-honor-mini-game.md)
-    - [发布到小米快游戏](publish/publish-xiaomi-quick-games.md)  
     - [命令行发布项目](publish/publish-in-command-line.md)
     - [定制项目构建模板](publish/custom-project-build-template.md)