LINK√∂PING GUIDELINE DEMO HACK >>

1 - 3 - 25

>> Visual Encoding

  1. Position, size, and colour variations always have meaning in every view - e.g. >> Munzner (2014)
  2. Move things to counter occlusion - e.g. >> BikeGrid (Wood et al, 2010); >> LondonSquaredMap (AfterTheFlood, 2014)

>> Control

  1. The data is the interface - e.g. >> PivotPaths (Doerk et al, 2012); >> PlaceSurvey (Slingsby et al, 2014); >> SketchStory (Lee et al, 2013)
  2. Controls appear only when you need them and in context - e.g. >> Bertifier (Perin et al, 2014)
  3. Need is determined by location (cursor | eye | data)
  4. Always have a description of configuration in natural language - e.g. PlaceSurvey (Slingsby et al, 2014); >> Glo-STIX (Stolper et al, 2014)
  5. Physical objects and data may interact in interesting and useful ways - e.g. VeniceUnfolding (Nagel et al., 2010)

>> Cross-View Interaction

  1. Moving containers (view and token) to different places has effect - e.g. >> LiquiData (Nagel et al., 2011)
  2. Data can be selected and transferred from one widget into another - e.g. >> OnSet (Sadana et al, 2014).

>> Process

  1. Start with "what's new"? - e.g. PivotPaths (Doerk et al, 2012)
  2. Keep your eyes on the data - e.g. Tangible Remote Controllers (Jansen et al., 2012)
  3. Workflows can be saved as a template in order to be applied to other data - e.g. DIVA (Walker et al., 2013); Glo-STIX (Stolper et al, 2014)

>> Things We Don't Say ...

... deliberately in some cases ...

  1. How to Achieve Consistency
  2. Interactions & Conflicts
  3. Anything Specific
  4. How we expect you lot to contribute | react to this 
  5. Various Other Stuff ...

valcriWidgets.png