Developer Information
Firstly, any questions about interaction with Tasker, please use the Developer Board (see menu left).
Trigger External Actions
There are four ways to invoke external components from Tasker:
- Use the Action Intent and Component Intent actions (in the Misc category) to send broadcasts. This is not very user-friendly.
- Write a Locale-Compatible setting plugin which will then appear in the Plugins category.
- Run an Android Scripting Environment script via action Run Script in the Misc category.
- Make your component controllable via intent broadcasts and contact me via the Developer board. Your app can then be included in the 3rd Party action category. I make no guarantees about which apps I will include in this manner so please contact me before you do any work in this direction.
Signal Tasker That Something Has Happened
There are two ways to arrange this:
- Write a Locale-Compatible condition plugin which will then appear in the Plugin state category. This possibility is only available in Tasker 1.1 and later.
- If you feel a condition plugin is not suitable for your purpose, then I'm happy to consider building in an intent handler for it which will then appear as an Event or a State, depending what's most appropriate.
Just make a post on the developer board with the details ('I broadcast x.y.ACTION_X when X happens, it has these extras...').
Run Existing and New Tasks
You can also easily create tasks programatically for Tasker to run, or invoke named tasks previously created
by the user. For more information see here.
Home Screen Intent
Tasker's Go Home action can specify the page of the home screen which should be shown. To support this action, a home screen need only accept the extra
net.dinglisch.android.tasker.extras.HOME_PAGE
with the launch intent, the value being an integer from 1 to 20.
|