Community
Participate
Working Groups
A problem with the shared editor in the collab example is that there is no history. If a participant opens a shared editor the receiver does not have any record of that shared editor opening, and no way to 'replay' that event under there own control. The shared editor in the ECF collab example can use the following features: 1) The display of editor opening and editor selection events in the chat text output (as hyperlinks) 2) The ability to have the receiver click on the hyperlinks and to locally (and/or remotely) 'replay' the event. 3) Allow the receiver to specify (as a preference) whether the received events will be immediately executed (as the shared editor is now) OR not immediately executed by presented in the text chat history 4) Provide some additional UI for specifying what events (and associated resources) to share (e.g. key board?)
I have released a class org.eclipse.ecf.ui.views.SimpleLinkTextViewer that wraps a StyledText and supports appending text and clickable links. When appending a link, you provide the link text and a Runnable that should be run when the user clicks on the link. I haven't changed ChatRoomView, but there is a main() in the new class for testing.
I have released code that does (1) and (2) for the "Share Selection" action. Clicking on the link replays the event locally. Scott/Ken: Over the next few days, I am too busy with the upcoming M4 of Eclipse and won't be able to contribute more.
Parts 1-3 of this bug/enhancement request now implemented, checked in, tested. Will be in stable release build 0.5.4 (12/11/05). Part 4 will be added as another enhancement request
*** Bug 119569 has been marked as a duplicate of this bug. ***
Just fyi, at the core of Mylar is a very simple interaction history model. Externalized it's just a stream of events in the following form: <InteractionEvent Delta="null" StartDate="2005-12-13 19:01:29.536 PST" EndDate="2005-12-13 19:01:29.536 PST" Interest="1.0" Kind="edit" Navigation="null" OriginId="org.eclipse.mylar.java.ui.editor.MylarCompilationUnitEditor" StructureHandle="=org.eclipse.mylar.ui/src<org.eclipse.mylar.ui.actions{AbstractApplyMylarAction.java[AbstractApplyMylarAction~getViewers" StructureKind="java" /> It's currently being used to create the interest model that shows up in the UI, and for analyzing usage patterns offline. It would be straightforward to use this model for replyaing interaction, as long as
(please excuse the previous partial post) Mylar has a bunch of support for working with these interaction history streams (e.g. to turn them into the interest model that drives the Mylar UI). It would be straightforward to use this model for replyaing interaction, as long as the same resources existed in both workspaces. This may be more than you need right now, and it may not be worth coupling to mylar.core, but I wanted to put this on your radar because there is interesting overlap here and that part of Mylar can be used independently of the task management and UI.
