CONNECTION

[TodePond]

I think it's worth just doign the UI for this first, and after getting a global tick + node thing going

[TodePond]

I think we need some better names for this...

ok so in CellPond we had this...

CELLPOND was the cellular automata engine. DRAGON was the virtual machine that ran cellpond. COLOURTODE was the ui that you used to write dragon machine code.

in Arroost, let's now name those same things...

ARROOST is the game engine, which runs the ui. NOGAN is the underlying virtual machine that contains and runs the node computer.

actually maybe it's worth doing this order:

1. design NOGAN
2. implement the connection ui for ARROOST
3. implement NOGAN

[TodePond]

NODE

• id (number)
• layer (number)
• type (string - contains hit test info, and fire behaviour)
• data (eg: audio buffer, eg: control level)
• inputs (array of wire ids)
• outputs (array of wire ids)
• position (x, y)
• firing??? (bool)

WIRE

• id (number)
• source (node id, wire id, or location)
• target (node id, wire id, or location)
• time (before, same, or after)
• colour (red, green, or blue)
• firing??? (bool)

[TodePond]

actually ive started on NOGAN first. I think I got this!

[TodePond]

do #38 first

[TodePond]

Still todo: Slots at start and end of arrow of time!

[TodePond]

connection now spawns slots. i think thats maybe ok now!?