[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] new feature request
- From: Carl Cook <carl@xxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 10 Nov 2005 18:32:29 +1300
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references; b=tqCfePtQR26XUD/FmSbSfivd5Yt79ptlX5TWa3IrqVvr03z2849p2r+YtlpO2aiT9QRCzGXL19dhLNmYND3NGVVa7RpjC0PolV84ztXbc2mRxSmChV+VRvu9PHbMaEnUfyLGrx9S1RRokxRm4LYXqmBABwkahJJsNHJGS1kTIe4=
Hi Boris and Scott,
>>If you have any questions about editors etc., feel free to send them my way.
> OK, thanks. One question: Do you think that using markers (where we
> introduce the notion of a marker that is added by a remote user) would
> work? Or should we just pass around selection offset and range for the
> time being and scroll/set selection for the time being?
From painful experience in writing groupware widgets, markers are the only way to go! Using selection offsets gets into all sorts of problems in real-time file sharing, especially when the order of actions between collaborating users can not be predicted in advance. There is nothing worse than sending an offset for a modification only to have someone at the same time change the text above the current cursor position.
I have quite a fair bit of experience in writing such widgets (including the MVC side of things), so if I can help at all with the high-level design, please just post back some questions!