Annotate Actions?

Post here if you need help using Actiona
Post Reply
Spatpora
Posts: 2
Joined: 15 Mar 2019, 22:44

Annotate Actions?

Post by Spatpora » 15 Mar 2019, 22:46

Hey there everyone.

I finally used this program, and set up a very complex script to automate a task I perform regularly. However, this task needs to be modified from time to time, and with over 100 actions, it can get very difficult to find the correct action to edit.

Other than the colors, which don't provide any meaningful information to me, is there any way to annotate or comment the actions? That would be really helpful

Thanks in advance, awesome app!

PS: Running on Ubuntu, latest version.

eureka
Posts: 87
Joined: 08 Mar 2016, 22:18

Re: Annotate Actions?

Post by eureka » 16 Mar 2019, 14:34

I am using Actiona in Ubuntu 16.04.
I can imagine that a single Actiona script with over 100 commands might become unwieldy.
I suggest breaking down the workflow into more manageable modules and saving these as a series of sub-actions.
Then you can have a master Actiona script which runs a series of say 10 commands
which launch the modules and then attach a MessageBox per module.

You would run in master script ..

Command: actexec module1.ascr
MessageBox1 // documentation on module1
Command: actexec module2.ascr
MessageBox2 // documentation on module2
Command: actexec module3.ascr
MessageBox3 // documentation on module3
Command: actexec module4.ascr
MessageBox4 // documentation on module4

In summary create a hierarchy. I have a library of such modular *.ascr files which I launch for desktop tasks using a python script (subprocess).

Another way I can think of would be to open your single large *.ascr file in an XML editor such as
XML Copy Editor and insert xml comments.

<!-- comments -->

Spatpora
Posts: 2
Joined: 15 Mar 2019, 22:44

Re: Annotate Actions?

Post by Spatpora » 23 Mar 2019, 22:19

That is a good way to do it. I will try to figure out, but in case I don't, how would I split something into modules? And then call on them in the master script?

eureka
Posts: 87
Joined: 08 Mar 2016, 22:18

Re: Annotate Actions?

Post by eureka » 23 Mar 2019, 22:52

Really the breakup of 100 actions into "modules" is up to you.
You can either have a single *.ascr script containing 100 separate actions
as you have now.
Or you can create a number of *.ascr scripts and in a separate meta script call these
one by one through actexec command.

Yet another approach would be to use OpenURL action after each command which opens documents in a wiki.
Zim Desktop Wiki might be used for documentation in browser.

JB0591
Posts: 5
Joined: 13 Mar 2019, 13:44

Re: Annotate Actions?

Post by JB0591 » 26 Mar 2019, 00:19

eureka wrote:
16 Mar 2019, 14:34
Then you can have a master Actiona script which runs a series of say 10 commands
which launch the modules and then attach a MessageBox per module.

You would run in master script ..

Command: actexec module1.ascr
MessageBox1 // documentation on module1
Command: actexec module2.ascr
MessageBox2 // documentation on module2
Command: actexec module3.ascr
MessageBox3 // documentation on module3
Command: actexec module4.ascr
MessageBox4 // documentation on module4

In summary create a hierarchy. I have a library of such modular *.ascr files which I launch for desktop tasks using a python script (subprocess).
I see that actexec is included in the windows installation. I can start a script using actexec from the cmd line but not using a command in ActionA. Says cant open file despite all details being provided.

eureka
Posts: 87
Joined: 08 Mar 2016, 22:18

Re: Annotate Actions?

Post by eureka » 26 Mar 2019, 10:58

It is sometime since I tested this (on Ubuntu) but here is an old test script I found .. note that Detached Command is used and not Command ..

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<scriptfile>
    <settings program="actiona" version="3.9.1" scriptVersion="1.1.0" os="GNU/Linux"/>
    <actions>
        <action name="ActionDetachedCommand" version="1.0.0"/>
    </actions>
    <parameters/>
    <resources/>
    <script pauseBefore="0" pauseAfter="0">
        <action name="ActionDetachedCommand">
            <exception id="2" action="1" line=""/>
            <exception id="32" action="0" line=""/>
            <exception id="0" action="0" line=""/>
            <exception id="1" action="0" line=""/>
            <parameter name="command">
                <subParameter name="value" code="0">actexec</subParameter>
            </parameter>
            <parameter name="parameters">
                <subParameter name="value" code="0">test.ascr</subParameter>
            </parameter>
            <parameter name="workingDirectory">
                <subParameter name="value" code="0"></subParameter>
            </parameter>
            <parameter name="processId">
                <subParameter name="value" code="0"></subParameter>
            </parameter>
        </action>
    </script>
</scriptfile>

Or alternatively from Command action you might run a separate (python or bash) script which in turn runs actexec and launches snippets of *.ascr code.

For completion I will also add another approach I have used. It is to create a URL protocol handler which launches *.ascr snippets as a hyperlink in your browser. Discussion on URL protocol handlers here ..

https://support.shotgunsoftware.com/hc/ ... -Protocols

The security warning is that this allows hyperlinks to launch *.ascr code and malicious code could be damaging. But it offers another method of documenting a workflow perhaps in a tutorial and running actions directly on the user's desktop.

Instead of the example foo:// you might uses actiona:// for the Actiona protocol. This is similar to http://, file// and other URL protocols.

With this approach you can write your documents to flow in a browser and launch various actions.

Post Reply