Glossary of Terms

 Main Coding objects

Code button – A visual object represented by a particular shape or image.
Properties:
Code Name
Functions:
can be pushed down,
can affect the coding process,
can be the initiator for a link

Event – a code button
Properties:
Lead Time
Lag Time
Functions:
can become turned on creating a new instance
can become turned off ending the instance
can be the master of popup tags
can be the target of a link

Tag – a code button
Properties:
Global Tag
Functions:
label an instance
be the target of a link

Popup tag – a code button
labels its master’s Event instances

Link an object that connects two code buttons
Properties:
Activate Target On Activation
Deactivate Target On Activation
Reactivate Lag Time On Activation
Activate Target On Deactivation
Deactivate Target On Deactivation
Pass Tags
Functions:
can turn a target on
can turn a target off
can reactivate a target’s lag time
can pass tag data

Exclusive Link Cluster – A logical group that includes member events
Properties:
Pass Last Event’s Code
Functions:
turns members off
can pass the last Event’s code on to the next activated member

 

Other objects and terms

Instance– A passage in time, created by a particular event
Properties:
Start Time
End Time
Code Name
Labels

Active instance
An instance that has been created, but has not been closed yet. It has an empty End Time property.

Current instance
An instance that is the last created with the event. When the coding session begins no Event has current instance. The last created active instance is the current instance for it’s Event. When the active instance is closed it remains the current instance until a new one is created.

Master event
An Event against its popup tags.

Coding session
A time interval that contains instances. A coding session has it’s own timer which starts with 0.

Code stack
An array of codes passed down a Link chain.

To label
Means to add a code name into the labels property of an instance.

Last Active Event
The last activated Event in the coding history. Even if it has been turned off (by run out lag time or user action) it remains the Last Active Event. It is able to receive doLabel messages from tags and links. Receiving doLabel messages makes it send doLabel messages to its current instance.

 Messages

During a coding session the user sends messages to code buttons. Thereafter, the code buttons send messages to the links connected to them.

Code buttons can receive messages:
pushDown – the message is initiated when the user presses a code button.
doActivate – the message is initiated by a link.
doDeactivate – the message is initiated by a link or exclusive link cluster.
doReactivateLagTime – the message is initiated by a link.
doLabel – the message is initiated by a link or tag. This message contains a code stack.

Links can receive messages from initiator code buttons
initiatorDidTurnOn – the message is initiated by a code button
initiatorDidTurnOff – the message is initiated by a code button
doLabel – the message is initiated by a tag (initiator). This message contains a code stack.

Coding SequenceWhen coding objects receive messages they do the following actions in the following order:

Turned off Event receives pushDown or doActivate message:
Sends a initiatorDidTurnOn message to all outbound links.
Sends a initiatorDidTurnOn message to the exclusive link cluster.
Creates the active instance.

Turned on Event receives doActivate message
No actions

 Turned on Event receives pushDown or doDeactivate message: 
Sends a initiatorDidTurnOff message to all outbound links.
Closes the active instance.

Event receives doLabel message:

If the event is turned on or the event is turned off and is the Last Active Event it will label its current instance. This means the event adds a code stack into the instance’s labels array keeping the order of appearance.

Global Tag is pushed down by the User:
Sends a initiatorDidTurnOn message to all outgoing links.
Sends a doLabel message to all turned on events. The Code stack contains the tag’s code.

Tag is pushed down by the User:
Sends a initiatorDidTurnOn message to all outgoing links.
Creates a code stack and adds its code to it.
Sends a doLabel message with a copy of the code stack to all outgoing links.

Tag receives a doLabel message:
Adds its code to the received code stack if the code stack does not contain the tag’s code yet. Sends a copy of the code stack to all outgoing links.

Popup tag receives a pushDown message:
Creates a code stack and adds its code to it.
Sends a doLabel message to its master event.
Sends a initiatorDidTurnOn message to all outgoing links.

Link receives a initiatorDidTurnOn message
If the Activate Target On Activate property is set on the link sends a doActivate message to its target.
If the Deactivate Target On Activate property is set on the link sends a doDeactivate event to its target
If the Reactivate Lag Time On Activate property is set on the link sends a doReactivateLagTime message to the target event.

Link receives a initiatorDidTurnOff message
If the Activate Target On Deactivate property is set on the link sends a doActivate message to its target.
If the Deactivate Target On Deactivate property is set on the link sends a doDeactivate event to its target

Link receives a doLabel message
If the Pass Tags property is set on the link passes a doLabel message to its target.

Exclusive link cluster receives a initiatorDidTurnOn message
Sends a doDeactivate message to all members except the initiator.
If the property Pass Last Code as Tag is set on the cluster sends a doLabel to the initiator. A Code stack contains code of the previous event.

 Coding Routines

Creation of an instance
An instance can only be created by an event.
An Event creates an instance when it goes from a turned off into a turned on state.
An Event sets a Code Name of the newly created instance to be equal to the Event’s Code Name.
A Start Time is assigned at the moment of creation.
A Start Time is calculated using this formula:
Start Time = Current Coding Session Time – Lead Time
If the Start Time is negative it sets to be 0.

Closing of an instance
An instance can only be closed by the same event it has been created by.
An Event closes an instance when it goes from a turned off into a turned on state.
An End Time is assigned at the moment of closing.
An End Time is calculated using this formula:
End Time = Current Coding Session Time + Lag Time

 


Fatal error: Call to undefined function get_top_parent_page_id() in /home/sporthelp/public_html/wp-content/themes/tropixel/footer-nav.php on line 27