AntiSyncroEditIdea.

Thought the RealTimeTopicEditPluginIdea seems for me enough interesting to be realized in plugin, I will be really unhappy if it will become default in twiki. It looks attractive, cool, ajax is extremally popular etc., but is it really The Right Direction To Move TWiki To? I have a doubt.

1. Let us imaging the situation. I am about to correct a term or an similar tiny part in all the sections. Now I have to lock all the document. In this moment my computer is suddenly off and before it come to working state nobody has access to document. If the document has really independent sections, then the current TWiki with SectonalEditPlugin? seems to be able to support the simultaneously editing in the more effective way.
2. I like ajax only if it really helps.
   • I do not want all my preliminary corrections to be immediately seen to others and I do not want to read uncomplete sentences and sentences in a minute before author change them. Only result of editing (probably partial or preliminary, but result) is ennoble to be shown to others. I do not see right place for ajax here.
   • I'd like to see immediately if somebody else start or abort editing the same topic and here is a good place for ajax;
   • I'd like to see immediately if there are any preliminary finalized by others editings (checkpoints) - good place for ajax also.
   • I'd like to distinguish preliminary and final savings. RCS has the feature to set status and get the last revisions of status required but twiki currently does not use this feature.
   • I'd like to have a simple interface to compare my last saved revision with any of the new other users savings and load the automatically merged new revision.

This need some small principal changes in core and additional contrib and (or) plugin.

How do you think, is it The Right Direction To Move TWiki To better multiple user editing support?

-- SergejZnamenskij - 29 Jan 2007