In the near future, I want to implement console for Javascripts in the first place, as decribed by Mikhail her And then one could build interaction with Tasker if they wish to, on their own. So, if Tasker triggers on a certain event (intent?), I could add a EN-javascript interface (ENJSI) that would launch intents in general with arguments taken from your javascript program. I think it would be more effective to add a post scripting capacity without relying on third-party's API. Here is an example of an app created within EN that loads data, does some calculation and saves data back They already can be used to load a document from Sd card to a javascript variable, make changes and save documents back. Like EN already has ENJSI.save and ENJSI.load. I was thinking of providing scripting opportunities through Javascript interfaces. That app can then deal with further actions (including executing a shell script, if so desired) > An alternative to shell scripts could be notifying an automation app through the tasker event API. Possibly a global setting, effective for any written file, and file specific scripts, specified through a YAML tag. > allow to specify locations and names of post save and export (shell) scripts, so further actions can be performed on written files after those events. ![]() The style yaml will also be used in Epsilon Notes. ![]() > Substitute variables like in html at export, as described here: provide a YAML tag which allows automatically exporting the document when it's saved.
0 Comments
Leave a Reply. |