search

ZeusWPI / MOZAIC

MOZAIC is the Massive Online Zeus Artificial Intelligence Competition platform
GNU Lesser General Public License v3.0
13 stars 6 forks source link

Internal game state to visualizer converter #208

Open tl3ilaxu opened 6 years ago

tl3ilaxu commented 6 years ago

The client should send information to the vis. We should assume the vis has stateless behaviour.

wschella commented 6 years ago

Wait, can we assume the vis is completely stateless? There's like control things right?

tl3ilaxu commented 6 years ago

The vis will obviously have a state. However that state should be totally detached our internal state, so we should assume statelessness for flexibility sake. Control things are solved by allowing the vis to emit events. #209 This emission is optional because not every vis will need a loopback. (ours does, bc controls)

wschella commented 6 years ago

If i understand correctly, you would make the visualizer emit control-events, and let those be handled by a control wrapper around the visualizer, which loads the visualizer with the corresponding arguments?

tl3ilaxu commented 6 years ago

Pretty much!

iasoon commented 6 years ago

@wschella cfr how react components are 'stateless' when used in redux: they can have state, but it is discardable. Also, vissen hebben geen toestand.