Minutes for June 4, 1998

• Recorder: Raphen
• Start: 13:32
• Stop : 14:25

Preliminaries

• Sam put the minutes up from yesterday.
• Sam canceled his trip to Germany so he could spend more time with his family and with us.
• Next week will be even more crazy for Sam, but things should settle down soon.
• Next meeting will be on Monday at noon!.

HyperWave

Sam heard from HyperWave. The problem is known but undocumented. They did give him a workaround, which he will try.

Annotation Subsystem

• http://www.math.grin.edu/~luebke/mockups/SampleMarginalAnnotation.html
  • Put buttons after the annotation
  • Many annotations creates lots of clutter
• http://www.math.grin.edu/~luebke/mockups/AnnotationOnPage.html
  • Make font size of annotations smaller * http://www.math.grin.edu/~masonh/mockups/popup_a.html
  • Asks for security permissions and has the windows always on top
  • When there are multiple annotations per window, each should have a reply button, but just one new annotation button for the window
  • Unfortunately, this seems to start Java and doesn't seem to work consistantly.
• http://www.math.grin.edu/~masonh/mockups/popup_a2.html
  • The popup window is not kept on top
• http://www.math.grin.edu/~masonh/mockups/popup_b.html
  • Asks for security permissions and has the windows always on top.
• http://www.math.grin.edu/~masonh/mockups/popup_b2.html
  • The popup window is not kept on top
• http://www.math.grin.edu/~masonh/mockups/newpage.html
  • Annotations listed in a new page, without reference
• http://www.math.grin.edu/~masonh/mockups/newpage2.html
  • Annotations listed in a new page, with reference
• http://www.math.grin.edu/~masonh/mockups/colors2.html
  • Uses the spiffy change-background-color-to-hide-annotate-button
  • Have the add annotation button start out totally invisible and then changed with JavaScript to a visible icon, instead of changing the background.

Things to do:

• Send a note to all of the research students and profs asking them to spare 10 min to come and give their insight about the annotation system interface.
• Start thinking about handling groups and annotation trees.

Important considerations:

• How many "places" are automatically annotated? Do we have annotations for every paragraph (and list item) or every section or?
  • If they're small enough, every paragraph might work.
• How do we deal with multiple followups to the same comment? There's a tendency to do "threads", but an annotation tree (or perhaps graph) may be better.

Logging Subsystem

Kevin explained his picture. Sam had questions about why Clio connects to the Perl Print Thread instead of a Client like the Java applets.

Kevin has most of the pieces coded already, he will work on Clio creating a socket with the HyperServer.

Analysis Subsystem

Raphen is working on writing classes that read and interpret the log files. He should start thinking about converting the log files to a MacSQUEAL type format, and the type of analyzing to allow.