» The Wittgenstein Browser
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

The Wittgenstein Browser


A prototype for the spatial display and gestural navigation of large hierarchical datasets


Even with the advent of new digital technologies, the traditional book still stands out prominently among devices which allow us to find, index and store information in a relative compact and handy space. This data storage and retrieval system is in fact so successful that it has been utilized over centuries and that its usage and internal workings have somewhat become second nature to humans.

In one way or the other even most digital information systems (for example Websites or PDA and Cellphone interfaces) make use of the characteristics and paradigms that are typical for the analog book. For instance, even though there is no such thing as a physical representation on a Google search return, we speak of a "page". The pages are numbered. We read them from upper left to lower right scanning one search item after the other. We "flip" them back and forth as represented through left and right pointing arrows, and, similarly to the book, we even get a short interruption in the flow of information when we go from one page to the next.

While this form of data representation has arguably many advantages (convention being among the strongest), it also brings with it some issues. Firstly, the eye is generally much faster than the hand. To stay with the Google example: It takes the eye usually no less than a few fractions of a second to scan a "page" for relevant bits of information, yet it takes comparably much longer to move the mouse to the "next" arrow, click it and wait for the next page to load. Secondly, digital representations of larga datasets such as Google search returns, rarely visualize how MUCH overall information the user is confronted with. A book communicates before we even read one sentence in it through its thickness. We do get an immediate sense of differentiation when putting a book with 100 pages next to one with 1000. Depending on our attitude a very thick and heavy book could stand for "Wealth of information", or it could make us think: "Oh my God! Do I really have to read all of that?". No such visual cue is given us through Google's search return number.

Finally, as books (and models which rely on the book paradigm) are by design read in a linear fashion (front to back, upper left to lowr right) they do not lend themselves naturally to highly crossreferenced and nested information which
relies more on vicinity of related information rather than on strict succession.

One prime example for the book's shortcommings in accommodating for this type of information is Austrian philosopher Ludwig Wittgenstein's famous Tractatus logico-philosophicus (subtitled Philosophical Remarks), first published in 1921 as part of the magazine Annalen der Naturphilosophie, and later in various book formats. This text, which despite Wittgenstein's rather laconic and succinct language, is quite difficult to decipher, deals foremost with the relation of language and thought, logics and ideas and tries to establish a set of "true" and incontestable propositions which interdepend on each other and strive to be totally devoid of any metaphysical subtext.

For our project the interesting part is however not so much the content, but more the way Wittgenstein has structured his text: There are seven main propositions (numbered 1 through 7), with various sets of subsidiary references (1.2, 2.1, 2.1.1 etc). The ordinary book form doesn't do this text much justice as the weight and prominence of the different statement levels (as given by the numbers) cannot be visualized due to the inherent linearity of the design. For instance, statement 3, which is on the same "level" as statement 2, might actually appear only pages after point 2, depending on how many sublevel items are grouped under point 2 (2.1 2.1.1, 2.2 etc). In other words, the relation of points to each other and their particular location withing the hierarchy is lost to the reader sooner rather than later.

Of course, the Tractatus stands here only as a model for any text scientific or not which is structured hierarchically. Texts which are purely linear (as novels for instance) are not subject of our investigation.

As a start we have formulated several requirements and prerequisites this application has to implement in order to be successful:

  • Readers should get a visual cue as to how much information is available to them in total and how much is in each section
  • We will utilize depth (the z-Axis) as an alternate means of grouping relevant information together
  • The movement in the application space as well as the relation of items to each other has to be logical and clear at any time
  • Moving from one state to the next has to be swift and without any interruption in the flow of the presentation (no "reload" effect)
  • The reader, not the application's design, should determine the speed of the reading
  • There should be no limitation as to the actual speed. Each user should be allowed to read as fast as they please
  • Navigating the information set and moving the screens will be achieved through gestures
  • There should be no more than 4 different gestures required to do everything that is possible within the application
  • Each gesture should do one thing, and one thing only
  • The gestures have to be self-explanatory, natural, and comfortable.

Please add points as you like

TN 03/2006


    http://www.multiblah.com/pmi http://riot.com.au/systems.php?s=b1 http://www.generation5.org/content/2004/aiGesture.asp http://video.google.com/videoplay?docid=-4429962219581954672&q=kartoun

anonymous user login


~1mth ago

mediadog: @ggml Yup, lots. Only used in 4.x, haven't tried in 5.x yet: https://www.unrealengine.com/marketplace/en-US/product/simple-udp-tcp-socket-client

~1mth ago

ggml: someone has sent udp bytes to unreal ?

~2mth ago

micha_nismus: worked out, thank you very much ! :-)

~2mth ago

joreg: @micha_nismus does this help? https://youtu.be/xkrbT45BgOQ

~2mth ago

micha_nismus: thx joerg. Can anybody help me why i can't see any renderer in gamma? thx :-)

~2mth ago

joreg: @micha_nismus instead of discord, we're using matrix, see: chat

~2mth ago

micha_nismus: searching for a public discord server for vvvv

~2mth ago

joreg: Join us for the 20th #vvvv meetup on January 19th: https://thenodeinstitute.org/event/20-worldwide-vvvv-meetup/

~2mth ago

joreg: @schlonzo re "SDSL support" did you see the Shader wizard? or do you mean something different?