RE: [ecf-dev] Shared Editor Usage Scenarios

["Gary Pollice" <gpollice@xxxxxxxxxx>]

As an instructor, one of the things I regularly do with  my students is talk to them over a chat client when I'm at home and they're in their dorm rooms or in the lab working on an assignment. I often have to have them email me their code so I can look at what they're saying. One of the reasons I want a shared editor in the collaborative environment we're building, based upon ECF, is that in such situations I, or one of my TAs, can establish a session with the student to see exactly what they're trying to do, have them explain it while they show me, and then to possibly insert code into the file so they can get started on the right path.

 

    --Gary

---------------------------------------------------------------------------------
Gary Pollice                                    gpollice@xxxxxxxxxx
Professor of Practice, Computer Science         gpollice@xxxxxxxxxxxx (alternate)
Worcester Polytechnic Institute                 Office: 508-831-6793
100 Institute Road                              Mobile: 978-798-0019
Worcester, MA 01609-2280                        <http://www.cs.wpi.edu/~gpollice/>

---

From: ecf-dev-bounces@xxxxxxxxxxx [mailto:ecf-dev-bounces@xxxxxxxxxxx] On Behalf Of Ken Gilmer
Sent: Friday, May 12, 2006 12:48 PM
To: Eclipse Communication Framework (ECF) developer mailing list.
Subject: [ecf-dev] Shared Editor Usage Scenarios

Hello,

  I've been thinking about various ways groups might use shared editing.  My initial (base) use case was a distributed development team, perhaps in a design meeting or doing code review.  However I can think of a few other scenarios.  These scenarios also imply better sharing models:

1. Instructor use case.  In an education context, one peer may have exclusive write access to an editor, others would be read only.  Additionally, file open/close actions on the instructor node would propagate to "student" nodes.
2. Document collaboration use case: A document (rtf, etc.) is being edited by a group.  Higher levels of locking semantics are required, as these people are not developers (or even if they are) and may be confused by free-for-all shared editing.
        a) A token style workflow, where the user with the token can edit, and can also pass the token to other users in the collaboration context.
        b) A lock style workflow, where a user locks a portion (paragraph?  line item?) of a document.  Others cannot edit until locker unlocks.


Any thoughts?  Any other use cases people can think of?  I may work on implementing these in the shared editor if they seem of value to others.

Thanks
Ken