Talk:NodalHusk.c

Here i'm trying to set out in a formal way, the initial contents for a nodal structure that will define some part of the user interface. By filling the space with some data we can see what hard-wired functions are needed. I am basing the data on the existing example in SDL.c.

• Interface # interface super-container
• Interface:Display

• Display # display node
• Display:Surface

• Surface # surface node
• Surface:x
• Surface:y
• Surface:width
• Surface:height
• Surface:background-colour

• background-colour:0x8000ff00 # green with alpha
• x:50
• y:50
• width:200
• height:100

--Rob 14:51, 20 Jul 2006 (NZST)

Those properties should cover it - the first stage is to have a nodally reducable list of interface container nodes (which are currently just coloured rectangles with no children). The order in the list determines their z-ordering since they're drawn in that order onto the root-surface.

So we have two root nodes, interface and network, the contents of interface is a list of containers, and the content of network is a server node and a clients node. The clients node contains a list of zero or more client nodes. Each client contains stream and security info etc. --Nad 15:04, 20 Jul 2006 (NZST)

p.s. the reason to have the clients containing the list of client nodes rather than bundling the list in with the server is that when the structure undergoes reduction, the calls to server() will be multiplexed (interleaved) with each of the calls to client().

Updating the above structure to include interface - which contains display as we may have several displays. The numbering in the example is going to get messy, but it can be renumbered efficiently by using the tri-hash I imagine --Rob 15:28, 20 Jul 2006 (NZST)