Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Saving in background would be very nice on large documents | ||||||
---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | Unknown <non-migrated> | ||||
Component: | code | Assignee: | Mathias_Bauer | ||||
Status: | CLOSED WONT_FIX | QA Contact: | issues@sw <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | issues, xslf | ||||
Version: | OOo 1.0.1 | Keywords: | oooqa | ||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Linux, all | ||||||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
Unknown
2002-11-14 04:52:28 UTC
Created attachment 3590 [details]
large file which takes a few seconds to save
Reassigned to Bettina. in 2.0 we will improve the saving so we can try this at 2.0 Hello Matthias, could you please give an estimation about the possibility of implementing multi-threading for allowing background saving in the applications? Thank you. There are no plans to add multi-threaded access to documents in "Q". Honestly speaking, it seems to be a nightmare to start working on this. Besides that I don't see the value. Even if we added multithreaded saving, of course you couldn't do any further changes on the document meanwhile. It's impossible to save a document *while* it is changed, with or without threads. So the only benefit you would have from a multithreaded storing procedure is that you can work in *other* documents while storing proceeds. But that is already possible in OOo1.1, even without multithreading. I think that multithreading is more elegant, but it doesn't add much value compared to the time it would take to implement it. So OOo later is OK for me, additionally I'd like to set the prio to 4. Our future plans don't leave room for a feature like this. The effort to move the complete document core outside the apartment is not judged by the value. If we ever will do this the desired feature will be gained automatically so there is no reason to keep this issue. closing |