Expecco Scripting API/en - Versionsgeschichte

Cg: /* Ruby */

2020-05-04T11:37:21Z

Ruby

← Nächstältere Version		Version vom 4. Mai 2020, 11:37 Uhr
Zeile 144:		Zeile 144:
	you should use "to_s" as in:		you should use "to_s" as in:
	STDERR.puts ":out:pinName:"+count.to_s		STDERR.puts ":out:pinName:"+count.to_s

			To generate a log entry, use
			STDERR.puts ":logInfo:some info message from ruby"

	For ruby, collections as input values are converted to ruby arrays if the pin type is "Array";		For ruby, collections as input values are converted to ruby arrays if the pin type is "Array";

Cg: /* Ruby */

2020-05-04T11:34:02Z

Ruby

← Nächstältere Version		Version vom 4. Mai 2020, 11:34 Uhr
Zeile 145:		Zeile 145:
	STDERR.puts ":out:pinName:"+count.to_s		STDERR.puts ":out:pinName:"+count.to_s

	For ruby, collections as input values are converted to ruby arrays;		For ruby, collections as input values are converted to ruby arrays if the pin type is "Array";
	i.e. if you pass an expecco array, such as #(1 3 5 7) as input, ruby will see it as "[1,3,5,7]".		i.e. if you pass an expecco array, such as #(1 3 5 7) as input, ruby will see it as "[1,3,5,7]".

Cg: /* Ruby */

2020-05-04T11:33:34Z

Ruby

← Nächstältere Version		Version vom 4. Mai 2020, 11:33 Uhr
Zeile 144:		Zeile 144:
	you should use "to_s" as in:		you should use "to_s" as in:
	STDERR.puts ":out:pinName:"+count.to_s		STDERR.puts ":out:pinName:"+count.to_s

			For ruby, collections as input values are converted to ruby arrays;
			i.e. if you pass an expecco array, such as #(1 3 5 7) as input, ruby will see it as "[1,3,5,7]".

	== TCL, Powershell, Go, ... Scripts ==		== TCL, Powershell, Go, ... Scripts ==

Cg: /* Ruby, TCL, Powershelgl, Go... Scripts */

2020-05-04T11:32:08Z

Ruby, TCL, Powershelgl, Go... Scripts

← Nächstältere Version		Version vom 4. Mai 2020, 11:32 Uhr
Zeile 135:		Zeile 135:
	* run the script; you'll get the output as one big string at the "''stdout''" pin, and individual lines at the "''stdoutValue''" pin		* run the script; you'll get the output as one big string at the "''stdout''" pin, and individual lines at the "''stdoutValue''" pin

	== Ruby~~, TCL, Powershelgl, Go... Scripts~~ ==		== Ruby ==

			All of the above applies to ruby scripting as well.
			Of course, the syntax to write to a pin or to generate log entries is slightly different;<br>use:
			STDERR.puts ":out:pinName:"+someString
			to write to an output pin.
			Notice, that <someString> needs to be a string. If it is not (i.e. numbers, booleans etc.),
			you should use "to_s" as in:
			STDERR.puts ":out:pinName:"+count.to_s

			== TCL, Powershell, Go, ... Scripts ==

	All of the above applies to those scripting languages as well.		All of the above applies to those scripting languages as well.

Cg: /* Generating log Entries */

2020-05-04T11:28:29Z

Generating log Entries

← Nächstältere Version		Version vom 4. Mai 2020, 11:28 Uhr
Zeile 98:		Zeile 98:
	echo ":logInfo:<string>" 1>&2		echo ":logInfo:<string>" 1>&2

	~~Alternatives~~ ~~are~~ "logWarning", "logError", "logFail" ~~and~~ "logInconclusive".		Replace "logInfo" by one of "logWarning", "logError", "logFail" or "logInconclusive", for corresponding log entries.

	=== Accessing Attachment Files ===		=== Accessing Attachment Files ===

Cg: /* Additional Output Pins */

2020-05-04T11:27:39Z

Additional Output Pins

← Nächstältere Version		Version vom 4. Mai 2020, 11:27 Uhr
Zeile 84:		Zeile 84:
	It is also possible to add regular output pins, and write to them via (somewhat special) strings written to stderr:		It is also possible to add regular output pins, and write to them via (somewhat special) strings written to stderr:

	echo "out:<pinName>:<string>" 1>&2		echo ":out:<pinName>:<string>" 1>&2

	If the pin's type is Integer or Number, the <string> will be converted;<br>for example, if the action has an output pin named "nFiles" with datatype "Integer", the following will write the number of files (in the current directory) to that pin:		If the pin's type is Integer or Number, the <string> will be converted;<br>for example, if the action has an output pin named "nFiles" with datatype "Integer", the following will write the number of files (in the current directory) to that pin:
Zeile 90:		Zeile 90:
	echo ":out:nFiles:"`ls \| wc -l` 1>&2		echo ":out:nFiles:"`ls \| wc -l` 1>&2

	Notice, that by default, all scripts are executed in the project's temporary folder (where they would see any attachment files).		Notice, that by default, all scripts are executed in the project's temporary folder (where they would see any attachment files as described below).

			=== Generating log Entries ===

			In a similar way to the above, scripts can also generate entries to the expecco execution log:

			echo ":logInfo:<string>" 1>&2

			Alternatives are "logWarning", "logError", "logFail" and "logInconclusive".

	=== Accessing Attachment Files ===		=== Accessing Attachment Files ===

Cg: /* Additional Output Pins */

2020-05-04T11:25:41Z

Additional Output Pins

← Nächstältere Version		Version vom 4. Mai 2020, 11:25 Uhr
Zeile 86:		Zeile 86:
	echo "out:<pinName>:<string>" 1>&2		echo "out:<pinName>:<string>" 1>&2

	If the pin's type is Integer or Number, the <string> will be converted;		If the pin's type is Integer or Number, the <string> will be converted;<br>for example, if the action has an output pin named "nFiles" with datatype "Integer", the following will write the number of files (in the current directory) to that pin:
	for example, if the action has an output pin named "nFiles" with datatype "Integer", the following will write the number of files (in the current directory) to that pin:

	echo ":out:nFiles:"`ls \| wc -l` 1>&2		echo ":out:nFiles:"`ls \| wc -l` 1>&2

Cg: /* Additional Output Pins */

2020-05-04T11:25:28Z

Additional Output Pins

← Nächstältere Version		Version vom 4. Mai 2020, 11:25 Uhr
Zeile 86:		Zeile 86:
	echo "out:<pinName>:<string>" 1>&2		echo "out:<pinName>:<string>" 1>&2

			If the pin's type is Integer or Number, the <string> will be converted;
	for example, if the action has an output pin named "nFiles" with datatype "Integer", the following will write the number of files (in the current directory) to that pin:		for example, if the action has an output pin named "nFiles" with datatype "Integer", the following will write the number of files (in the current directory) to that pin:

Cg: /* Additional Output Pins */

2020-05-04T11:24:38Z

Additional Output Pins

← Nächstältere Version		Version vom 4. Mai 2020, 11:24 Uhr
Zeile 84:		Zeile 84:
	It is also possible to add regular output pins, and write to them via (somewhat special) strings written to stderr:		It is also possible to add regular output pins, and write to them via (somewhat special) strings written to stderr:

	echo "out:<pinName>:<string>" >2		echo "out:<pinName>:<string>" 1>&2

	for example, if the action has an output pin named "~~numFiles~~" with datatype "Integer", the following will write the number of files in a ~~folder~~ to that pin:		for example, if the action has an output pin named "nFiles" with datatype "Integer", the following will write the number of files (in the current directory) to that pin:

	~~n =~~ ls \| wc -l		echo ":out:nFiles:"`ls \| wc -l` 1>&2

	echo "out:numFiles:$(n)"
			Notice, that by default, all scripts are executed in the project's temporary folder (where they would see any attachment files).


	=== Accessing Attachment Files ===		=== Accessing Attachment Files ===

Cg: /* Shell Scripts */

2020-05-04T10:51:16Z

Shell Scripts

← Nächstältere Version		Version vom 4. Mai 2020, 10:51 Uhr
Zeile 55:		Zeile 55:
	== Shell Scripts ==		== Shell Scripts ==

		⚫	Notice to Windows users:<br>you have to have a unix compatible shell installed and either "sh" in your PATH, or the path to "sh.exe" configured in expecco's "''Execution''" - "''External Tools''" settings.
	Notice to Windows users:

⚫	you have to have a unix compatible shell installed and either "sh" in your PATH, or the path to "sh.exe" configured in expecco's "''Execution''" - "''External Tools''" settings.
	Many shell packages can be found in the internet, for example "cygwin", "win-sh", etc.		Many shell packages can be found in the internet, for example "cygwin", "win-sh", etc.