-
Notifications
You must be signed in to change notification settings - Fork 93
Usage example
Since many people have no clue how Easer should be used (probably because of the unproper UI), this page is created to describe usages and some basic examples for Easer. (Note this page is not intended for sharing usages -- some other places may be used later for this purpose.)
This tutorial will assume you have basic understanding of common interaction patterns and UI elements of Android apps (e.g. navigation drawer). Please refer to relevant documents first if you don't. This is not only a joke :/
Please read the following content linearly, unless explicitly said.
Function description and first-use
Generally, since Easer is for automation based on your needs, you should have some requirements first.
In the first part of this tutorial, let's assume you want to:
- mute your phone and turn off wifi at 1:00 am
- turn wifi on when reaching home
Then, you should (naturally be able to) restructure your needs as:
- At 1:00 am => (mute phone & turn off wifi)
- When reaching home => (turn wifi on)
Aha, you now get an Event and a set of actions/operations (i.e. Profile in Easer) for each requirement. This is what "event-driven" means -- do something when an event happens.
Then, things become intuitive:
- Move to Event page
- Create an Event named (for example)
E1
, with the content selecting the "Time" event and 1:00 am - Do the similar thing for "reaching home" (you can use "Cell Location" for this, which depends on the cellular basestation)
- Create an Event named (for example)
- Move to Profile page
- Create a Profile named (for example)
pA
, with two Operations (by clicking the "add" button)- mute phone ("Ringer Mode" -> mute / do-not-disturb)
- turn off wifi ("WiFi" -> off)
- Do the similar thing for "reaching home"
- Create a Profile named (for example)
The reason Event and Profile are separated is for reusing -- this will be covered later.
Then, you have the last step to do: create Script to link between Event and Profile.
- Move to Script page
- Create a new Script
- Name it "At 1 am"
- At the "Profile" part, select
pA
in the drop-down menu - Choose "Use Event" (which is the default choice)
- Select
E1
in the drop-down menu for "Event" - Save
- Do the similar thing for "reaching home"
Now you are ready, and if you start the background service of Easer, your phone will be muted and wifi will be turned off at 1:00 am everyday, and wifi will be turned on when approaching your home (basestation, if you use "Cell Location").
Tips
There are some overlapping on the functionalities of Condition and Event.
As a rule of thumb, use Condition if you find your desired skill has both a Condition version and an Event version. This would give you more freedom when you want to chain Scripts <#chained-scripts>
__.
Advanced use
You may have noticed that there are more options than what is introduced in the previous part. They are more advanced functions of Easer, which usually do not need to change unless you know what you are doing (e.g. after reading this part). We try to make them as intuitive as possible, and/but here are some more explanations and examples.
This is the "Predecessor" setting when editing a Script.
Scripts can be connected like graphs <https://en.wikipedia.org/wiki/Graph_(abstract_data_type)>
_.
See issues #62 <https://github.com/renyuneyun/Easer/issues/62>
_ #152 <https://github.com/renyuneyun/Easer/issues/152>
_ for some examples.
This is the "chain"/"link" button besides "Profile" spinner/drop-down-list when editing a Script.
See the Dynamics section of the Features page <https://renyuneyun.github.io/Easer/en/FEATURES.html>
_.
This is the extra settings when editing an Event.