Difficult to parse Storage Contents

[JoshOrndorff]

The storage contents, which can be expanded in the right panel, contains items from several runs from different users. Typically the majority of the contents is filled with runs from the example Hello World contract that is populated by default. It is quite difficult to find contents that I'm actually interested in.

This combined with #13 makes it quite challenging to actually see the results of the rholang code I'm running.

Possible fixes may be:

1. A separate container for each session
2. Allow filtering on the tuple space so I can easily inspect the channels that I care about.

[tschoffelen]

As explained in #13 I don't think a separate container for each session is a possibility right now with the way the nodes work (and their startup time).

I guess we could calculate the diff between the previous run and the result of the current one and only show that diff, but I don't know how well that would work (in theory executions are queued, but of course contracts are executed concurrently, so a contract created hours ago could in theory still change the tuple space).