Hi,
There seems room to enhance the usability around a file lock system of 3.0.
A division runs a file server for its staffs.
1. A general manger sends an e-mail to staffs to see a document in the file
server.
2. User A opens the file with OpenOffice.org 3.0 as usual.
3. User B opens the file with OpenOffice.org 3.0 and faces a dialog window
saying
Document file 'xxx.odt' is locked for editing by:
user_a (mm.dd.yyyy hh:mm)
Open document read only or open a copy of the document for editing.
[Open Read Only] [Open Copy] [Cancel]
4. User C opens the file with OpenOffice.org 3.0 and faces the same dialog.
5. User D opens ..., and blames User A.
User A did not intend to edit it or even bother anybody else, but just wanted
to SEE it.
Models
"Look before editing it" model - once used by legacy version control systems:
rcs, sccs.
"Merge after editing it" model - used by recent version control systems: CVS,
Subversion, git.
Current implemention of 3.0 could be considered "Lock before editing it" model.
Interoperability with other tools
Several ODF tools - ODFToolkit, OODoc in Perl, ... - work with ODF files.
They, however, do not work with a lock file of 3.x: .~lock.xxx.odt# .
Regards,
Tora
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
