Listing of developer traces

The following are the developer traces resulting from the experiment. A description of the contents of the traces is found further below. Note that these are not currently conformant XML as they do not have a surrounding top-level pair.

• First Task (T1): The first task was always performed with Eclipse.
  • First task was Autosave: 01, 02, 03, 07, 08, 12, 13, 14, 18
  • First task was Settings-Reloading: 04, 05, 06, 09, 10, 11, 15, 16, 17
• Second Task: performed with either JQuery, Suggestions Plug-in, or Ferret.
  • Second task performed with JQuery
    • Second task was Autosave: 04, 10, 17
    • Second task was Settings-Reloading 01, 07, 13
  • Second task performed with Suggestions Plug-in
    • Second task was Autosave: 06, 09, 15
    • Second task was Settings-Reloading: 02, 12, 14
  • Second task performed with Ferret
    • Second task was Autosave: 05, 11, 16
    • Second task was Settings-Reloading: 03, 08, 18

Description of the Trace Format

The JavaEditorViewportMonitor causes editor changes to be recorded as selection events, with the delta containing an XML fragment such as:

<interactionEvent>
    <kind>selection</kind>
    <!-- other tags elided -->
    <navigation>scrolling</navigation>
    <delta>
	<scrolling removed="23 " added="64 " visible="24:26 31:64 ">
	    <newlyVisibleElements>
		<handle kind="java" lines="41:150">
		    =jEdit-4.1pre6/&lt;org.gjt.sp.jedit.options{LoadSaveOptionPane.java[LoadSaveOptionPane~_init
		</handle>
	    </newlyVisibleElements>
	</scrolling>
    </delta>
</interactionEvent>

There are four types of delta, corresponding to the navigation type:

<opened>

this part (an editor) was newly opened

<brought-to-top>

the part was just brought to the top

<folding>

there was a folding change, resulting in either an expansion or contraction in content

<scrolling>

the part was scrolled

All delta types have three attributes. The added and removed attributes report the change since the previously reported delta. The visible attribute summarizes what is currently visible. Each attribute reports a set of space-delimited numbers representing line ranges.

The delta also reports the handles of the domain-specific elements that were added as a result of the change (where available). This is a delta from the previously reported changes, and is listed in the <newlyVisibleElements>...</newlyVisibleElements> tags. Each handle represents some domain-level element (the domain is contained in the kind attribute); the handle's lines attribute provides the line range containing the elements definition.

The example above reports that a part was scrolled, with line 23 disappearing, line 64 newly appearing, and the net result being lines 24 through 26 and 31 through 64 are currently visible. The scrolling revealed more of an element (from its lines attribute, we can determine that part of the definition was previously visible).