Standard Library - Versionsgeschichte

Cg: /* Sending Events */

2021-03-04T10:27:32Z

Sending Events

← Nächstältere Version		Version vom 4. März 2021, 10:27 Uhr
Zeile 298:		Zeile 298:

	This makes it possible to communicate asynchronously from processes started inside a Node or Python		This makes it possible to communicate asynchronously from processes started inside a Node or Python
	server process. For example, a communication protocol reader~~, which~~ may push events on incoming messages,		server process. For example, a communication protocol reader may push events on incoming messages,
	to be processed asynchronously by an expecco action (eg. registered event handler action).		to be processed asynchronously by an expecco action (eg. the registered event handler action).

	* [[EventServer Get Global Server \| '''EventServer [ Get Global Server ]''' ]]<br/> Retrieve the global event handling server		* [[EventServer Get Global Server \| '''EventServer [ Get Global Server ]''' ]]<br/> Retrieve the global event handling server

Cg: /* Sending Events */

2021-03-04T10:26:48Z

Sending Events

← Nächstältere Version		Version vom 4. März 2021, 10:26 Uhr
Zeile 295:		Zeile 295:
	Events can be generated either via regular action blocks, or via calls to the Activity API.		Events can be generated either via regular action blocks, or via calls to the Activity API.
	The API is available both to internal elementary actions (i.e. Smalltalk and JavaScript actions),		The API is available both to internal elementary actions (i.e. Smalltalk and JavaScript actions),
	and to bridged (i.e. Node or ~~Python~~) actions.		and to bridged (i.e. Node, Python or C) actions.

	This makes it possible to communicate asynchronously from processes started inside a Node or Python		This makes it possible to communicate asynchronously from processes started inside a Node or Python

Cg: /* Overview */

2021-03-04T10:26:00Z

Overview

← Nächstältere Version		Version vom 4. März 2021, 10:26 Uhr
Zeile 283:		Zeile 283:
	* the handler will be scheduled and executed, getting the event at its sole input pin		* the handler will be scheduled and executed, getting the event at its sole input pin

	Although the general mechanism is very flexible, allowing for multiple queues and ~~allowing~~ for a very fine grain dispatch to different handlers via the eventType, most real world scenarios will only need a single queue and a single handler to handle all incoming events.		Although the general mechanism is very flexible, allowing for multiple queues and for a very fine grain dispatch to different handlers via the eventType, most real world scenarios will only need a single queue and a single handler to handle all incoming events.

	==== The Global Event Handler ====		==== The Global Event Handler ====

Cg: /* Overview */

2021-03-04T10:25:40Z

Overview

← Nächstältere Version		Version vom 4. März 2021, 10:25 Uhr
Zeile 282:		Zeile 282:
	* at some time, some action may want to trigger an event. This can be done either by a step in a compound, or by elementary code. It is even possible to trigger events from bridged actions.		* at some time, some action may want to trigger an event. This can be done either by a step in a compound, or by elementary code. It is even possible to trigger events from bridged actions.
	* the handler will be scheduled and executed, getting the event at its sole input pin		* the handler will be scheduled and executed, getting the event at its sole input pin

			Although the general mechanism is very flexible, allowing for multiple queues and allowing for a very fine grain dispatch to different handlers via the eventType, most real world scenarios will only need a single queue and a single handler to handle all incoming events.

	==== The Global Event Handler ====		==== The Global Event Handler ====

Cg: /* Overview */

2021-03-04T10:23:38Z

Overview

← Nächstältere Version		Version vom 4. März 2021, 10:23 Uhr
Zeile 276:		Zeile 276:

	The typical scenario is:		The typical scenario is:
	* define a handler action with one ~~pine~~ (there, the event will be delivered later)		* define a handler action block with one pin (there, the event will be delivered later)
	* in an initializing action, associate an event handling action to a tag. This can be done in a preAction or as the first action in a testplan. The association is done with the "[Register Handler]" action.		* in an initializing action, associate an event handling action to a tag. This can be done in a preAction or as the first action in a testplan. The association is done with the "[Register Handler]" action.
	* start the event handler process (typically, the global event handler)		* start the event handler process (typically, the global event handler)

Cg: /* Sending Events */

2021-02-16T01:22:57Z

Sending Events

← Nächstältere Version		Version vom 16. Februar 2021, 01:22 Uhr
Zeile 301:		Zeile 301:
	* [[EventServer Get Global Server \| '''EventServer [ Get Global Server ]''' ]]<br/> Retrieve the global event handling server		* [[EventServer Get Global Server \| '''EventServer [ Get Global Server ]''' ]]<br/> Retrieve the global event handling server
	* [[EventServer Register Handler \| '''EventServer [ Register Handler ]''' ]]<br/> Register a handler action in the global event handling server		* [[EventServer Register Handler \| '''EventServer [ Register Handler ]''' ]]<br/> Register a handler action in the global event handling server
			* [[EventServer Start \| '''EventServer [ Start ]''' ]]<br/> Start event processing
	* [[EventServer Suspend \| '''EventServer [ Suspend ]''' ]]<br/> Suspend event processing		* [[EventServer Suspend \| '''EventServer [ Suspend ]''' ]]<br/> Suspend event processing
	* [[EventServer Resume \| '''EventServer [ Resume ]''' ]]<br/> Resume event processing		* [[EventServer Resume \| '''EventServer [ Resume ]''' ]]<br/> Resume event processing

Cg: /* Overview */

2021-02-16T01:18:26Z

Overview

← Nächstältere Version		Version vom 16. Februar 2021, 01:18 Uhr
Zeile 277:		Zeile 277:
	The typical scenario is:		The typical scenario is:
	* define a handler action with one pine (there, the event will be delivered later)		* define a handler action with one pine (there, the event will be delivered later)
	* in an initializing action, associate an event handling action to a tag.		* in an initializing action, associate an event handling action to a tag. This can be done in a preAction or as the first action in a testplan. The association is done with the "[Register Handler]" action.
	This can be done in a preAction or as the first action in a testplan.
	The association is done with the "[Register Handler]" action.
	* start the event handler process (typically, the global event handler)		* start the event handler process (typically, the global event handler)
	* run your actions;		* run your actions;

Cg: /* Event Queues */

2021-02-16T01:17:44Z

Event Queues

@@ Zeile 274: / Zeile 274: @@
 Actions themself are defined as an expecco action (or JavaScript function or Smalltalk block),
 which must take a single input (the event) to be processed.
 ==== The Global Event Handler ====

Cg: /* Overview */

2021-02-16T01:12:40Z

Overview

← Nächstältere Version		Version vom 16. Februar 2021, 01:12 Uhr
Zeile 273:		Zeile 273:
	Handler actions are registered by eventType, which is a symbolic tag, attached to every event.		Handler actions are registered by eventType, which is a symbolic tag, attached to every event.
	Actions themself are defined as an expecco action (or JavaScript function or Smalltalk block),		Actions themself are defined as an expecco action (or JavaScript function or Smalltalk block),
	which must take a single input, the event to be processed.		which must take a single input (the event) to be processed.

	==== The Global Event Handler ====		==== The Global Event Handler ====

Cg: /* Comparing & Matching */

2020-11-22T01:11:04Z

Comparing & Matching

← Nächstältere Version		Version vom 22. November 2020, 01:11 Uhr
Zeile 583:		Zeile 583:
	* [[string regular expression match for subexpressions \| ''' String [ Regular Expression Match for Subexpressions? ] ''' ]] <br/> Do a regular expression pattern match, provide matched subexpressions (1.8.3).		* [[string regular expression match for subexpressions \| ''' String [ Regular Expression Match for Subexpressions? ] ''' ]] <br/> Do a regular expression pattern match, provide matched subexpressions (1.8.3).

	* [[string Extract All Regex Matches\| ''' String [ Extract All Regex Matches] ''' ]] <br/> Given a string and a regex pattern, provide a collection of ALL matching elements.		* [[string Extract All Regex Matches\| ''' String [ Extract All Regex Matches] ''' ]] <br/> Given a string and a [[Regex Pattern Info\|regex pattern]], provide a collection of ALL matching elements.
	* [[string Extract ONE Regex Match\| ''' String [ Extract ONE Regex Matches] ''' ]] <br/> Given a string and a regex pattern, provide the first matching elements.		* [[string Extract ONE Regex Match\| ''' String [ Extract ONE Regex Matches] ''' ]] <br/> Given a string and a [[Regex Pattern Info\|regex pattern]], provide the first matching elements.
	* [[string compare switch \| ''' String [ Compare Switch ] ''' ]] <br/> Compares a string with six other strings and triggers the first corresponding output-pin.		* [[string compare switch \| ''' String [ Compare Switch ] ''' ]] <br/> Compares a string with six other strings and triggers the first corresponding output-pin.
	* [[string includesstring \| ''' String [ IncludesString? ] ''' ]] <br/> If the given string is contained in another string (substring) send the original string to the triggerYES output. Otherwise send it to the triggerNO output.		* [[string includesstring \| ''' String [ IncludesString? ] ''' ]] <br/> If the given string is contained in another string (substring) send the original string to the triggerYES output. Otherwise send it to the triggerNO output.

← Nächstältere Version		Version vom 16. Februar 2021, 01:22 Uhr
Zeile 301:		Zeile 301:
	* [[EventServer Get Global Server \| '''EventServer [ Get Global Server ]''' ]]<br/> Retrieve the global event handling server		* [[EventServer Get Global Server \| '''EventServer [ Get Global Server ]''' ]]<br/> Retrieve the global event handling server
	* [[EventServer Register Handler \| '''EventServer [ Register Handler ]''' ]]<br/> Register a handler action in the global event handling server		* [[EventServer Register Handler \| '''EventServer [ Register Handler ]''' ]]<br/> Register a handler action in the global event handling server
			* [[EventServer Start \| '''EventServer [ Start ]''' ]]<br/> Start event processing
	* [[EventServer Suspend \| '''EventServer [ Suspend ]''' ]]<br/> Suspend event processing		* [[EventServer Suspend \| '''EventServer [ Suspend ]''' ]]<br/> Suspend event processing
	* [[EventServer Resume \| '''EventServer [ Resume ]''' ]]<br/> Resume event processing		* [[EventServer Resume \| '''EventServer [ Resume ]''' ]]<br/> Resume event processing

← Nächstältere Version		Version vom 22. November 2020, 01:11 Uhr
Zeile 583:		Zeile 583:
	* [[string regular expression match for subexpressions \| ''' String [ Regular Expression Match for Subexpressions? ] ''' ]] <br/> Do a regular expression pattern match, provide matched subexpressions (1.8.3).		* [[string regular expression match for subexpressions \| ''' String [ Regular Expression Match for Subexpressions? ] ''' ]] <br/> Do a regular expression pattern match, provide matched subexpressions (1.8.3).

	* [[string Extract All Regex Matches\| ''' String [ Extract All Regex Matches] ''' ]] <br/> Given a string and a regex pattern, provide a collection of ALL matching elements.		* [[string Extract All Regex Matches\| ''' String [ Extract All Regex Matches] ''' ]] <br/> Given a string and a [[Regex Pattern Info\|regex pattern]], provide a collection of ALL matching elements.
	* [[string Extract ONE Regex Match\| ''' String [ Extract ONE Regex Matches] ''' ]] <br/> Given a string and a regex pattern, provide the first matching elements.		* [[string Extract ONE Regex Match\| ''' String [ Extract ONE Regex Matches] ''' ]] <br/> Given a string and a [[Regex Pattern Info\|regex pattern]], provide the first matching elements.
	* [[string compare switch \| ''' String [ Compare Switch ] ''' ]] <br/> Compares a string with six other strings and triggers the first corresponding output-pin.		* [[string compare switch \| ''' String [ Compare Switch ] ''' ]] <br/> Compares a string with six other strings and triggers the first corresponding output-pin.
	* [[string includesstring \| ''' String [ IncludesString? ] ''' ]] <br/> If the given string is contained in another string (substring) send the original string to the triggerYES output. Otherwise send it to the triggerNO output.		* [[string includesstring \| ''' String [ IncludesString? ] ''' ]] <br/> If the given string is contained in another string (substring) send the original string to the triggerYES output. Otherwise send it to the triggerNO output.