|
| From: | Torben Hoffmann |
| Subject: | Re: [O] colorg: Protocol [was: Re: Rudel - Real-Time collaborative editing of Org-Mode files] |
| Date: | Mon, 1 Apr 2013 22:46:24 +0200 |
Samuel Loury <address@hidden> writes:Yes, of course. My goal is getting some solution, not creating my own
> But instead of creating your own protocol, have you thought about
> extending an already existing one?
thing. I only tried to look at the internals of Rudel and
Etherpad-lite, and also to read some literature on the topic, starting
with Wikipedia. In all cases, I felt stupid and overwhelmed. :-) This
is not simple, as far as I can see.
Besides Rudel, no.
> I see that you have read negative comments about tools using the obby
> protocol, but have you read about the protocol itself?
While not being fully sure, I think I have some understanding of the
> By recreating a new protocol, you might be facing the same issues in
> synchronization that gooby faced at some time and spending useless
> effort trying to fix it.
problem, and the solution I have in head might have no issue. Its
optimization is going to be a bit hairy however, and there lies the
danger for introducing errors. My fix would then be to not optimize, so
with at least an inefficient solution, the effort is not useless. :-).
Because of the bad press, which gave me the unverified impression that
> As far as I can see, the only thing that appears to be missing in the
> obby protocol is the possibility to move entries without deleting and
> reinserting. This makes sense since it is specific to outlined
> documents. Why not adding this feature to the obby protocol?
by adopting Obby, I would have to spouse its problems, and get to solve
them. I guess people much more brilliant than me already tried, and
failed or abandoned, so I just have no chance of succeeding :-).
It sounds important to me, for Org mode, to support some "Move Block"
operation, which combines delete and reinsert the same contents as a
single operation instead of two, as I suspect this is frequent when
someone is reorganize an Org outline, and I would ideally like that
people editing within a block which is being moved by someone else does
barely notice s/he is being shuffled elsewhere. This is an Org
specialty, that is unlikely part of other protocols, and this
consideration pushed me into attempting something. Not that I currently
have a "Move Block" operation in the protocol, but it should be easier
to add to something that I well understand.
I also got quick failures in my tries, of many kinds.
> By the way, I tried this week end gobby server 0.4 and rudel client
> (last git version) and it did not manage to connect to the gobby server
> while a gobby client 0.4 succeeded. So sad...
> [1] http://gobby.0x539.de/trac/wiki/AnnotatedObbySession
Thanks for this one, which I did not see. I'll take a closer look!
I'm saving these messages and recycling their content on the Wiki. I
> If the obby protocol or any other RTCE protocol does not fit your needs
> causing the creation of a new protocol, I think it would be a good idea
> to write why on your wiki page.
should get more documentation on the Wiki, but did not have much time
since I started, Friday evening, as I rather wanted to push on the code
to have by Sunday at least some skeleton that moves a bit. And even
then, I took the time to move some previous comments to the Wiki, and
explain at least the current state of protocol. Documenting early helps
at avoiding design errors.
Ista Zahn published a working solution on the Wiki, that one could use
> I can't wait to see RTCE of org document!
if in a hurry. It is said to work well, see:
https://github.com/pinard/ColOrg/wiki/emacsclient
François
| [Prev in Thread] | Current Thread | [Next in Thread] |