As for myself I would say that scripts could benefit a higher level interface such as this one, for instance by loading it at startup, but I don’t wish to change the API at the launcher level yet, because sticking to the Tasker provided API let me upgrade it easily, should an update appear some day.
Personnellement je dirais que les scripts pourraient en effet bénéficier d’une API plus haut niveau, par exemple en chargeant TaskerTask au démarrage, par contre je ne souhaite pas changer l’API existante au niveau de LLX car c’est celle fournie par Tasker, de cette manière c’est simple pour moi de la mettre à jour si du côté de Tasker elle évolue.
This is exactly what I’m working at ATM, and thats why I need to create a File Chooser Dialog. I want to create a script which can import any readable file into a script.
D5 Creation
< ![CDATA[
As for myself I would say that scripts could benefit a higher level interface such as this one, for instance by loading it at startup, but I don’t wish to change the API at the launcher level yet, because sticking to the Tasker provided API let me upgrade it easily, should an update appear some day.
]]>
< ![CDATA[
can you translate in french… even with GTraduction I don’t understand this comment…
]]>
< ![CDATA[
I would prefer the top one, because setAction is already a function and there shouldn’t be a property with the same name.
]]>
< ![CDATA[
no Lukas Morawietz I’m making a new object, I’m not adding function to TaskerIntent, but TaskerTask (my creation)
]]>
< ![CDATA[
ok 🙂
Personnellement je dirais que les scripts pourraient en effet bénéficier d’une API plus haut niveau, par exemple en chargeant TaskerTask au démarrage, par contre je ne souhaite pas changer l’API existante au niveau de LLX car c’est celle fournie par Tasker, de cette manière c’est simple pour moi de la mettre à jour si du côté de Tasker elle évolue.
]]>
< ![CDATA[
Oh yes, of course ! it’s just an additional API, to make tasker tasks manipulations easier !
And TaskerTask use ‘internally’ all the TaskerIntent’s feature, so we must load it…
(is it possible to import js files in our scripts ?)
]]>
< ![CDATA[
Benoît de Chezelles
This is exactly what I’m working at ATM, and thats why I need to create a File Chooser Dialog. I want to create a script which can import any readable file into a script.
]]>
< ![CDATA[
Lukas Morawietznice, but that’s not what I was saying, I mean : import “task.js”
or
import “/storage/sdcard1/LLX/js/script.js”
To access the functions located in script.js
Surely, the first one is better, but actually (I think), script are not on sdcard… (or easy access storage place)
]]>
< ![CDATA[
Ah, you want to use a js file as library
]]>
< ![CDATA[
Yes exactly
Pierre Hébert possible ?
]]>
< ![CDATA[
everything works fine ! in the dropbox folder, you’ll find “TaskerTask test.js”, it’s a LLX script that you can use to try the api..
…
You’ll find at the end of that file an example of use.. Try to play with it !
ATM there is only the setVariable & flash Tasker actions available…
I’ll make a new post to explain to thoses who may want help me, how to add others tasker actions support in TaskerTask API !
]]>
< ![CDATA[
Ryoen Deprouw check this out…
]]>
< ![CDATA[
Eric Chaffey Thnx, I will check it…
]]>