Support for calling other TagUI scripts within a script

It would be great to have the the ability to create a library of functions that include actions, blocks of code that I can reuse from script to script.

example: include include.filename

This feature would allow us to create reusable code and provide the ability to rapidly create new scripts based on previous work.

best regards, Terry

[terrygoldman]

Sure, will do over the weekend and get back to you on this.

BR, Terry

On 6 Mar 2018, at 23:50, Ken Soh <[e-mail]:[e-mail]> wrote:

Hey Terry no probs at all, I’m closing the issue to focus on working on some of the outstanding ideas to explore. Do let me know if you run into issue calling subscripts using the above tagui step and I’ll reopen the issue to track when needed.

Let me know too your thoughts, if there is a way to improve on the current implementation. I chose the word tagui instead of programming convention call or include or require, so that the same word can be used even for other languages. As TagUI supports writing scripts in over 20 human languages, something like call or include can be translated and I got a hunch doing that can introduce bugs later on.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/kelaberetiv/TagUI/issues/80#issuecomment-370826685, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AiI5Tc7KtzUfu6-hB_NMPmshSzNdw7Pjks5tbrAwgaJpZM4SUKWR.

[kensoh]

Adding on, besides following naming convention -

tagui filename

Users can also use something like below to make it easier to organize their ‘action libraries’. By naming the filename as some context . followed by some action.

tagui context.action

For example, below will expand a TagUI script named as mainscreen.login to perform the login actions.

tagui mainscreen.login