If a node requested to delete by a WS command doesn't exist, don't log or report an error. It's probably just bad UI timing that the request was sent, so the server-side status is just fine.
Changed order how created and deleted nodes are handled.
This fixes some problems with the actions of DOMNode#appendChild not being executed in the proper order.
Now deletion is handled before creation which should fix it.
The root problem is that Neo4j's TransactionEventHandler doesn't know the order of the events in the queue.
Some further UI improvements.