1 / 13

S eeThroughTalk

S eeThroughTalk. A new collaborative programming environment. 2003 Masashi Umezawa. Contents. Main Concept Demo Future Plan Q&A. Programming is fun (especially in Smalltalk). Smalltalk programming brings us a lot of fun Why? Dynamic interactions with the system magnify our imagination

shoshana-klein
Download Presentation

S eeThroughTalk

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SeeThroughTalk A new collaborative programming environment 2003 Masashi Umezawa

  2. Contents • Main Concept • Demo • Future Plan • Q&A

  3. Programming is fun (especially in Smalltalk) • Smalltalk programming brings us a lot of fun • Why? • Dynamic interactions with the system magnify our imagination • A creative way of thinking • Like growing another brain in a machine • But…

  4. Smalltalk image is a lonely place • Smalltalk image is too personalized • It does not support image sharing • Developing ideas deeply relates to exchanging ideas • Although great breakthroughs are often done by talented individuals’ intensive work, • we should not underestimate the power of team interactions

  5. Traditional team programming environment • Software Configuration Management System (SCM) • CVS, SCCS, PVCS, etc. • It only focuses on “source codes”, not people • We need a real “team” development tool • It should support dynamic interactions between other members, while keeping private working spaces

  6. “See Through” desktop interface • Overlapping windows → Overlapping desktops • People can see the activities of other members in an easier manner • It enables on-demand interactive programming sessions

  7. What desktop translucency represents: • It supports ‘Ma’ with other members. • If interactions are rare, the desktop will be blurred • If there are frequent interactions, desktop will appear clearly

  8. Avatar interface • Avatar visualizes each developers various states • User feelings - excited, sleepy, embarrassed, etc. • User status – connected, causing conflicts of sources, etc. • It naturally reduces communication overheads

  9. Automatic source-changes propagation • Merging change-sets is a tedious work • Each member’s changes are instantly propagated to other members • No need to merge things! • It is sometimes dangerous, so you can manually detach the propagation

  10. Demo • Desktop sharing • Interaction between remote users • Automatic change propagation

  11. What we have done… • New desktop sharing system • Modern, modularized version of Nebraska • Remote desktop display • Remote cursor control • Each can be used independently • Basic change propagation mechanism • Hooks are added to ChangeSet • Source changes are raised as events • Avatar morph • Pluggable animation

  12. What we will do • Category-changes propagation • Need to adopt “SystemChangeNotification Package” • More sophisticated avatar interface • Currently, avatar’s pop-up menu is rather complicated • True smooth, fast, “SeeThrough” desktop • Need to solve a “display-looping” problem • Optimization of processing damaged rectangles • More GUIs for remote user sessions • Chat interfaces • Integration with “Monticello”?

  13. Questions?

More Related