The Proof Is In The Pudding

They say the proof is in the pudding so I decided to try to make sense of the mass of documents in my folder for the 9 month report by taking it from this:

 

 

To this, using Scapple:

 

I’m sitting in the Groucho’s lobby working for a few minutes before the Big Guys Gather for the Little Guy dinner (me and my male friends having a boy’s baby shower since Emily decided to wait for a gathering until after Kazu is born), so I will be working on the logic and layout for this tomorrow. Already some patterns are beginning to show, but I have to close my laptop soon. Here is what I have the following Tuesday:

 

What became clear when working on this is that it does not really reflect a logic of a word processing document – the bold headings on the left hand side are the categories/sections I should be using for this document, but here they are just indications. I therefore decided to make the bold level one headings and have the ‘document’ presented as columns, each for a level one heading, 4 headings wide and this made much more sense:

The lines are still just reminder lines for me and there are a few headings/nodes which are not under a level one heading (for example; ‘A Personal Note on the Process’) which would be at the very end of the document in word processor view.

This leads to a couple of insights/ideas

The default layout of liquid view should not be the same as Table of Contents view.

The user should be able to specify automatic layouts for the level one view, such as the grid shown here (by keyboard 1,2,3,4 to indicate the number of columns), in the same way the user should able to choose to ‘Align vertical’ and so on.

 

Ray McAleese

Ray McAleese, from the University of Aberdeen, refers to that the process of making knowledge explicit, using nodes and relationships, allows the individual to become aware of what they know and as a result to be able to modify what they know.

“Being able to move information chunks around, to group them and connect them makes “the process of making knowledge explicit, using nodes and relationships, allows the individual to become aware of what they know and as a result to be able to modify what they know.”
(McAleese)

Paper Liquid Views

I thought it would be useful to play with paper cut-outs of the liquid view since I keep talking about how it should feel ‘tangible’.

Here is a document with a heading and body text illustrated with horizontal lines.

 

I then pinch to fold away the body text under the headings. This is an important step since the liquid view will only feature headings, not body text so the body text needs to be removed in both the liquid view and the table of contents pinch (as we are doing now:


And in the liquid view I can move the headings around:

 

And use more of the screen space:

 

And connect headings:

 

So that is what it looks like on paper. How can the user now toggle back into word processing view and then into TOC or liquid views?