move to v0.5.9 && Update documents

renyuneyun · May 9, 2018 · 2a0a888 · 2a0a888
1 parent 3d203a4
commit 2a0a888
Show file tree

Hide file tree

Showing 8 changed files with 24 additions and 4 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,6 +1,12 @@
 CHANGELOG
 ======
 
+* v0.5.9: Add *Condition* mechanism && Add BatteryConditionPlugin && Fix importing / exporting due to storage change
+	* Add *Condition* mechanism, as a complementary of Event
+		* *Condition* represents for "state", and *Event* will be changed to represent real one-shot events
+	* Add BatteryConditionPlugin
+	* Fix importing / exporting, which was broken because of naming change (event -> script)
+
 * v0.5.8: Rename the UI component "Event" to "Script" && Activity Log && New plugins (`UiModeOperationPlugin` & `ScreenEventPlugin`) && Allow to assign delay to set bluetooth volume && Little UI update
 	* Rename the UI component "Event" to "Script" to avoid confusion to "scenario" (and also for future needs)
 	* New page (Activity Log) for Easer's activity log

diff --git a/README.en.md b/README.en.md
@@ -27,6 +27,8 @@ Easer is also a coordinator of inter-app actions (e.g. communications) -- it can
 
 You can chain *Script* (which specifies *Events* as well as its *Profile*) as trees (i.e. setting dependencies), by specifying its *Parent*. This mechanism allows Easer to (somewhat) create custom *Events* using Boolean logic (e.g. "and", "or").
 
+Easer is adding the support of *Condition* mechanism, and is transforming relevant *Event* to *Condition*, for better expressivity.
+
 Currently, Easer performs a post-order traversal to load your *Profiles*. In the near future, Easer will have more meticulous, expressive and intuitive categorization of *Events*.
 
 Also, have a look at the [wiki](https://github.com/renyuneyun/Easer/wiki), and especially the [FAQ](https://github.com/renyuneyun/Easer/wiki/FAQ).

diff --git a/README.md b/README.md
@@ -25,7 +25,9 @@ Easer也是app合作的協調者——自定義在收到特定廣播（Broadcast
 
 ### 自定義事件
 
-Event可對事件腳本（Script，包含Event及對應載入的Profile）設置依賴（前置條件），使得他們以樹狀鏈接。這一機制使得Easer的事件初步具備使用布爾邏輯（與、或）相鏈接的能力，以便實現自定義事件。
+Easer可對事件腳本（Script，包含Event及對應載入的Profile）設置依賴（前置條件），使得他們以樹狀鏈接。這一機制使得Easer的事件初步具備使用布爾邏輯（與、或）相鏈接的能力，以便實現自定義事件。
+
+Easer在逐步支持*狀況*（Condition）機制，且在逐漸將相關*事件*遷移至*狀況*。
 
 當前，Easer會以後續遍歷選擇所有符合條件的Script對應Profile載入。但在不久的將來，Easer將會擁有更細緻且更直觀的對事件狀況的分類，使得用戶擁有對事件更佳的把握。
 

diff --git a/app/build.gradle b/app/build.gradle
@@ -7,8 +7,8 @@ android {
         applicationId 'ryey.easer'
         minSdkVersion 15
         targetSdkVersion 23
-        versionCode 65
-        versionName "0.5.8"
+        versionCode 67
+        versionName "0.5.9"
 
         vectorDrawables.useSupportLibrary = true
 

diff --git a/docs/en/FEATURES.md b/docs/en/FEATURES.md
@@ -19,6 +19,9 @@ Supported Features
 * TCP communication (one round trip)
 * Screen on/off
 
+### Condition
+* Battery status
+
 ### Operation
 * WiFi switch
 * Cellular network switch

diff --git a/docs/en/README.md b/docs/en/README.md
@@ -24,6 +24,8 @@ Easer is also a coordinator of inter-app actions (e.g. communications) -- it can
 
 You can chain *Script* (which specifies *Events* as well as its *Profile*) as trees (i.e. setting dependencies), by specifying its *Parent*. This mechanism allows Easer to (somewhat) create custom *Events* using Boolean logic (e.g. "and", "or").
 
+Easer is adding the support of *Condition* mechanism, and is transforming relevant *Event* to *Condition*, for better expressivity.
+
 Currently, Easer performs a post-order traversal to load your *Profiles*. In the near future, Easer will have more meticulous, expressive and intuitive categorization of *Events*.
 
 Also, have a look at the [wiki](https://github.com/renyuneyun/Easer/wiki), and especially the [FAQ](https://github.com/renyuneyun/Easer/wiki/FAQ).

diff --git a/docs/zh/FEATURES.md b/docs/zh/FEATURES.md
@@ -19,6 +19,9 @@
 * TCP通信
 * 屏幕開啓/關閉
 
+### 狀況(Condition)
+* 電池狀況
+
 ### 動作(Operation)
 * WiFi開關
 * 數據網絡開關

diff --git a/docs/zh/README.md b/docs/zh/README.md
@@ -19,7 +19,9 @@ Easer也是app合作的協調者——自定義在收到特定廣播（Broadcast
 
 ### 自定義事件
 
-Event可對事件腳本（Script，包含Event及對應載入的Profile）設置依賴（前置條件），使得他們以樹狀鏈接。這一機制使得Easer的事件初步具備使用布爾邏輯（與、或）相鏈接的能力，以便實現自定義事件。
+Easer可對事件腳本（Script，包含Event及對應載入的Profile）設置依賴（前置條件），使得他們以樹狀鏈接。這一機制使得Easer的事件初步具備使用布爾邏輯（與、或）相鏈接的能力，以便實現自定義事件。
+
+Easer在逐步支持*狀況*（Condition）機制，且在逐漸將相關*事件*遷移至*狀況*。
 
 當前，Easer會以後續遍歷選擇所有符合條件的Script對應Profile載入。但在不久的將來，Easer將會擁有更細緻且更直觀的對事件狀況的分類，使得用戶擁有對事件更佳的把握。