edu.stanford.hci.r3.pen.batch
Class BatchedEventHandler

java.lang.Object
  edu.stanford.hci.r3.pen.batch.BatchedEventHandler

public abstract class BatchedEventHandler
extends java.lang.Object

Reads in XML request files as Ink objects. TODO: We need to change this to allow for real event handling, after the fact. Basically, we could allow a user to "play back" the batched events, if necessary. They could accomplish this through a slider or something (as a debugging environment). Would this be useful for the end user too? Imagine if the end user saw the stream of events, and could see which event handlers were actuated when. Maybe we can cancel some strokes (after the fact)? For example, if the system recognizes a TODO somewhere, we might want to cancel that event. TODO: We should also change this to parse XML "for real", so we can get at attributes such as the segment, shelf, book, page, etc...

This software is distributed under the BSD License.

Constructor Summary

BatchedEventHandler(java.lang.String theName)
Create an Event Handler for reading in Batched Ink Files, synched over USB.

Method Summary

void	batchedDataArrived(java.io.File xmlDataFile)
abstract void	inkArrived(Ink inkOnThisPage) Handlers will get this notification for every ... that is read in from disk.
java.lang.String	toString()

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Constructor Detail

BatchedEventHandler

public BatchedEventHandler(java.lang.String theName)

Create an Event Handler for reading in Batched Ink Files, synched over USB.

Method Detail

batchedDataArrived

public void batchedDataArrived(java.io.File xmlDataFile)

Parameters:

xmlDataFile -

inkArrived

public abstract void inkArrived(Ink inkOnThisPage)

Handlers will get this notification for every ... that is read in from disk.

Parameters:

inkOnThisPage -

toString

public java.lang.String toString()

Overrides:

toString in class java.lang.Object

See Also:

Object.toString()