Difference between revisions of "Package Stack"

Jump to navigation Jump to search
2 bytes added ,  15:24, 5 October 2016
m
→‎Summary: you remove the ones unavailable...
imported>Henning
m
 
imported>SarthesArai
m (→‎Summary: you remove the ones unavailable...)
 
Line 6: Line 6:
This stack is formed by adding Alias Package Lists to the top of Actor Package Lists which are added on top of default package lists.
This stack is formed by adding Alias Package Lists to the top of Actor Package Lists which are added on top of default package lists.


After processing all the packages' schedule and [[:Category:Conditions|conditions]] and removing ones which are available during the current day/time or whose conditions evaluate to false, the actor picks the top most package left on the stack.
After processing all the packages' schedule and [[:Category:Conditions|conditions]] and removing ones which are unavailable during the current day/time or whose conditions evaluate to false, the actor picks the top most package left on the stack.


This is a very powerful (if at first confusing) way to organize an actors set of behaviors, because you don't have to poke an actor every time he needs to do something else. The dynamic stack of packages is constantly updating based on schedules and conditions of individual packages causing them to be removed or returned to the stack.
This is a very powerful (if at first confusing) way to organize an actors set of behaviors, because you don't have to poke an actor every time he needs to do something else. The dynamic stack of packages is constantly updating based on schedules and conditions of individual packages causing them to be removed or returned to the stack.
Anonymous user

Navigation menu