Hi Matthias,
On Monday, 2006-11-20 15:34:26 +0100, Matthias Müller-Prove
wrote:
> Ok, let me put it this way: Any automatic solution to
date has flaws
> because the machine can not sense an important change.
If we need to prepare for important changes not expressable
as a change
summary we could provide an additional "important
changes" field.
However, in general the summary field is sufficient to
describe
a change.
> And it does not
> give you an overview about the history of the entire
document's life span.
If the summary field is taken serious the wiki history will
provide you
with an even better overview.
> Maybe managing source code with CVS is a different
story than managing
> specs. In any case is depends on the accuracy of the
user who checks in
> the new revision.
That's the same with some kind of changes field inside the
document.
> A useful summary for your example above would be:
"Correcting links to
> [[User Interface Guidrline]]"
> Less than 50 characters. The wiki diff page uses more
than 900
> characters for the same message.
The wiki page would say that with exact the same less than
50 characters
where it now only says "(->HCI Guidelines)" if
the author entered it as
a change summary, additionally to the "/* HCI
Guidelines */" that
already was pre-filled as the section comment in the summary
field.
Additionally it would still display all the bunch of changes
done in
that revision and the entire document as it was then.
Compare that to
a comment inside the document: "Correcting links to
[[User Interface
Guidrline]]", now what exactly did she change and
where?
Eike
--
OOo/SO Calc core developer. Number formatter stricken i18n
transpositionizer.
OpenOffice.org Engineering at Sun: http://blogs.sun.com/Gu
llFOSS
Please don't send personal mail to the erl sun.com
account, which I use for
mailing lists only and don't read from outside Sun. Thanks.
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe specs.openoffice.org
For additional commands, e-mail: dev-help specs.openoffice.org
|