No Tasker Sunday But there is good things coming
This has been a busy week for me. At the end of last week I asked the Tasker Google+ community for some ideas of what they would like to see, and the first lesson I took away from that was – I should have asked sooner than Thursday!
The community have some fantastic ideas just waiting for Tasker, but there is no way I can do them any justice by “Tasker Sunday” so instead I offer you this post as my mitigation.
Over the next few weeks I intend to push out the first of these ideas +J Pearson gave me. Like many self employed contractors he wanted a way to get Tasker to record and track his work using voice inputs, something like:
**"I'm done for today"**
"How many hours did you work?"
"Who were you working for?"
"What did you do?"
**"Made the world go round"**
Then at the end of the month/week be able to pull out a report of who you need to bill and for how much.
When I mentioned this idea to a few other it has definitely struck a cord so I’m going to make this my first task, although it will probably turn into a project with multiple tasks and actions.
The Futures Bright The Futures Tasker
The next thing on my ‘agenda’ is a new idea I came up with yesterday. Since Android 4.3 came out I’ve seen allot of people use the input command to mimic screen touches and swipes, this is perfect for working with applications that have no Tasker interface or public APIs you can get a hold of. The problem is any input command used is specific to the screen its been recorded on, something I do on my Nexus 4 has no hope of working on the Nexus 7 or HTC Sensation without rewriting the co-ordinates.
My idea is to create some kind of query database that will return the correct location. For example, and these are only examples off the top of my head mind you, to click the send button in the Gmail add you would ask for the location by passing “deviceid, app, button name” this would return “123,456” for the Nexus 4 and “789,012” on the Nexus 7. As this obviously a new idea there are allot of problems still to workout, like: some form of local caching, a unified naming scheme for buttons and a way for the community to input new devices and new locations. Lets just say, this will be a long process – if you have any ideas about it please drop me a line.
Before you go I wouldn’t want to leave you without
Now, seeing as I’m not posting any Tasker projects today I don’t want to leave you without. +Tasker by Ryoen has posted a fantastic and easy to follow example of using +João Dias’s AutoVoice and the new AutoApp, still in beta, to open any app just by saying its name. Hope you enjoy this