Skip to content

Commit

Permalink
Move to v0.5.8 && Update documents
Browse files Browse the repository at this point in the history
  • Loading branch information
renyuneyun committed May 6, 2018
1 parent 2377e24 commit d437c1a
Show file tree
Hide file tree
Showing 8 changed files with 24 additions and 12 deletions.
8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,14 @@
CHANGELOG
======

* 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
* New plugin `UiModeOperationPlugin` for Android UI mode (e.g. car mode and normal mode)
* New plugin `ScreenEventPlugin` for screen on / off
* Allow to assign delay when setting bluetooth volume
* Add divider when selecting Operation

* v0.5.7.1: Fix bluetooth volume not changing && Fix crash when rotating && Code clean up
* Fix `VolumeOperationPlugin` changing bluetooth volume
* Fix crash when rotating device on `Edit{Event,Profile}Activity`
Expand Down
4 changes: 2 additions & 2 deletions README.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Make your smart phone smarter: tell it what to do under different situations.

Easer is an event-driven Android automation tool. It knows various events (see below) and YOU (the user) tell it what to do on what events (you can even combine multiple events). Thus, you no longer need to manually perform routine actions, or worry about forgetting to perform them.

You can think of Easer as a local version of IFTTT: trigger actions or change settings (*Operations*, bundled as *Profiles*) in different situations (*Events*).
You can think of Easer as a local version of IFTTT: trigger actions or change settings (*Operations*, bundled as *Profiles*) under different situations (*Events*).

### Inter-app coordination

Expand All @@ -25,7 +25,7 @@ Easer is also a coordinator of inter-app actions (e.g. communications) -- it can

### Custom Events

You can chain *Events* (set dependencies) as trees. This mechanism allows Easer to (somewhat) organize *Events* using Boolean logic (e.g. "and", "or").
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").

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*.

Expand Down
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ See [README.en.md](README.en.md) for the English version of README.
### 智能自動化
Easer是一個事件驅動的Android自動化工具——用戶告訴它在什麼情況下做什麼事(或連結多個事件來自定義事件),此後再也不需要手動進行這些例程,也不必擔心忘記進行。

Easer類似於一個本地版的IFTTT:在不同的狀況(Event)下載入指定的情境(Profile)。每個情境(Profile)由多個動作(Operation)組成,包括但不限於調整手機設置(見下)。
Easer類似於一個本地版的IFTTT:在不同的事件(Event)下執行指定的行爲集(Profile)。每個行爲集(Profile)由多個動作(Operation)組成,包括但不限於調整手機設置(見下)。

### app合作協調

Expand All @@ -25,9 +25,9 @@ Easer也是app合作的協調者——自定義在收到特定廣播(Broadcast

### 自定義事件

Event可設置依賴(前置條件),使得他們以樹狀鏈接。這一機制使得Easer的事件初步具備使用布爾邏輯(與、或)相鏈接的能力。
Event可對事件腳本(Script,包含Event及對應載入的Profile)設置依賴(前置條件),使得他們以樹狀鏈接。這一機制使得Easer的事件初步具備使用布爾邏輯(與、或)相鏈接的能力,以便實現自定義事件

當前,Easer會以後續遍歷選擇所有符合條件的Event對應Profile載入。但在不久的將來,Easer將會擁有更細緻且更直觀的對事件狀況的分類,使得用戶擁有對事件更佳的把握。
當前,Easer會以後續遍歷選擇所有符合條件的Script對應Profile載入。但在不久的將來,Easer將會擁有更細緻且更直觀的對事件狀況的分類,使得用戶擁有對事件更佳的把握。


另請參見[wiki](https://github.com/renyuneyun/Easer/wiki),尤其是[須知](https://github.com/renyuneyun/Easer/wiki/%E9%A0%88%E7%9F%A5)
Expand Down
4 changes: 2 additions & 2 deletions app/build.gradle
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@ android {
applicationId 'ryey.easer'
minSdkVersion 15
targetSdkVersion 23
versionCode 64
versionName "0.5.7.1"
versionCode 65
versionName "0.5.8"

vectorDrawables.useSupportLibrary = true

Expand Down
2 changes: 2 additions & 0 deletions docs/en/FEATURES.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ Supported Features
* NFC tag scanned
* Headset plug in/out
* TCP communication (one round trip)
* Screen on/off

### Operation
* WiFi switch
Expand All @@ -37,6 +38,7 @@ Supported Features
* Change Event status
* Control volume
* Launch App
* UI mode (e.g. car mode)

### Misc
* Formatting expression (supported in the fields of many Events/Operations)
Expand Down
4 changes: 2 additions & 2 deletions docs/en/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Make your smart phone smarter: tell it what to do under different situations.

Easer is an event-driven Android automation tool. It knows various events (see below) and YOU (the user) tell it what to do on what events (you can even combine multiple events). Thus, you no longer need to manually perform routine actions, or worry about forgetting to perform them.

You can think of Easer as a local version of IFTTT: trigger actions or change settings (*Operations*, bundled as *Profiles*) in different situations (*Events*).
You can think of Easer as a local version of IFTTT: trigger actions or change settings (*Operations*, bundled as *Profiles*) under different situations (*Events*).

### Inter-app coordination

Expand All @@ -22,7 +22,7 @@ Easer is also a coordinator of inter-app actions (e.g. communications) -- it can

### Custom Events

You can chain *Events* (set dependencies) as trees. This mechanism allows Easer to (somewhat) organize *Events* using Boolean logic (e.g. "and", "or").
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").

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*.

Expand Down
2 changes: 2 additions & 0 deletions docs/zh/FEATURES.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@
* 掃描NFC標籤
* 耳機插入/拔出
* TCP通信
* 屏幕開啓/關閉

### 動作(Operation)
* WiFi開關
Expand All @@ -37,6 +38,7 @@
* 控制事件狀態
* 調整音量
* 啓動程序
* 用戶界面模式(如車載模式)

### 雜項
* 格式化表達式(多數事件和動作的用戶輸入區均支持)
Expand Down
6 changes: 3 additions & 3 deletions docs/zh/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
### 智能自動化
Easer是一個事件驅動的Android自動化工具——用戶告訴它在什麼情況下做什麼事(或連結多個事件來自定義事件),此後再也不需要手動進行這些例程,也不必擔心忘記進行。

Easer類似於一個本地版的IFTTT:在不同的狀況(Event)下載入指定的情境(Profile)。每個情境(Profile)由多個動作(Operation)組成,包括但不限於調整手機設置(見下)。
Easer類似於一個本地版的IFTTT:在不同的事件(Event)下執行指定的行爲集(Profile)。每個行爲集(Profile)由多個動作(Operation)組成,包括但不限於調整手機設置(見下)。

### app合作協調

Expand All @@ -19,9 +19,9 @@ Easer也是app合作的協調者——自定義在收到特定廣播(Broadcast

### 自定義事件

Event可設置依賴(前置條件),使得他們以樹狀鏈接。這一機制使得Easer的事件初步具備使用布爾邏輯(與、或)相鏈接的能力。
Event可對事件腳本(Script,包含Event及對應載入的Profile)設置依賴(前置條件),使得他們以樹狀鏈接。這一機制使得Easer的事件初步具備使用布爾邏輯(與、或)相鏈接的能力,以便實現自定義事件

當前,Easer會以後續遍歷選擇所有符合條件的Event對應Profile載入。但在不久的將來,Easer將會擁有更細緻且更直觀的對事件狀況的分類,使得用戶擁有對事件更佳的把握。
當前,Easer會以後續遍歷選擇所有符合條件的Script對應Profile載入。但在不久的將來,Easer將會擁有更細緻且更直觀的對事件狀況的分類,使得用戶擁有對事件更佳的把握。

另請參見[wiki](https://github.com/renyuneyun/Easer/wiki),尤其是[須知](https://github.com/renyuneyun/Easer/wiki/%E9%A0%88%E7%9F%A5)

Expand Down

0 comments on commit d437c1a

Please sign in to comment.