office-collab — archive

How do we count? - September 26, 2012

From: Oliver-Rainer Wittmann <[email protected]>
To: [email protected]
Date: Wed, 26 Sep 2012 11:05:00 -0000

Hi, Andreas, Yes, Andreas is more or less right - it is a feature of the application. Do you think it make sense to create a dependency in the file format between two tracked changes which is not needed? Mit freundlichen Grüßen / Best regards Oliver-Rainer Wittmann -- Advisory Software Engineer ------------------------------------------------------------------------------------------------------------------------------------------- IBM Deutschland Beim Strohhause 17 20097 Hamburg Phone: +49-40-6389-1415 E-Mail: [email protected] ------------------------------------------------------------------------------------------------------------------------------------------- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 From: "Andreas J. Guelzow" <[email protected]> To: <[email protected]> Date: 25.09.2012 17:11 Subject: Re: [office-collab] How do we count? - September 26, 2012 Sent by: <[email protected]> On Tue, 2012-09-25 at 08:31 -0600, Oliver-Rainer Wittmann wrote: > Hi, > > > Operations are being added upon a stack/queue. Each operation is working > in > > relation to the document state at their time. Every operation is simply > added > > upon the stack, there is a basic time/stack depth relation. > > I am not sure, if it needed that operations need to be on a stack/queue for > an intrinsic change tracking. > > My view is: > In general two changes are independent unless the changes are touching the > same content. Even if they are touching the same content they can be > independent - e.g., formatting a text as bold and afterwards as underlined. > I admit that certain changes are depending on each other, but this is not > the general case from my point of view. > I think it is an important feature of CT in an application that certain > changes can be rejected/accepted independently. This feature is not really > supported by bringing the changes into a strict order. > I don't think that this is a feature of the file format. The file format needs an efficient way of storing a record of these changes. I don't think that whether individual changes can be accepted or rejected has nothing to do with that. Andreas -- Andreas J. Guelzow, PhD, FTICA Concordia University College of Alberta [attachment "signature.asc" deleted by Oliver-Rainer Wittmann/Germany/IBM]