Versions

Versions as milestones

Version 1.0

TBD: Not yet in work. First self running version with no vehicled stacks. Moving containers randomly.

TBD: Collision control of cranes with stacks reachable by other cranes to. The idea is to pause the colliding container tasks until one task is ready.

Version 0.2

TBD: For a crane object the dispatcher calculates if yet registered stacks are reachable and retours a list of reachable stacks with a "DISPATCHER","EXISTING_REACHABLE_STACKS,StackGOIDListSoup message. If a not yet registered stack will be appended or updated a "DISPATCHER","APPEND_REACHABLE_STACK,StackGOIDSoup.

TBD: For stack objects the dispatcher calculates if yet registered cranes may reach it and posts the message "DISPATCHER","REACHABLE_STACK" to fitting cranes with appended goid as an one tag soup and reposts the list of crane goid's with the message "DISPATCHER","CRANES_REACHABLE" with the appended goid list as soup.

TBD: For registered container objects the dispatcher reproofs the stack. Unregistered containers will be appended randomly to a stack and if there is yet no stack it will be informed to re register sometimes later again.

TBD: Messaging while moving containers from stack to stack.

Version 0.1

TBD: Moving of animated parts.

The asset instances of containers, stacks and cranes load their config parameters and their soups.

After finishing their Init and SetProperties methods and if the "World","ModuleInit" message was sent they post their "REGISTER","REGISTER_ME",ObjectDataSoup message to the dispatcher.

The dispatcher reposts after processing the registering a "DISPATCHER","UPDATED"/"INSERTED"/"APPENDED",ObjectDataSoup message. The registering process updates registered object's data or inserts/appends yet not registered object's data.

• The used Blender files as zip archive: File:ACTS 215489 Blender Files V0.1.zip

• The used Asset Source files as zip archive: File:ACTS 215489 Asset Files V0.1.zip