|State of ECF [message #614889]
||Sat, 14 April 2007 16:46
Originally posted by: vansickle.gmail.com|
I play with current version of ECF, and found that it works good for
chatting, for example, in xmpp/gtalk - and i see in plan what work done
in this direction.
But for me more interesting is collaboration feature - and particularly
collaborative work on project files. I try to create shared work on text
files - without any success - so what ecf for now able to do and what not?
|Re: State of ECF [message #614891 is a reply to message #614889]
||Sun, 15 April 2007 03:06
| Scott Lewis
Registered: July 2009
Pavel Samokha wrote:
> I play with current version of ECF, and found that it works good for
> chatting, for example, in xmpp/gtalk - and i see in plan what work done
> in this direction.
> But for me more interesting is collaboration feature - and particularly
> collaborative work on project files.
Our example collab application (bundle org.eclipse.ecf.example.collab)
allows the sharing of workspace resources.
>I try to create shared work on text
> files - without any success - so what ecf for now able to do and what not?
The ecf shared text editing does work...actually in two different ways:
1) by simply launching an editor (java editor, text editor, etc) on a
given workspace resource (this is probably what you tried in the ECF
2) a very simple shared real-time text editor example
Here's some wiki info for the latter:
Also, last summer there was a Google SOC project by Mustafa Isik on
using operational transformations for supporting synchronized real-time
text editing. See http://wiki.eclipse.org/index.php/RT_Shared_Editing
The code for this work is available also, but we are not yet deploying
it as part of the ECF examples because of the Eclipse Foundation IP
approval process, and because it wasn't/isn't complete in some important
There has been a lot of interest in a full-feature shared editor, and
ECF's messaging APIs (datashare and sharedobject) can/would support such
an application very well...as the messaging APIs provide the necessary
message ordering and reliability semantics for implementing reliable
state replication and synchronization.
Up to now, we've not had resources sufficient to undertake such a
sub-project (as unlike most Eclipse projects ECF has no corporate
support), and there have not been any significant community
contributions in that area so far. All offers of contributions and or
assistance for undertaking this sub-project would be most welcome. Even
better, if a member company would sponsor work on such a thing, we
could/would do it quite quickly.
Powered by FUDForum
. Page generated in 0.16563 seconds