Maybe I don't understand how you integrate with OOo. My understanding is
that you have a component that registers at a document and waits until
it is closed, then you want to revert this document back to the last
saved state, modify the edit time and send it to the server. How is the
document
Fabricio Lemos wrote:
Here is the scenario for my application:
1. The user request a document to the server.
2. The server stores, via java applet, the document at the user disk.
3. The user may open and close the document as many times he wants.
Some times he edit it, sometimes not. He can
So you could do the following:
If you know where the local disk copy is you can wait until the document
is closed, then load the file from disk in hidden mode, change the data
about the editing time (preferable as extended metadata in the document)
and send it to the server. Later on when we
All I need to do is, given a document file to the user, know how long
it kept the document open before he returned it to the server.
To prenvent the user from dealing all the time with 2 files, I was
storing this information on a user-field in the document file. But
before closing the document I
Fabricio Lemos wrote:
All I need to do is, given a document file to the user, know how long
it kept the document open before he returned it to the server.
To prenvent the user from dealing all the time with 2 files, I was
storing this information on a user-field in the document file. But
Why don't you update the editing time when the document is stored by the
user instead of waiting until he closes the document? In this case the
correct time gets stored along with all the changes the user wants. Of
course you will not keep track of the time that the user works on the
document
Fabricio Lemos wrote:
Why don't you update the editing time when the document is stored by the
user instead of waiting until he closes the document? In this case the
correct time gets stored along with all the changes the user wants. Of
course you will not keep track of the time that the user
I see. The best idea I have is to keep a local copy of the file each
time the document is sent to the server and when the document is closed
load the copy of the document (in hidden mode), change the time and sent
*this* document to the server.
Unhappyly, the user should be able to travel
Hello all,
Is there anyway, with macros, to revert all changes made in a document
since last time it was saved, without reloading it?
thanks in advance,
FabrÃcio Lemos
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Fabricio Lemos wrote:
Hello all,
Is there anyway, with macros, to revert all changes made in a document
since last time it was saved, without reloading it?
Such functionality does not exist at all, neither in the GUI nor in the
API.
You can call Undo until the undo stack is empty, in many
10 matches
Mail list logo