Add example message log
Simulate two logs
Inherit common model elements from BaseModel

Model adapters like Messages, Nodes and History are to inherit common elements from BaseModel class.

In terms of OOP patterns, there is a number of patterns to implement this in Javascript, and I am going with the Constructors-everywhere one.
Here is a good overview of it:
http://javascript.info/tutorial/all-one-constructor-pattern
Draft loading messages
Move definition for NetVis.Render() to View section

jbenet wrote that:
one thing to keep in mind while building the code for this is to keep "the simulator"
and "the animation" separate in the code, so we can swap out rendering later
(i.e. shift between "circle view" (great for understanding protocols, and for small networks),

and it makes sense to me.

So now I am trying to put all the rendering and representation specific things into the files within the view directory.

And all the controller-apropriate definitions to controller directory.
Clean up some general crud leftovers
Move all trace parsing-related stuff into parse/ dir

Parsing/deserializing/unmarshalling things in NetVis format goes to parse/ directory.

Potentially, whenever one needs to add parsers for various other formats, only this section will need rewriting/additions.
Link messages to Node instances when parsing them
Delete redundant node ids in message objects when recognized
Render messages on canvas
NetVis format file example in the event log style
Parse event loop with custom handlers
Add loggerID attrs to example NetVis trace
Initialize node instance from all node IDs mentioned
Scaffold history model handler
Select messages by clicking on them on canvas
Clicking on selected item cancels selection
Add lower and upper timestamp bounds
Make message strokes more prominent
Assign eventID as timestamp#count where count is # of events with same timestamp